IIS 5 & IIS 6
Com+ transaction taking long time after migration
Last post Feb 14, 2008 12:05 AM by steve schofield
Feb 11, 2008 07:35 AM|Sevian|LINK
in progress of migrating an app to new infrastructure
1 MTS server handling COM (app layer)
1 IIS6 server Proxied stubs pointing to MTS server.
Involves removing Win2k Server from existing domain (firewalled domain)
Repatching to new network and assigning new host file entries ie Webserver address etc.
Same port rules used from previous enviroment as there are hops through firewalls between app n pres layer.
Same proces for presentation Win2k (IIS6) server.
Problem is once i move to new network running a simple test.vbs to instantiate the com object takes about 15 seconds, its almost instant in the old enviroment. Same for application itself invoking a test object via IIS takes possibly longer up to 30/45. Ive
checked app/system even logs nothing jumping out at all, any idea how or where i start?
Feb 14, 2008 12:05 AM|steve schofield|LINK
I forget now if this is an IIS 4 to IIS 5 thing or IIS 5 to 6. AspExecuteInMTA is a metabase setting.
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/e9880a74-49bd-4fb6-9856-c4f4c5108207.mspx I recall having COM+ issues when migrating from one IIS version to the next, I believe it was 4 to 5, but my I'm having a senior moment.
I would test this in a controlled environment to see if you can reproduce the 'slowness'. Also, do you see anything in network monitor? maybe some kind of resolution, duplex issue somewhere, just a thought.
Windows Server MVP - IIS
Log archival solution
Install, Configure, Forget