We have problems with a third party software application. We have installed this software program on a terminal server (server 2003 32bit) and when we open this software with a existing user account the application crashes with the following entry in the eventviewer:
Application Error 100
Faulting application ProTime.exe, version 220.127.116.11, faulting module msvbvm60.dll, version 18.104.22.168, fault address 0x000fd0d9.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
We have checked the eventlog on the server but the only error that we see is the application error 100 when we open the program. Also we checked the rights on the program's database and folders but that doesn't help either.
The last thing we did was;
- Installing the software on a brand new virtual server with server 2003 x86 (no other software installed)
- Installing the software on a new virtual machine with server 2008 r2 x64 (no other software installed)
The strange thing is when we change something in the compatibility mode setting for example run as windows xp then we can run the program just fine but when the user logs off and log on again it doesn't work until you change something at the compatibility mode setting (doesn't mather which setting)
When we create a new domain user then the software works properly without any settings changed.
Any idea what could cause this problem?
With kind regards,
That is actually the problem. The support departement told us that they have no idea what is causing this problem and that the problems are not related to their software. But the problem only occur with their software.
They are 'working' on this issue since the beginning of Q2 2013. We have tried anything we could think of but it seems we are out of options.
Is the application build for usage on a terminal server? (Which registry hives is it using) Maybe changing it on registry level(Option Three) might do the trick. Note that it applies changes to both Local Machine and Current User. And that might be the root of your problems to begin with. That changes are not written to the correct registry hive. No matter what the below might give you something to work with.
Sorry for the late response. We think so, atleast the software company says it is.
We should not use the compat. mode because the application is not working on server 2003 x86, server 2003 x64, server 2008 r2.
It is just really strange. Software company has no clue how to fix this problem and they say it is caused by the active directory because when we add a new user then the application starts properly. User accounts created a long time ago are not able to start the application.
Well pull out two AD user objects and see if there is any difference between them? (new and old) - I'm thinking full set of properties. If using Powershell, you can even get Powershell to compare the two for you :)
$NewUser = GET-ADUser -Filter name John
$OldUser = Get-ADUser -filter Jimbo
Compare-Object $NewUser $OldUser
This will list the differences :)