Guest Russell3 Posted November 2, 2007 Posted November 2, 2007 I a have a program which provides COM/OLE sevices. It registers its COM Interfaces on first running. This registration works in all MS operating systems used to date: Win9x, Win 2000, XP, Vista (after logging on as the real admin) and in Win 2003 (with no SPs or SP1). When trying to register the program in Win 2003 SP2 using any registration method, the registration is partial. Many, perhaps all interfaces are placed in the registry but the program does not provide the COM services. The methods of registration tried are: 1. Run the program. It runs and no errors are given on loading. 2. myprogram.exe /regserver All give partial registration. The program allows other programs to request data from a DB Server on separate DB Server. The program is used by VB code in MS Word to ask for data from the DB. The symptom seen by MS Word is I cannot compile in MS Word the main prog.dot file. When attempting to compile prog.dot in MS Word, using the VB Editor the error "Compile error \n Error in Loading DLL" is given. However when working in MS Word's VB Editor with my dot file the code completion feature works ... when I type in a call, it suggests options. So it seems the type library is being accessed. So between Win server 2003 SP1 and SP2 I have lost the ability to register my COM Server by running it or by any other method I know of. I have verified the program self registers running on Win 2003 server (initial version and SP1). I have verified on three MS Win 2003 Servers at different sites that the program does not install properly, all the same partial install. This indicates the problem has come into Win 2003 server with SP2, not with SP1. I need to get the program running on Win 2003 used as a terminal server. Users with thin clients use it to have MS Word get data out of a database and into their documents. Any insights appreciated.
Recommended Posts