IIS 5 & IIS 6
IIS reporting Microsoft.VisualBasic error '80131500' Cannot create Ac...
Last post May 29, 2008 11:39 AM by pfelsted
May 28, 2008 11:57 AM|pfelsted|LINK
I recently bought a new server to put in my NLB cluster. It came from dell preisntalled with windows server 2003 R2 standard edition and it has SP2 on it. All of my other IIS servers have windows server 2003 (not R2).
When I installed my application we started getting errors after a while of running from one of my COM mobdules that some ASP code calls. This COM code works fine on all of my other servers just this new one is having trouble. The error is:
Microsoft.VisualBasic error '80131500'
Cannot create ActiveX component.
I found a hot fix for this on the MS site: KB883955. However, when I went to install it it said I have it already in a service pack and would not install.
Anyone have any ideas about this issue?
Another oditiy about this system is it appears when this happens the web service extensions are not working. When i select it with the IIS manager i see nothing. Then I go to the web servers and select it and it says do you want to connect, then I say
yes and then the web service extensions works. However, i still get this error for the COM module. Even it if do a iisreset or reboot it gets the error described above. I have to change the classids in the com module and rename it then it can load it again
for about 24hours and then the same error happens. At this point i can reload the original one.
There are no events in the eventvwr.
May 29, 2008 07:18 AMfirstname.lastname@example.org|LINK
You're probably referring to the COM+ rollup, which is included in the SP. This is unlikely an IIS issue as much as the COM object needing to be updated. Have you contacted whomever created the object?
May 29, 2008 08:23 AM|tomkmvp|LINK
That also looks like a very uncommon error ... what does the component do?
May 29, 2008 11:39 AM|pfelsted|LINK
Thanks for the replies.
It is an in house COM module I wrote. It has be running on about 6 other IIS servers for months with no trouble just this new machine. The constructor for this class has nothing in it. It runs for about a day then just stops with this error. It's like
there is a crash or a hang that is messing up IIS and the web services exentions. But with no event errors I can not tell what is going on. Is there anyway to log the COM system?
The specific class that i start getting this error with is justs a wrapper for a few static methods out of another vb class. One of these methods will create a connection to a database and return it. I did this so that some Classic ASP code can call into