>>What is the nature of your problems migrating COM / MTS objects? What OS is the new server running?
>
>Not migrating, just rebuilding. Running W2K advanced server. After the network upgrade the web service simply refused to serve up classic ASP pages. Standard HTML and .NET pages worked fine. Actually classic ASP would serve each ASP page one time then refuse to process that page again until server was rebooted. Very strange behavior. Network monitor shows communication ok until ASP page served and then it started dropping frames. I tried everything (I know) to fix the problem with no success.
>
>The time consuming part has been reloading, registering and configuring MTS on all the COM's that are used, mostly legacy stuff. A lot of VFP COM's handling web requests before we developed a common VFP/ASP COM wrapper. I've had a number of problems with old COM's that were ported up from the old NT server days like graphics server. They ran fine on the old W2k box but I've not been able to get them running on the rebuild. Get past one error just to get another one.
>
>
>>We will be moving some of our apps to W2K, including several MTS packages. Any pointers / gotchas are welcome and appreciated.
>
>Expected the unexpected and pray hard...
>Actually assuming you are talking about VFP based applications I would expect the transition to go fairly smooth.

Yes, mostly VFP DLLs. Are you using VFP 6 or 7?