ADOVB Persistent recordset and Win2003 not working

ADOVB Persistent recordset and Win2003 not working

am 15.11.2006 00:48:46 von Darren Peck

I have a saved or persistent recordset
(http://www.MoneyFlowDS.com/holidays.rst) that I am trying to open with
either ASP or VBScript (using a .wsf file). When the .rst file was on
my Win2000 server, it worked fine, when I moved it to my Win2003 Server
(where it is now in the URL referenced above), it no longer works, I
get the error "The connection cannot be used to perform this operation.
It is either closed or invalid in this context.", code 800A0E7D. Here's
the vbscript file:

'*****************************'
' This one DOES NOT work, it is going to a Win2003 Server '
cHolidaysFile = "http://www.MoneyflowDS.com/Holidays.rst"

' This one DOES work, it is going to the old Win2000 Server. '
' Un-comment this one to see it work! '
'cHolidaysFile = "http://204.10.140.84/Holidays.rst"

set rHolidays = CreateObject("ADODB.RecordSet")
rHolidays.Open cHolidaysFile

WScript.Echo(cHolidaysFile & " is open")
rHolidays.Close
set rHolidays = Nothing
'******************************'

I'm guessing that there is a setting, probably something that is "more
secure", on the Win2003 server that I need to adjust to get this to
work. Can anyone help me?

Re: ADOVB Persistent recordset and Win2003 not working

am 16.11.2006 04:40:00 von mmcginty

"Darren Peck" wrote in message
news:1163548126.866164.203180@i42g2000cwa.googlegroups.com.. .
>I have a saved or persistent recordset
> (http://www.MoneyFlowDS.com/holidays.rst) that I am trying to open with
> either ASP or VBScript (using a .wsf file). When the .rst file was on
> my Win2000 server, it worked fine, when I moved it to my Win2003 Server
> (where it is now in the URL referenced above), it no longer works, I
> get the error "The connection cannot be used to perform this operation.
> It is either closed or invalid in this context.", code 800A0E7D. Here's
> the vbscript file:

Windows Server 2003 returns HTTP status 404 when a file is requested, if the
file's MIME type is not defined in its configuration (HTTP Headers tab in
IIS properties.) What the correct MIME type for that might be, I'm not
sure, but that is the core issue.


-Mark



> '*****************************'
> ' This one DOES NOT work, it is going to a Win2003 Server '
> cHolidaysFile = "http://www.MoneyflowDS.com/Holidays.rst"
>
> ' This one DOES work, it is going to the old Win2000 Server. '
> ' Un-comment this one to see it work! '
> 'cHolidaysFile = "http://204.10.140.84/Holidays.rst"
>
> set rHolidays = CreateObject("ADODB.RecordSet")
> rHolidays.Open cHolidaysFile
>
> WScript.Echo(cHolidaysFile & " is open")
> rHolidays.Close
> set rHolidays = Nothing
> '******************************'
>
> I'm guessing that there is a setting, probably something that is "more
> secure", on the Win2003 server that I need to adjust to get this to
> work. Can anyone help me?
>

Re: ADOVB Persistent recordset and Win2003 not working

am 16.11.2006 23:14:14 von Darren Peck

Mark,

That was EXACTLY the problem. Although my Win2000 server doesn't have
any additional MIME types registered, I went ahead and added the "rst"
extension to the MIME file types on my Win2003 server (for the MIME
type, I just put in ADODB recordset), AND IT WORKS! Thank you VERY
much.

Darren

Mark McGinty wrote:
> "Darren Peck" wrote in message
> news:1163548126.866164.203180@i42g2000cwa.googlegroups.com.. .
> >I have a saved or persistent recordset
> > (http://www.MoneyFlowDS.com/holidays.rst) that I am trying to open with
> > either ASP or VBScript (using a .wsf file). When the .rst file was on
> > my Win2000 server, it worked fine, when I moved it to my Win2003 Server
> > (where it is now in the URL referenced above), it no longer works, I
> > get the error "The connection cannot be used to perform this operation.
> > It is either closed or invalid in this context.", code 800A0E7D. Here's
> > the vbscript file:
>
> Windows Server 2003 returns HTTP status 404 when a file is requested, if the
> file's MIME type is not defined in its configuration (HTTP Headers tab in
> IIS properties.) What the correct MIME type for that might be, I'm not
> sure, but that is the core issue.
>
>
> -Mark