I've been executing msbuild.exe from the NT_AUTHORITY\SYSTEM account to build VS 2005 C# projects and the builds have been working as expected. Recently, I attempted the same for a VS 2004 C++ project and the build failed with the following error.
fatal error C1902:
Program database manager mismatch;
please check your installation
Is this a bug with msbuild or am I doing something wrong?
Thanks
Hello -
Unfortunately this is a bug in the C++ compiler, and there is no work-around for the issue. It has been fixed, and we expect the fix to ship in the next update of our product.
Until that time you'll have to compile under a normal user account.
Sorry for the inconvenience.
Mark Lacey
Visual C++ Development Team
Hello
I have been bitten by the same problem upgrading from DevStudio 2003 to DevStudio 2005.
I am using an automated build system and changing the user account [currently LocalService] is not possible.
Any idea of the timescale for the bug-fix release? (even an hot-fix would be great)
best regards,
andrea
Hi Mark
We are having exactly the same problem here but when we call MS to get the hotfix we are asked for the article id.
Can you let us know what this is so we can get the hotfix.
Thanks
Dan
Dan,
I sent mail to Mark to ask him to reply back with the article number. He's out of the office on vacation until the 15th though, hope that's ok.
Neil
It was only recently that we started working on a hot fix for this bug (the bug was fixed in our "live" sources but had not yet been ported back to the Whidbey sources).
The fix is actually not yet available. Once it is complete I will reply again with the hot fix number. I suspect this should be within the next week or two.
Sorry for any inconvenience this delay might cause.
Mark Lacey
Visual C++ Development
Hi,
I've been informed that you should be able to get this fix by mentioning KB article #920770. The article is not yet published, but you should still be able to use this to get the hot fix.
Hi Mark,
I have run into the same problem, but the folks we have spoken with at Microsoft have not been able to find the hotfix based on the KB article number. Are there any other pointers you can give on how to get the hotfix?
Thanks, and best regards,
- Bill
Hi Bill,
The hotfix has been available since 6/19. Do you have support case # to follow up on?
Jaganathan
we had the same problem.
the MS guys are waiting for the knoledgebase article to be published before they will look up the hotfix. so we were waiting but nothing yet.
Dan
A colleague of mine was able to get the hotfix after a second call to MS support, mentioning that the KB article hadn't been published yet, and that the hotfix seems to be difficult to get ahold of. Thank you, Jaganathan, for your reply - do have any tips for the rest of the class on how best to get the hotfix?
- Bill
Unfortunately the KB article is the only link I can post externally and that is not published. I would ask the support person you are talking to, to look up the KB # on MS internal "hotfix sever" where its available to send to customers.
Jaganathan
Tested: The error in mspdbsrv is still in VS 2005 SP1 not fixed.
The error will occur less often - but when starting cl.exe in a service (e.g remote login, run as) the bug will still occur.
I don't understand, why .obj file could be generated by cl.exe, but .pdb files need an additional (buggy) service.
