LDAP Query - Unspecified Error

[creed1]

I have created an ASP page to execute an LDAP query that works sometimes, but not all of the time. When it does not work, it returns "unspecified error" and references the line of code where the query is being executed (oConn.Execute). Within IIS, the page is configured to use only Basic Authentication and MDAC 2.8 is installed on the server.

After rebooting the server, the ASP page may work or it may not work...anybody's guess. Without modifying the ASP page at all and without changing any server settings, I can get it to work again either by repeatedly restarting the

http://WWW service

or rebooting countless times. Eventually it just starts working again.

I also recreated the ASP page as a .vbs script. The .vbs script always runs perfectly from server, even when the ASP page refuses to work.

Any ideas?

 

[anonymiss]

Strangly enough I have the exact same problem. Why in this case I have no idee. If you come across a solution please post it. In my environment I use NTFS authentication. The system is running fine except when the Server is rebooted. The only solution so far is to
*Temp switch to Basic Authentication.
*Reboot IIS Services (

http://www service

etc.)
*I'm able to log in to the site.
*Switch back to NTFS authentication
*Reboot IIS services
*System is working fine
I've found some event errors on the server that is running the system after rebooting. I'm not sure if this is the reason why it has difficulties maybe you could try it and see what happens. Try the first link this seems closer to my error on the server than any other errors.

*

http://support.microsoft.com/default.aspx?scid=kb;en-us;297519&Product=iis50

*

http://support.microsoft.com/default.aspx?scid=kb;en-us;255770&Product=iis50

Let me know how it goes.

 

[creed1]

Unfortunately, I never did track down the cause of this problem. I talked to other people at my company and found that they had the same problem. They had found that by compiling the exact same query in a Visual Basic DLL and calling the DLL from ASP, the problem disappeared. I tried it and the problem has not appeared since.