Interesting note about portuguese XP. Are any other users using international versions of Windows?

By international you meen other than English? If so I'm using Swedish XP.

  Quote:

Originally Posted by hesa80

By international you meen other than English? If so I'm using Swedish XP.

Yes exactly, I'm beginning to think this is related to international versions.

Could I send you then the full log file?

  Quote:

Originally Posted by hesa80

Could I send you then the full log file?

Only the tail end is necessary and can be posted here.

Tue Jul 07 01:03:53 2009> [CoreManager] Starting client.
Tue Jul 07 01:04:21 2009> [CoreManager] Starting client.
Tue Jul 07 01:05:13 2009> [CoreManager] Starting client.
Tue Jul 07 01:06:21 2009> [CoreManager] Starting client.
Tue Jul 07 01:06:53 2009> [CoreManager] Starting client.
Tue Jul 07 01:15:32 2009> [CoreManager] Starting client.
Tue Jul 07 01:15:48 2009> [CoreManager] Starting client.
Tue Jul 07 01:15:49 2009> [CoreManager] Starting client.

The log I posted here is from the English Windows 7 RC1 64-bit, which eliminates the "international only"-theory.

  Quote:

Originally Posted by Hazno

The log I posted here is from the English Windows 7 RC1 64-bit, which eliminates the "international only"-theory.

Partially but not entirely. Do any of your paths contain special characters?

I'm trying to understand why some users are having issues with the same setup as others for who it is working fine.

Tue Jul 07 00:26:05 2009> [Warhammer Manager] Processing file
Tue Jul 07 00:26:05 2009> [Warhammer Manager] C:\ANVNDA~1\SAULIU~1\LOKALA~1\Temp\1246919165.tmp
Tue Jul 07 00:54:45 2009> [Warhammer Manager] E:/Spel2/Warhammer Online - Age of Reckoning/user/settings/Karak Eight Peaks/Raidan/Raidan/ZCurse_Profiler/
Tue Jul 07 00:54:46 2009> [Warhammer Upload] E:/Spel2/Warhammer Online - Age of Reckoning/user/settings/Karak Eight Peaks/Raidan/Raidan/ZCurse_Profiler/SavedVariables.lua
Tue Jul 07 00:54:46 2009> [Warhammer Manager] Processing file
Tue Jul 07 00:54:46 2009> [Warhammer Manager] C:\ANVNDA~1\SAULIU~1\LOKALA~1\Temp\1246920886.tmp
Tue Jul 07 00:56:05 2009> [Warhammer Manager] Warhammer closing
Tue Jul 07 01:03:53 2009> [CoreManager] Starting client.
Tue Jul 07 01:04:21 2009> [CoreManager] Starting client.
Tue Jul 07 01:05:13 2009> [CoreManager] Starting client.
Tue Jul 07 01:06:21 2009> [CoreManager] Starting client.

hesa80 - those log file entries are from May

  Quote:

Originally Posted by llamabark

Partially but not entirely. Do any of your paths contain special characters?

Didn't think about that, and it does as my user contains the special character é, which supports the special character issue theory.

Exact user path to log file: C:\Users\René\AppData\Local\CurseClient

Sry put from the wrong place :)

Tue Jul 07 18:53:30 2009> [CoreManager] Starting client.

That's all my .log says but nothing happens :)

------------------
System Information
------------------
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234)
Language: Swedish (Regional Setting: Swedish)
Processor: Intel(R) Pentium(R) D CPU 3.00GHz (2 CPUs)
Memory: 2046MB RAM
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)

*edit* reverted to 3.0.0.7 and it works peachy *edit*

  Quote:

Originally Posted by Hazno

  Quote:

Originally Posted by llamabark

Partially but not entirely. Do any of your paths contain special characters?

Didn't think about that, and it does as my user contains the special character é, which supports the special character issue theory.

I do think it is related to special characters which more support was added for in 3.0.0.8, but still determining exactly how. I am installing a swedish version of XP right now to do testing on. Hopefully I'll have more information and a fix soon.

My CurseClient log looks like the ones allready posted.  Eng. Win XP SP3.  I have an "ö" in my path.

Or simply try to create a new user account with a special character, which seems to cause it in my case. I'll try to create a new user account myself without any special characters to verify this theory.

My Path:

C:\Användare\Saulius Helene\Lokala inställningar\Application Data\CurseClient

  Quote:

Originally Posted by Hazno

Or simply try to create a new user account with a special character, which seems to cause it in my case. I'll try to create a new user account myself without any special characters to verify this theory.

Confirmed!

Just enabled my Guest Account, ran Curse Client logged in as Guest (which makes my path free of special characters), and it ran Curse Client successfully!

Yey! Atleast we know where the problem is hope we can run curse client soon again. :)

Alright, I have a local reproducible case. The public link to the client has also been temporarily rescinded to version 3.0.0.7.

I'll post when I have a fix.

Thanks 3.0.0.7 is working like before.

As an update, we will be doing more international testing before the next release.

I'm currently observing the reported behavior on the XP swedish installation, as described - client puts "Starting client" in the log file, and then does nothing.

It also appears there are two separate issues - upgrading the client via the updater, and the client not starting if it does update or installed manually.

I will be looking into both issues.

Reading the latest updates on the localization issues, I might add that the system it was working on for me (the Windows 7 machine) is of English language whereas the XP machine on which wasn't working on has a Swedish copy of Windows.

(My old post is the third one in the very beginning btw and contains more detailed system specs.)

Thanks again for the feedback Nusamitas,

I've verified the problem under swedish XP, and I'm fairly confident the issue is the same for international versions of Vista/Win7 too.

The issue has been tracked down to an error opening the master.log file and so returning early. I'm adding additional error reporting to the startup sequence for the future while fixing the actual issue.

Confirmed: I have a 3.0.0.8 version that runs on swedish xp now - the issue was with the sql engine not supporting the extended characters when they were part of the master.log path name (we'd tested for games with extended characters, but not international appdata configurations which are now added to the test set).

We will be waiting on a release of it until we have also resolved the updater issue too though. Until then the 3.0.0.7 client is available and should be working just as before.

Check up also Russian version Vista. My characters are not visible on wowdb.com in version 3.0.0.8

In version 3.0.0.7 too

Thanks for all the helpful feedback all,

There are two separate distinct issues:

1) The 3.0.0.7 client doing an automatic update improperly - We may not be able to fix that for international users in this version. However code has been changed to prevent that issue in the future. The issue is with how 3.0.0.7 lacked proper international support in calls the arguments to the updater.

2) The 3.0.0.8 client not running under international versions of windows(also mac, but as a very very rare case) - The 3.0.0.8 client now executes properly under the swedish XP testbed here (and of course english versions which were not affected by this issue)

Below is a modified 3.0.0.8 client I've verified under swedish XP. Please try the following link and report problems, if any with it:

http://files.getdropbox.com/u/428607/CurseSetup-3.0.0.8.exe

If you do encounter troubles, please include your operating system, language version, and any special characters. Additional logging has been added to the startup sequence as well, so the log file should be more useful relating to this issue.

Windows XP
german
special character: ü, but I think it's the same with ä and ö

Log:
Wed Jul 08 00:37:02 2009> [CoreManager] Starting client.
Wed Jul 08 00:37:03 2009> [CoreManager] Datadir C:/Dokumente und Einstellungen/Jürgen/Lokale Einstellungen/Anwendungsdaten/CurseClient/
Wed Jul 08 00:37:03 2009> [CoreManager] GameDB C:/Dokumente und Einstellungen/Jürgen/Lokale Einstellungen/Anwendungsdaten/CurseClient/
Wed Jul 08 00:37:03 2009> [CoreManager] Managers
Wed Jul 08 00:37:03 2009> [GameDB] GameDB opened successfully
Wed Jul 08 00:37:03 2009> [GameDB] Getting game instances
Wed Jul 08 00:37:03 2009> [GameDatabase] Error opening DB: C:/Dokumente und Einstellungen/Jürgen/Lokale Einstellungen/Anwendungsdaten/CurseClient/1246975694.log

Hello,

I've downgraded back to 3.0.0.7 and it works fine. I only now got to read this thread again, so my log has a mix of information from the weekend (running something previous to 3.0.0.8, not sure which version), then the bugged version, then a successful 3.0.0.7 run again. Here:

Sun Jul 05 13:39:51 2009> [CoreManager] Starting client.
Sun Jul 05 13:39:51 2009> [Startup] App started.
Sun Jul 05 13:39:54 2009> [Manage Addons Panel] Rebuilding Packages
Sun Jul 05 13:39:55 2009> [ProjectExceptions] OnExceptionsRetrieved
Sun Jul 05 13:39:56 2009> [GameProjectManager] OnExceptionsRetrieved
Sun Jul 05 13:40:17 2009> [Manage Addons Panel] Rebuilding Packages
Mon Jul 06 21:18:11 2009> [CoreManager] Starting client.
Mon Jul 06 21:18:12 2009> [Startup] App started.
Mon Jul 06 21:21:12 2009> [CoreManager] Starting client.
Mon Jul 06 21:21:13 2009> [Startup] App started.
Mon Jul 06 21:22:02 2009> [CoreManager] Starting client.
Mon Jul 06 21:27:36 2009> [CoreManager] Starting client.
Mon Jul 06 21:28:55 2009> [CoreManager] Starting client.
Mon Jul 06 21:29:47 2009> [CoreManager] Starting client.
Mon Jul 06 21:34:12 2009> [CoreManager] Starting client.
Mon Jul 06 21:34:13 2009> [CoreManager] Starting client.
Mon Jul 06 21:34:13 2009> [CoreManager] Starting client.
Mon Jul 06 21:34:14 2009> [CoreManager] Starting client.
Mon Jul 06 21:34:14 2009> [CoreManager] Starting client.
Mon Jul 06 21:34:14 2009> [CoreManager] Starting client.
Mon Jul 06 21:34:14 2009> [CoreManager] Starting client.
Mon Jul 06 21:34:15 2009> [CoreManager] Starting client.
Mon Jul 06 21:34:15 2009> [CoreManager] Starting client.
Mon Jul 06 21:39:12 2009> [CoreManager] Starting client.
Mon Jul 06 21:39:58 2009> [CoreManager] Starting client.
Tue Jul 07 09:21:58 2009> [CoreManager] Starting client.
Tue Jul 07 19:39:33 2009> [CoreManager] Starting client.
Tue Jul 07 19:45:31 2009> [CoreManager] Starting client.
Tue Jul 07 19:45:31 2009> [Startup] App started.
Tue Jul 07 19:45:34 2009> [Manage Addons Panel] Rebuilding Packages
Tue Jul 07 19:45:35 2009> [ProjectExceptions] OnExceptionsRetrieved
Tue Jul 07 19:45:35 2009> [GameProjectManager] OnExceptionsRetrieved
Tue Jul 07 19:46:07 2009> [Manage Addons Panel] Rebuilding Packages

The client updated itself on monday, then you can see the many frustrated attempts at running it. OS version is Windows XP Professional SP2, Brazilian Portuguese. The full path for the log is C:\Documents and Settings\User\Configurações locais\Dados de aplicativos\CurseClient\CurseClient.log, so your suspicion about "special" characters in the path may be valid.

  Quote:

Wed Jul 08 00:37:03 2009> [GameDatabase] Error opening DB: C:/Dokumente und Einstellungen/Jürgen/Lokale Einstellungen/Anwendungsdaten/CurseClient/1246975694.log

Thanks for the information Vyrt,

I checked the code on that portion and have a concern that the problem is not the 3.0.0.8 client itself, but the database files themselves which may have been created before international support was improved.

Could you try closing the client, purging the .log files in your user/appdata/local/curseclient (or the equivalent folder on your system) and restarting?

If my suspicion is correct, that should bring you up completely.

• .log files deleted
• first start of the client creates 3 new .log files (1247008591.log, CurseClient.log and master.log), but doesn't show itself
• second start the same I've posted before

complete log:
Wed Jul 08 01:16:31 2009> [CoreManager] Starting client.
Wed Jul 08 01:16:31 2009> [CoreManager] Datadir C:/Dokumente und Einstellungen/Jürgen/Lokale Einstellungen/Anwendungsdaten/CurseClient/
Wed Jul 08 01:16:31 2009> [CoreManager] Managers
Wed Jul 08 01:16:31 2009> [GameDB] GameDB opened successfully
Wed Jul 08 01:16:31 2009> [GameDB] Getting game instances
Wed Jul 08 01:16:31 2009> [CoreManager] Sanity check
Wed Jul 08 01:16:48 2009> [CoreManager] Starting client.
Wed Jul 08 01:16:48 2009> [CoreManager] Datadir C:/Dokumente und Einstellungen/Jürgen/Lokale Einstellungen/Anwendungsdaten/CurseClient/
Wed Jul 08 01:16:48 2009> [CoreManager] GameDB C:/Dokumente und Einstellungen/Jürgen/Lokale Einstellungen/Anwendungsdaten/CurseClient/
Wed Jul 08 01:16:48 2009> [CoreManager] Managers
Wed Jul 08 01:16:48 2009> [GameDB] GameDB opened successfully
Wed Jul 08 01:16:48 2009> [GameDB] Getting game instances
Wed Jul 08 01:16:48 2009> [GameDatabase] Error opening DB: C:/Dokumente und Einstellungen/J�rgen/Lokale Einstellungen/Anwendungsdaten/CurseClient/1247008591.log
Wed Jul 08 01:16:49 2009> [CoreManager] Sanity check
Wed Jul 08 01:16:49 2009> [CoreManager] Sane failed

http://files.getdropbox.com/u/428607/CurseSetup-3.0.0.8.exe

It is not started on 2008 server

The Russian coding is not supported:)

Wed Jul 08 13:15:44 2009> [CoreManager] Starting client.
Wed Jul 08 13:15:44 2009> [CoreManager] Datadir C:/Users/Администратор/AppData/Local/CurseClient/
Wed Jul 08 13:15:44 2009> [CoreManager] Managers
Wed Jul 08 13:15:44 2009> [GameDB] GameDB opened successfully
Wed Jul 08 13:15:44 2009> [GameDB] Getting game instances
Wed Jul 08 13:15:44 2009> [CoreManager] Sanity check
Wed Jul 08 13:15:47 2009> [CoreManager] Starting client.
Wed Jul 08 13:15:47 2009> [CoreManager] Datadir C:/Users/Администратор/AppData/Local/CurseClient/
Wed Jul 08 13:15:47 2009> [CoreManager] GameDB C:/Users/Администратор/AppData/Local/CurseClient/
Wed Jul 08 13:15:47 2009> [CoreManager] Managers
Wed Jul 08 13:15:47 2009> [GameDB] GameDB opened successfully
Wed Jul 08 13:15:47 2009> [GameDB] Getting game instances
Wed Jul 08 13:15:47 2009> [GameDatabase] Error opening DB: C:/Users/пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ/AppData/Local/CurseClient/1247044544.log
Wed Jul 08 13:15:54 2009> [CoreManager] Sanity check
Wed Jul 08 13:15:54 2009> [CoreManager] Sane failed
Wed Jul 08 13:16:23 2009> [CoreManager] Starting client.
Wed Jul 08 13:16:23 2009> [CoreManager] Datadir C:/Users/Администратор/AppData/Local/CurseClient/
Wed Jul 08 13:16:23 2009> [CoreManager] GameDB C:/Users/Администратор/AppData/Local/CurseClient/
Wed Jul 08 13:16:23 2009> [CoreManager] Managers
Wed Jul 08 13:16:23 2009> [GameDB] GameDB opened successfully
Wed Jul 08 13:16:23 2009> [GameDB] Getting game instances
Wed Jul 08 13:16:23 2009> [GameDatabase] Error opening DB: C:/Users/пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ/AppData/Local/CurseClient/1247044544.log
Wed Jul 08 13:16:25 2009> [CoreManager] Sanity check
Wed Jul 08 13:16:25 2009> [CoreManager] Sane failed
Wed Jul 08 13:16:37 2009> [CoreManager] Starting client.
Wed Jul 08 13:16:37 2009> [CoreManager] Datadir C:/Users/Администратор/AppData/Local/CurseClient/
Wed Jul 08 13:16:37 2009> [CoreManager] GameDB C:/Users/Администратор/AppData/Local/CurseClient/
Wed Jul 08 13:16:37 2009> [CoreManager] Managers
Wed Jul 08 13:16:37 2009> [GameDB] GameDB opened successfully
Wed Jul 08 13:16:37 2009> [GameDB] Getting game instances
Wed Jul 08 13:16:37 2009> [GameDatabase] Error opening DB: C:/Users/пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ/AppData/Local/CurseClient/1247044544.log
Wed Jul 08 13:16:41 2009> [CoreManager] Sanity check
Wed Jul 08 13:16:41 2009> [CoreManager] Sane failed

K lot of work, 3 liters of coffee, half a pack of smokes, and a couple of Xanax later, i think i got it.

Tue Jul 07 11:07:05 2009> [CoreManager] Starting client.
Tue Jul 07 11:07:19 2009> [CoreManager] Starting client.
Tue Jul 07 11:07:35 2009> [CoreManager] Starting client.
Tue Jul 07 11:07:43 2009> [CoreManager] Starting client.
Tue Jul 07 11:07:50 2009> [CoreManager] Starting client.
Tue Jul 07 11:08:33 2009> [CoreManager] Starting client.
Tue Jul 07 11:08:46 2009> [CoreManager] Starting client.
Tue Jul 07 11:08:53 2009> [CoreManager] Starting client.
Tue Jul 07 15:08:54 2009> [CoreManager] Starting client.
Tue Jul 07 16:19:24 2009> [CoreManager] Starting client.
Tue Jul 07 16:19:39 2009> [CoreManager] Starting client.
Tue Jul 07 16:19:53 2009> [CoreManager] Starting client.
Tue Jul 07 16:20:05 2009> [CoreManager] Starting client.
Tue Jul 07 16:20:06 2009> [CoreManager] Starting client.
Tue Jul 07 16:37:41 2009> [CoreManager] Starting client.
Tue Jul 07 17:16:48 2009> [CoreManager] Starting client.
Tue Jul 07 17:17:08 2009> [CoreManager] Starting client.
Tue Jul 07 17:53:58 2009> [CoreManager] Starting client.
Tue Jul 07 17:55:14 2009> [CoreManager] Starting client.
Tue Jul 07 17:55:16 2009> [CoreManager] Starting client.
Tue Jul 07 17:55:19 2009> [CoreManager] Starting client.
Tue Jul 07 18:56:56 2009> [CoreManager] Starting client.
Wed Jul 08 06:16:16 2009> [CoreManager] Starting client.
Wed Jul 08 12:04:38 2009> [CoreManager] Starting client.

I'm in Germany, running a Pentium Extreme, dual SLI Nvidea 280 on a Windows XP Porfessional 32 bits, using a US keyboard, without using any "special chars" aside from the ones the system might alocate...( you know Uncle Bill, he has HIS own ideas about what windows should do)

after the last install, which must be like the 5th or so, to get an Uninstall option i got to look for the curse folder and run it from there, tried really all i read here, EXEPT: downgrading, which i will do next.

Thanks dude :)

Hi!

These are all the files that apear inside Curse folder in Programs files in mi computer:

changelog.txt

CurseClient.exe

CurseClientUpdater.exe

EULA.txt

Uninstall.exe

On users folder \App Data\Local\CurseClient:

CurseClient.log

here i reproduce (copy-paste) that log:

Tue Jul 07 14:28:18 2009> [CoreManager] Starting client.

Tue Jul 07 14:28:47 2009> [CoreManager] Starting client.

Tue Jul 07 14:29:17 2009> [CoreManager] Starting client.

Tue Jul 07 14:30:02 2009> [CoreManager] Starting client.

Tue Jul 07 23:43:50 2009> [CoreManager] Starting client.

Wed Jul 08 12:27:40 2009> [CoreManager] Starting client.

Wed Jul 08 12:28:14 2009> [CoreManager] Starting client.

Thanks for your pourpose in fixing the problem

greetings

MaDBR

Roll back to 3.0.0.7 and!!! works fine. :)

thanks!

(till it updates itself again I guess)

mi Windows vista home premium 32bit sp1 is in spanish version

greetings

MaDBR

  Quote:

Originally Posted by llamabark

Thanks for all the helpful feedback all,

There are two separate distinct issues:

1) The 3.0.0.7 client doing an automatic update improperly - We may not be able to fix that for international users in this version. However code has been changed to prevent that issue in the future. The issue is with how 3.0.0.7 lacked proper international support in calls the arguments to the updater.

2) The 3.0.0.8 client not running under international versions of windows(also mac, but as a very very rare case) - The 3.0.0.8 client now executes properly under the swedish XP testbed here (and of course english versions which were not affected by this issue)

 

Below is a modified 3.0.0.8 client I've verified under swedish XP. Please try the following link and report problems, if any with it:

http://files.getdropbox.com/u/428607/CurseSetup-3.0.0.8.exe

 

If you do encounter troubles, please include your operating system, language version, and any special characters. Additional logging has been added to the startup sequence as well, so the log file should be more useful relating to this issue.

heya, after installing this 3.0.0.8 file you gave us on the quoted post i got this error:

So i did as it told, and after the installation tryed to open the client again. Not thing happened. So i tried to open it again and got the same error again. (The number on the log might've been diferent on the first time (didn't took a screen that time). But the error was exactly the same.)

So... one thing to notice is that path... it has those strange characters... the real path is:

The log file link is here.

That makes it all. I'm thinking of unstalling the 3.0.0.8 and stick with 3.0.0.7 till you find out the uncompatibility problems.

Good luck.

lol i notice youre using a Portuguese copy of windows as well, BUT a serious question comes to mind!!! could it be that the windows updates, from Xp Portuguese, that GET (!!!) updates from XP Portuguese (Brazil) and sometimes ARE very, (VERY) badly translated, could mess up this thing??

Can't seem to get my updates 100% from Portuguese/ Portugal  >.<

and sometimes you get them in Portuguese/Portugal => Portuguese/ Brazil => and some English ones thrown in for good measure, (godda love Uncle Bill's Windows )

just a thought, for i have had some "minor" >.< probs wiht that.

Thank you for the additional information all,

Vyrt - I will look into why the secondary log filenames are not being handled correctly.
SokRus - I'll add Russian to the current list of languages we hope to support - english,spanish,swedish,german,french,portugese.
Lyanthros - Great feedback, it appears a couple people are getting the sanity check failed error.

I had hoped purging the log files would reset the database, but it seems more testing is needed there.

I'll post when I have an update.

Lynathros,

There seems to be a paradox in what you wrote. I just did a few tests on the swedish xp box and it appears to handle creating new log files fine.

You showed the error dialog saying it could not open 1247054247.log
However after you'd said you purged the .log files - that file is still there?

My concern is that the DB itself has a corrupted file path, and that purging the database would have forced a rebuild, creating a new file name/path properly.

However the 1247054247.log was still there after, so either:
* The report is in error
* The filename was erroneously created identically (which should not happen as it is timestamp based)
* The client is recreating it with another bad handle.

  Quote:

Originally Posted by llamabark

Lynathros,

There seems to be a paradox in what you wrote. I just did a few tests on the swedish xp box and it appears to handle creating new log files fine.

You showed the error dialog saying it could not open 1247054247.log
However after you'd said you purged the .log files - that file is still there?

My concern is that the DB itself has a corrupted file path, and that purging the database would have forced a rebuild, creating a new file name/path properly.

However the 1247054247.log was still there after, so either:
* The report is in error
* The filename was erroneously created identically (which should not happen as it is timestamp based)
* The client is recreating it with another bad handle.

Quoting myself on the previous post:

  Quote:

(The number on the log might've been different on the first time (didn't took a screen that time). But the error was exactly the same.)

It probably purged the file on the installation i had. then after i reinstalled, open the first time (which it probably created the new log file - that you see on the images) and nothing happened, then opening a second time and then the error showed.

Basically, what i'm saying is the same thing happened twice. And i simply didn't take a screen on the first error (related to the log file). Supposedly the first error filename was different, so it did purge the file.