vbs works, asp doesn't

csmsam · #1 (**permalink**) 02-19-03, 04:40

I have a script which connects to an Exchange server, and calculates the size of a mailbox.

When I run this script as asp on my own IIS, it works. When I copy it to a front-end exchange server if fails. When I copy it to a back-end exchange server it also fails. If I run the same script as vbs is runs fine, thus I arrived at the conclusion that the problem lies in the IIS running on the Exchange servers.

The script fails on the line
"cmd.ActiveConnection = con"

The script is

<%@ Language=VBScript %>
<HTML>
<HEAD>
</HEAD>
<BODY>
<SCRIPT LANGUAGE=vbscript RUNAT=Server>

dim con
dim cmd

set con = server.createObject("ADODB.Connection")
set cmd = server.CreateObject("ADODB.Command")

con.Provider="MSDAIPP.DSO"
con.ConnectionString="User ID=test" & _
";Password=test" & _
";Data Source=http://exchangeserver" & _
".domain.co.xx/exchange/test"
con.Open
cmd.ActiveConnection = con
con.Close

set con = nothing
set cmd = nothing

</SCRIPT>

</BODY>
</HTML>

Bunce · #2 (**permalink**) 02-22-03, 02:14

Have you checked that IIS is running on the exchange server?

csmsam · #3 (**permalink**) 02-23-03, 00:48

There is IIS on the Exchange Server, only it's the default one installed while installing Exchange, so it isn't exactly the same as a regular IIS.
Do you know of anything specific to look for?

Bunce · #4 (**permalink**) 02-23-03, 03:14

Whats the actual error message? Perhaps its a permissions issue..

Cheers,
Andrew

csmsam · #5 (**permalink**) 02-23-03, 03:19

The error message is

Microsoft OLE DB Provider for Internet Publishing (0x80004005)
Unspecified error

and it occurs on the line
cmd.ActiveConnection = con

The con.open works.

Don't forget - this works fine in vbs.

Thanks,
Caroline

Bunce · #6 (**permalink**) 02-23-03, 03:25

Yes but you need to remember that by default, anonymous WEB requests run under the context of IUSR_<MachineName> local account, whereas a VBS file would run under the current user.

You may have different permissions on the machine that the script works on..

I must admit I've only connected to exchange using LDAP and not the provider you are using, however my gut feeling is that it could be a permissions issue.

Is there anywhere in exchange where you can alter permission for this type of access?

Cheers,
Andrew

Internet Services

Web Development

Digital Marketing

Consumer Tech