• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 267
  • Last Modified:

Interdev 6.0 and IIS5.0 on Win2KPro

I Recently upgraded to Win2Kpro. I have the following problem:

All recordset design-time controls generate the same error when viewed locally - through view in browser.(Still works on the IIS4 serevr)

PAGE OUPUT:

The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot be displayed.

--------------------------------------------------------------------------------

Please try the following:

Click the Refresh button, or try again later.

Open the g35292 home page, and then look for links to the information you want.
HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services

--------------------------------------------------------------------------------

Technical Information (for support personnel)

Error Type:
ADODB.Connection (0x800A0BB9)
Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another.
/test_Local/ASP Page1.asp, line 29


Browser Type:
Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Page:
GET /test_Local/ASP Page1.asp

Time:
Wednesday, March 08, 2000, 3:25:20 PM


More information:
Microsoft Support
 

0
Manie
Asked:
Manie
  • 3
  • 2
1 Solution
 
TTomCommented:
Can we see the contents of line 29 (or a chunk of code relating to that line)?

Quick guess.

It's possible that the connection information (DNS string) was trashed by your update.

Tom
0
 
ManieAuthor Commented:
Line 29 contains the code for a "drag'n'drop" Recordset object.  As it is a GUI object I do not want to change the code - I only modify the properties of the object.

Code follows:  error line marked with (*).  BTW, if I comment out the line, the next one gives an error, and so on.

<!--#INCLUDE FILE="../_ScriptLibrary/Recordset.ASP"-->
<SCRIPT LANGUAGE="JavaScript" RUNAT="server">
function _initrsAgent()
{
      var DBConn = Server.CreateObject('ADODB.Connection');
(*)      DBConn.ConnectionTimeout = Application('BulkConn1_ConnectionTimeout');
      DBConn.CommandTimeout = Application('BulkConn1_CommandTimeout');
      DBConn.CursorLocation = Application('BulkConn1_CursorLocation');
      DBConn.Open(Application('BulkConn1_ConnectionString'), Application('BulkConn1_RuntimeUserName'), Application('BulkConn1_RuntimePassword'));
      var cmdTmp = Server.CreateObject('ADODB.Command');
      var rsTmp = Server.CreateObject('ADODB.Recordset');
      cmdTmp.ActiveConnection = DBConn;
      rsTmp.Source = cmdTmp;
      cmdTmp.CommandType = 1;
      cmdTmp.CommandTimeout = 10;
      cmdTmp.CommandText = 'SET ROWCOUNT 0 SELECT * FROM Agent';
      rsTmp.CacheSize = 10;
      rsTmp.CursorType = 3;
      rsTmp.CursorLocation = 3;
      rsTmp.LockType = 3;
      rsAgent.setRecordSource(rsTmp);
      rsAgent.open();
      if (thisPage.getState('pb_rsAgent') != null)
            rsAgent.setBookmark(thisPage.getState('pb_rsAgent'));
}
function _rsAgent_ctor()
{
      CreateRecordset('rsAgent', _initrsAgent, null);
}
function _rsAgent_dtor()
{
      rsAgent._preserveState();
      thisPage.setState('pb_rsAgent', rsAgent.getBookmark());
}
</SCRIPT>
0
 
TTomCommented:
Let's look at:

Application(BulkConn1_ConnectionTimeout) = ???

in global.asa

Tom
0
 
ManieAuthor Commented:
TTom,

Solved my problem.  Thanks for your attempts.  It worked out that when you create a project through INTERDEV, it doesn't create the local web as an application.  

Until I find the solution, the workaround is to modify the local web and set it to be an application.
I found this out when all ASP code that requires Appliactions (such as server.application) breaks with th esame error.

I reduced the point score to 100.
Respond to claim your points.
0
 
ManieAuthor Commented:
Points allocated for response.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now