HTTP 500 error while browsing http://localhost/xmla/msxisapi.dll

HTTP 500 error while browsing http://localhost/xmla/msxisapi.dll

Post by nkunap » Wed, 09 Feb 2005 09:49:00


Hi: I have successfully installed XML Analysis Services SDK 1.1 on
windows 2000 server as described in this URL.

http://www.yqcomputer.com/

I have applied XML A SP3 and my SQL Server 2000 has sp3a installed.
After, I created the virtual directory in IIS 5.1 and try to browse
http://localhost/xmla/msxisapi.dll, I get a HTTP 500 error instead of
getting the XML message as described in the paper. I have spent the
whole day trying to figure this but was unable to get a suitable
solution.

In the event log, I get this error when I try to browse the above URL.

DCOM got error "Overlapped I/O operation is in progress. " and was
unable to logon .\IWAM_SQL in order to run the server:
 
 
 

HTTP 500 error while browsing http://localhost/xmla/msxisapi.dll

Post by Akshai Mir » Thu, 10 Feb 2005 05:17:13

Can you try switching the virtual directory to use Low Isolation instead of
Medium/High? I'm not sure what the cause is, but it looks like your
out-of-process COM host has some problem...

Thanks,
Akshai


http://www.yqcomputer.com/

 
 
 

HTTP 500 error while browsing http://localhost/xmla/msxisapi.dll

Post by nkunap » Thu, 10 Feb 2005 06:01:49

Akshai,
Thanks a lot. Changing the security to low worked. How will this
effect the security of our application? We have this server anyway
inside the firewall?

Thankyou for your time.

Thanks,
Narendra
 
 
 

HTTP 500 error while browsing http://localhost/xmla/msxisapi.dll

Post by Akshai Mir » Sat, 12 Feb 2005 05:19:28

Low isolation is a little faster, but the risk is that if the ISAPI DLL
crashes for any reason it will bring down IIS and you will need to restart
it. Medium/High isolation applications run outside the inetinfo.exe process
and therefore application errors in them do not affect IIS.

You could try to fix the Isolation problem as well but I can't offer much
help there -- perhaps searching the IIS newsgroups may find you an answer or
you could try posting a question to one of them.

Thanks,
Akshai