Registration-free COM not working on Windows Server 2003 -


I created the required client application for my COM server DLL and Windows XP to do registration-free work. I have tested all types of combinations (without a registration and without) and in all cases the client sees the side-by-side version of the application library if the manifest exists and is not registered (or COM error if all No registration). I have tested on my Windows XP development machine, and have given files to co-workers (DLL, Client XE and a Manifest for each) who have successfully run everything on their Windows XP machines. Manifest is external XML files, there are no embedded resources. So far, so good.

However, when I copy files into a Windows Server 2003 machine, it does not work, I get a silent failure, but an app error in the application event log (see below). If I unregister DLL and delete the manifest, I get a similar error (shut down at the command prompt, but an application error in the event log). Obviously there is some problem in finding the registration. I have reproduced it on every Windows Server 2003 machine which I can use in our company. According to Microsoft's documentation of Side-by-Side / Registration-free COM, it is going to work on Windows XP and above, and Windows Server 2003 and later.

The same COM DLL version registered ( i.e., under the same login credentials on the same Windows Server 2003 machines that the customer runs entirely, to be clear. , using regsvr32) I am trying to use to register for free COM In other words, there are no internal problems not being asserted as registration-free com problems - this client and Server works fine When the server is registered in the Worldwide Registry.

How do anyone have any idea of ​​further investigation? I'm not an expert on Windows Server, but maybe it's some policy setting that needs to be changed to enable this support? If I can find out the necessary changes, then our technical support / infrastructure people probably will not do this, but I can not trust them to do research on this issue to rely on them.

Cases (I do not think it should, but you never know) DLL has been written in Delphi 2007, while the client has been written in Visual C ++. Event Type: Information Event Source: Application Error Event Category: (100) Event ID: 1004 Date: 5/2/2009 Time: 8:07:45 AM User: N / A Computer: ** * Server Name **** Description: Reporting Error: Application of Error *** Program Name ***. Exe, Version 0.0.0.0, Defective Module *** Program Name ***. Exe, version 0.0.0.0, mistake address 0x0002ac9e. For more information, see the Help and Help Center at http://go.microsoft.com/fwlink/events.asp

One thing to see is that if an internal appears in XP, in XP, the XE manifest search order is external then internal server 2003 and later, if the order is internal then external


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -