<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Subject to confirmation at all sites with the
problem described below the error discussed below has been solved. Its solution
is described here. First, another fact. When win 2003 sp2 is installed on a
virtual host the problem does not appear. So what is the problem? You can read
the symptoms below. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>When a Delphi 6 application providing COM/OLE
automation services is installed the stdvcl40.dll also should be registered
in the PC's registry. If the application is installed after SP2 is installed,
stdvcl40.dll is not registered; unless Win2003 sp2 is installed virtually (only
confirmed in one case). This omission caused the COM Server interface to
fail when created in a client application, such as a dot file for MS Word
containing VB code. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>What causes this omission? I don't know; it seems
somewhere in the transition from SP1 to SP2, Win 2003 has introduced a
bug.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>What can be done to remedy this omission?
stdvcl.dll must be with the application. tregsvr .exe is in the D6.bin
folder. With both files in the apps folder, log onto the troubled box as
administrator. From a cmd window run "tregsvr stdvcl40.dll" <enter>. This
should register the dll properly and the app can now provide its
services.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>On all other MS operating systems, including Vista
(when logged on as the true administrator) the registration of stdvcl40.dll is
handled properly by </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>"..\bcddocuments.exe /regserver"</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Resources:</FONT></DIV>
<DIV><FONT face=Arial size=2>ResistryTool.exe (program for multiple
registry comparisons with a help manual explaining COM/OLE principles and how
Windows' registry uses its data for COM services)</FONT></DIV>
<DIV><FONT face=Arial size=2>Process Monitor (procMon.exe) Free download from
SysInternals for capturing OS actions in a log file. It replaces RegMon.
The best Windows diagnostic tool I have used. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Russell Belding</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=staff@belding.co.nz href="mailto:staff@belding.co.nz">staff</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=delphi@delphi.org.nz
href="mailto:delphi@delphi.org.nz">NZ Borland Developers Group - Delphi
List</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, November 13, 2007 12:40
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [DUG] Repost of COM/OLE install
problems</DIV>
<DIV><BR></DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>In light of
new insights in this note I am reposting it here, after posting it to
"microsoft.public.windows.windows.server.general". </FONT></FONT></DIV>
<DIV>Perhaps others here using Delphi might run into this error later.</DIV>
<DIV>***************</DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman"
size=3></FONT></FONT> </DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>SP2 for Win
2003 was published in Mar 07.<BR></FONT><A
href="http://www.microsoft.com/downloads/details.aspx?familyid=95ac1610-c232-4644-b828-c55eec605d55&displaylang=en"><FONT
face="Times New Roman"
size=3>http://www.microsoft.com/downloads/details.aspx?familyid=95ac1610-c232-4644-b828-c55eec605d55&displaylang=en</FONT></A><BR><BR><FONT
face="Times New Roman" size=3>A program, bcdDocuments.exe, providing COM
services was already running on <BR>terminal servers and working correctly was
unaffected as SP2 was installed.<BR>This program uses MS Word, all versions
using VB, to make documents. Its <BR>installation is done by
running<BR>"..\bcdDocuments.exe /regserver" and its uninstall by
running<BR>"..\bcdDocuments.exe /unregserver".<BR><BR>The program still
installs and runs correctly on Win 2003 SP1 and below. It <BR>also installs
and runs as expected on all versions of Win 2000, Win XP and <BR>Vista that we
have tried. On Win 2003 SP2 the registry entries appear to <BR>install
correctly but the program will not run correctly, as follows.<BR><BR>When
attempting to compile prog.dot in MS Word, using the VB Editor, the <BR>error
"Compile error \n Error in Loading DLL" is given. However<BR>when working in
MS Word's VB Editor with this dot file the code completion <BR>feature works
... when I type in a call, it suggests options. So it seems <BR>the<BR>type
library is being accessed. The type lib is inside bcdDocuments.exe.<BR><BR>The
prog.dot file asks bcdDocuments for data which is inserted into <BR>documents
being made.<BR><BR>We have consistent results.<BR><BR>bcdDocuments installs
and runs as expected on Win 2000, Win XP, Vista, Win <BR>2003 SP1 and below.
It runs on Win 2003 SP2 provided it was installed before <BR>SP2 was
installed. It will not (install and run correctly) on Win 2003 SP2 <BR>if
installed after SP2.<BR><BR>I have looked and not found any static registry
problem between an <BR>installation on a<BR>1. Win 2003 SP1 box, and a<BR>2.
Win 2003 SP2 box.<BR><BR>I am trying to instrument using ProcMon to look for
dynamic errors.<BR><BR>Is this the best place to post this problem? Can
someone suggest a better <BR>place?<BR><BR>Any help appreciated.<BR>Russell
Belding </FONT><BR></DIV></FONT>
<P>
<HR>
<P></P>_______________________________________________<BR>NZ Borland
Developers Group - Delphi mailing list<BR>Post: delphi@delphi.org.nz<BR>Admin:
http://delphi.org.nz/mailman/listinfo/delphi<BR>Unsubscribe: send an email to
delphi-request@delphi.org.nz with Subject:
unsubscribe</BLOCKQUOTE></BODY></HTML>