« Previous Next »

Thread: COM+ DLL loses ASPTypeLibrary function when moved to server

Last post 07-16-2009 6:01 PM by dcwebman. 1 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (2 items)

Sort Posts:

  • 07-16-2009, 10:58 AM

    • dcwebman
    • Not Ranked
    • Joined on 01-29-2009, 1:23 PM
    • Posts 2

    COM+ DLL loses ASPTypeLibrary function when moved to server

    We have multiple web servers running Windows Server 2003 with IIS 6. ASP pages call COM+ VB6 DLL's which in turn call SQL database stored procedures. The DLL's had to be changed because IIS had to be changed from Windows authentication to Anonymous. Since the DLL's were expecting the Windows authentication they didn't work so they had to be changed to use ASPTypeLibrary to get values from session variables. Works great and we put them on our test server and everything tested fine. No changes were necessary for the server.

    We then moved them to our staging server and suddenly ASPTypeLibrary doesn't work on that server as nothing comes back from the session variables. The servers were built identically and we have checked every IIS setting we can think of, the services running seem to be the same, and every comparison we can think of is identical. Obviously the code hasn't changed so there must be something server related we're not finding that's different between the two servers.

    To check it out more we put the DLL's on another server and they worked fine there too. And a dummy DLL was created to try on the production server and it failed there just like the staging server. So we have 2 servers where they work and 2 where they don't.

    We have been trying for a couple days to resolve this since the latest code was supposed to be released to production already so any help would be greatly appreciated! Thanks!

  • 07-16-2009, 6:01 PM In reply to

    • dcwebman
    • Not Ranked
    • Joined on 01-29-2009, 1:23 PM
    • Posts 2

    Re: COM+ DLL loses ASPTypeLibrary function when moved to server

    After getting no answers and not finding a solution, we just reinstalled IIS and everything else along with it and then the other server worked.

Page 1 of 1 (2 items)
Microsoft Communities