Re: Changes Required for migration from MTS to COM+
From: Alexander Nickolov (agnickolov_at_mvps.org)
Date: 02/03/05
- Next message: Isaac: "RE: Accessing web service from C++: BeginParse fails in atlsoap.h"
- Previous message: Alexander Nickolov: "Re: how to cache the application dll in an ATL web service?"
- In reply to: tbs: "Changes Required for migration from MTS to COM+"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 3 Feb 2005 10:04:11 -0800
You may want to ask this on the COM+ group as well:
microsoft.public.platformsdk.complus_mts
-- ===================================== Alexander Nickolov Microsoft MVP [VC], MCSD email: agnickolov@mvps.org MVP VC FAQ: http://www.mvps.org/vcfaq ===================================== "tbs" <tbs@discussions.microsoft.com> wrote in message news:F57F4FFF-D7DF-496E-989A-A8EFDD56A181@microsoft.com... > Hi, > > I'm not sure whether this is the right forum to approach as I have not > much > background on C++. Sorry if I'm in the wrong forum and please direct me to > the right one. > > My client has recently upgraded their web/dbs server from win NT 4.0 to > windows server 2003 and mssql server 7.0 to 2000. Since the client have no > intention of moving the web to .net, therefore, to ensure that our exist > dlls > hosted in mts to be workable in com+ servers, minimal changes was done to > the > existing c++ codes/settings to ensure it's workability. Also, we were > planning to move the web server hosting from 2-tiers to 3-tiers. Most of > the > dlls are STA and windows crypto api and msxml.dll was also used in our > application. > > We are using visual studio 6.0, sp6 and asp for our implementation. > > We hired a technical consultant to advice us on the code/setting changes > to > be implemented on visual c++ 6.0. Here are his suggestions... > > 1. Download and install the Core SDK and Internet Development SDK for > Platform SDK. > > 2. Goto Project -> Project Settings -> Link, replace "mtx.lib mtxguid.lib > delayimp.lib" in Project Options with "comsvcs.lib". Also remove the line > "/delayload: mtxex.dll" > > 3. Goto Project -> Settings -> custom Build -> remove the commands and > outputs, if any. > > 4. Change #include <mtx.h> to <comsvcs.h> > > 5. Change the line in the code: > //HRESULT hr = GetObjectContext(&m_spObjectContext); > HRESULT hr = CoGetObjectContext(IID_IObjectContextInfo, (void > **)&m_spObjectContext); > > 6. Comment out the code to the calls of setAbort, setComplete from the > code. > > We have implemented his suggestion and hitting problems with the dlls. > After > some debugging, I discovered that some of his suggestions are the root > cause. > So we have reverted the changes made in No 6 and 7. And everything was > working fine after that even after all the neccessary testing done in both > development and production servers. > > However, after the production servers was release to go live, we start to > hit errors with the windows api. Example, some process seems to be holding > on > to the crypto api and when other processes tries to access it, it'll throw > some error to the other processes. It won't release until we restarted the > IIS sevices. > > I can't seem to replicate the problem in our development servers and when > I've even tried extensive testing on the production server but nothing > came > out. > > Now I'm at my wits end and since now there's some doubts on the > reliability > of the suggestion by the technical consultant, I need expert's in > verifying > the validity of the suggestions made. > > Thanks and Regards, > Boon Sie
- Next message: Isaac: "RE: Accessing web service from C++: BeginParse fails in atlsoap.h"
- Previous message: Alexander Nickolov: "Re: how to cache the application dll in an ATL web service?"
- In reply to: tbs: "Changes Required for migration from MTS to COM+"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
