Win 2003 SP2 Bug?

[Guest Russell Belding]

SP2 for Win 2003 was published in Mar 07.

http://www.microsoft.com/downloads/details.aspx?familyid=95ac1610-c232-4644-b828-c55eec605d55&displaylang=en

 

A program, bcdDocuments.exe, providing COM services was already running on

terminal servers and working correctly was unaffected as SP2 was installed.

This program uses MS Word, all versions using VB, to make documents. Its

installation is done by running

"..\bcdDocuments.exe /regserver" and its uninstall by running

"..\bcdDocuments.exe /unregserver".

 

The program still installs and runs correctly on Win 2003 SP1 and below. It

also installs and runs as expected on all versions of Win 2000, Win XP and

Vista that we have tried. On Win 2003 SP2 the registry entries appear to

install correctly but the program will not run correctly, as follows.

 

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 this 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. The type lib is inside bcdDocuments.exe.

 

The prog.dot file asks bcdDocuments for data which is inserted into

documents being made.

 

We have consistent results.

 

bcdDocuments installs and runs as expected on Win 2000, Win XP, Vista, Win

2003 SP1 and below. It runs on Win 2003 SP2 provided it was installed before

SP2 was installed. It will not (install and run correctly) on Win 2003 SP2

if installed after SP2.

 

I have looked and not found any static registry problem between an

installation on a

1. Win 2003 SP1 box, and a

2. Win 2003 SP2 box.

 

I am trying to instrument using ProcMon to look for dynamic errors.

 

Is this the best place to post this problem? Can someone suggest a better

place?

 

Any help appreciated.

Russell Belding

[Guest Russell Belding]

Re: Win 2003 SP2 Bug?

 

Can one of the MS experts on servers, attending this newsgroup, suggest to

me where I should go to present this possible bug in Win 2003 SP2? It seems

to me nowone here is willing to say anything. I mean no disrespect!

 

I have looked into an SP2 server with ProcMon from SyInternals and althought

I am not competent with this tool yet, I have found no problems.

 

"Russell Belding" <staff@belding.co.nz> wrote in message

news:uSRO%23KYJIHA.3940@TK2MSFTNGP05.phx.gbl...

> SP2 for Win 2003 was published in Mar 07.

> http://www.microsoft.com/downloads/details.aspx?familyid=95ac1610-c232-4644-b828-c55eec605d55&displaylang=en

>

> A program, bcdDocuments.exe, providing COM services was already running on

> terminal servers and working correctly was unaffected as SP2 was

> installed.

> This program uses MS Word, all versions using VB, to make documents. Its

> installation is done by running

> "..\bcdDocuments.exe /regserver" and its uninstall by running

> "..\bcdDocuments.exe /unregserver".

>

> The program still installs and runs correctly on Win 2003 SP1 and below.

> It also installs and runs as expected on all versions of Win 2000, Win XP

> and Vista that we have tried. On Win 2003 SP2 the registry entries appear

> to install correctly but the program will not run correctly, as follows.

>

> 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 this 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. The type lib is inside bcdDocuments.exe.

>

> The prog.dot file asks bcdDocuments for data which is inserted into

> documents being made.

>

> We have consistent results.

>

> bcdDocuments installs and runs as expected on Win 2000, Win XP, Vista, Win

> 2003 SP1 and below. It runs on Win 2003 SP2 provided it was installed

> before SP2 was installed. It will not (install and run correctly) on Win

> 2003 SP2 if installed after SP2.

>

> I have looked and not found any static registry problem between an

> installation on a

> 1. Win 2003 SP1 box, and a

> 2. Win 2003 SP2 box.

>

> I am trying to instrument using ProcMon to look for dynamic errors.

>

> Is this the best place to post this problem? Can someone suggest a better

> place?

>

> Any help appreciated.

> Russell Belding

>