VBS vs ASP object instantiation

Results 1 to 2 of 2

Thread: VBS vs ASP object instantiation

  1. #1
    Steve F. Guest

    Default VBS vs ASP object instantiation

    I have an out of process (.exe) COM component, that can be instantiated for a .VBS on our IIS server.<BR>This tells me that the COM is register and functioning correctly.<BR><BR>But when the instantiation the component is within ASP (ie IIS) I get the dreaded 429: Server cannot create object error!<BR><BR>Two questions:<BR><BR>What is the difference between Server.CreateObject and CreateObject in regards to application memory space?<BR><BR>Why can the native VBS engine work and not within ASP?<BR><BR>I think that is has to do with IIS securities?????<BR><BR>If you need more information, let me know.<BR>

  2. #2
    Join Date
    Dec 1969

    Default RE: VBS vs ASP object instantiation

    You have to enable out-of-process objects in IIS and PWS.<BR><BR>Microsoft recommends that you do *NOT* do this, but if you check the MSDN knowledge base, there&#039s at least one article on how to enable them.<BR><BR>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts