COMs not working in Windows Server 2003

[Cesar Manzano]

I had a working Web site with several VFP COMs, this site was hosted in a
Windows 2000 Server machine. The company changed to Microsoft Windows Server
2003 for Small Business Server (Service Pack 1) and I moved all the
directories with ne ASP files to the new computer, copied the *.EXE, *.TLB
and *.VBR to the new SYSTEM32 directory and registered all of them with
name.exe /regserver

Then the nightmare began ...

Nothing worked, I raised the security level of IUSR_namemachine, in every
directory I thought, I used the Component Services Management Utility, I
recompiled the EXEs in DLLs, registering them with RegSvr32 ;

The site is working very erratical, with the ASPNET account sometimes the
COMs work, sometimes don't. As far as I understand, all this is a security
problem. Windows 2003 is a more secure platform and this should be
documented somewhere ....

Has anybody already went through this path ? Does anybody know what to do
and how to do it ?

Thank you

[Eric den Doop]

Did you set DCOM on the EXEs? I have no problems running COM EXE in
IIS/ASP.NET... If you are using an Application Pool in IIS, you need to make
sure that the account for that AP has sufficient rights in DCOM.
--
Eric den Doop
www.foxite.com - The Home Of The Visual FoxPro Experts
Microsoft MVP for Visual FoxPro

"Cesar Manzano" <cesar_manzano-nospam-at-nospam-vitservices.com> wrote in

Post by Cesar Manzano
I had a working Web site with several VFP COMs, this site was hosted in a
Windows 2000 Server machine. The company changed to Microsoft Windows Server
2003 for Small Business Server (Service Pack 1) and I moved all the
directories with ne ASP files to the new computer, copied the *.EXE, *.TLB
and *.VBR to the new SYSTEM32 directory and registered all of them with
name.exe /regserver
Then the nightmare began ...
Nothing worked, I raised the security level of IUSR_namemachine, in every
directory I thought, I used the Component Services Management Utility, I
recompiled the EXEs in DLLs, registering them with RegSvr32 ;
The site is working very erratical, with the ASPNET account sometimes the
COMs work, sometimes don't. As far as I understand, all this is a security
problem. Windows 2003 is a more secure platform and this should be
documented somewhere ....
Has anybody already went through this path ? Does anybody know what to do
and how to do it ?
Thank you

[Cesar Manzano]

Eric, all of this is new to me. All I had to do before Windows SBS 2003 was
to copy the EXE, TLB and VBR and register the COM with name.exe /regserver.

Now, it is a complete new ball game for me. I put these files in
Windows\System32 and register them with the same method and nothing happens;
I tried compiling them as a .DLL and registering them with RegSvr32, same
result.

I have worked with the DCOM utility, sometimes I find my EXEs with their
names, sometimes only with the GUID key. I change the user to Administrator,
and get no results.

I have worked with the IIS Manager and I have spend a lot of time with the
Windows Explorer, I even installed the NET Framework SDK to get the ASPNET
account, because it wasn't there.

What do I do ?, How do I do it ?

Everything was working perfectly in Windows XP Pro and Windows 2000 Server,
now it is a nightmare of permits and security. I am sure somebody has had
this problems already and found that simple switch to correct it.

There are some 12 ASP pages, about 4 VFP 6.0 COMs and the error I get is
'ASP 0177 : 80004005' , an error I understand is about permits. The ASPNET,
IUSR and IIS_WPG ahve already all the security rights possible.

Do I have to do something different in the IIS Manager ? Do I have to
configure the server specially for Web ?

Post by Eric den Doop
Did you set DCOM on the EXEs? I have no problems running COM EXE in
IIS/ASP.NET... If you are using an Application Pool in IIS, you need to make
sure that the account for that AP has sufficient rights in DCOM.
--
Eric den Doop
www.foxite.com - The Home Of The Visual FoxPro Experts
Microsoft MVP for Visual FoxPro
"Cesar Manzano" <cesar_manzano-nospam-at-nospam-vitservices.com> wrote in

Post by Cesar Manzano
I had a working Web site with several VFP COMs, this site was hosted in a
Windows 2000 Server machine. The company changed to Microsoft Windows Server
2003 for Small Business Server (Service Pack 1) and I moved all the
directories with ne ASP files to the new computer, copied the *.EXE, *.TLB
and *.VBR to the new SYSTEM32 directory and registered all of them with
name.exe /regserver
Then the nightmare began ...
Nothing worked, I raised the security level of IUSR_namemachine, in every
directory I thought, I used the Component Services Management Utility, I
recompiled the EXEs in DLLs, registering them with RegSvr32 ;
The site is working very erratical, with the ASPNET account sometimes the
COMs work, sometimes don't. As far as I understand, all this is a security
problem. Windows 2003 is a more secure platform and this should be
documented somewhere ....
Has anybody already went through this path ? Does anybody know what to do
and how to do it ?
Thank you