We have developed a COM based Client-Server application. The UI makes request to the Server which is a COM (MyServer.dll) DLL. This DLL in turn calls another generic COM component (DBWrapper.dll) for Database access. MyServer.dll is to be deployed on COM+ on a different machine than that of UI and DBWrapper will be deployed on the same machine as MyServer.dll and is to be instantiated as In-Proc (NO COM+).
If we instantiate MyServer as a In-Proc server the application works fine. But if I deploy MyServer on COM+ the DBWrapper behaves erratic. Some times it gives proper response and sometimes it returns error. We have no clue as to what is wrong. The behaviour is random and it can't be predicted which specific call causes failure.
Can anybody tell me what might be going wrong in this scenario? I am using ATL with C++ for sever and the component threading model is both.
>>the component threading model is both.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;150777 ("INFO: Descriptions and Workings of OLE Threading Models")
See also http://support.microsoft.com/default.aspx?scid=kb;en-us;206076
MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.
A theme is a collection of property settings that allow you to define the look of pages and controls, and then apply the look consistently across pages in an application. Themes can be made up of a set of elements: skins, style sheets, images, and o…
Whether you've completed a degree in computer sciences or you're a self-taught programmer, writing your first lines of code in the real world is always a challenge. Here are some of the most common pitfalls for new programmers.
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel.
Part 1 of this series discussed basic error handling code using VBA.
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …