2. ASPRunnerPro General questions
  3. problem with IIS7 and ASPRunner 6.2?
This topic is locked

problem with IIS7 and ASPRunner 6.2?

 		4/7/2010 2:14:33 PM
ASPRunnerPro General questions
T
 tone21705 author

My company currently upgraded to ASPRunner 6.2 from 6.1. I am currently using a trial version of 6.2 (waiting on my code). When I create a project in 6.2 and upload it to a windows server 2008 box and browse to the index.htm and get redirected to the _list.asp page, I get this error:
Server Error

500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.
I have turned off Friendly HTTP messages and tried it in both Firefox and IE 6/7. Same error.

I created the exact same project with 6.1 and it works perfectly. What could be the problem?
Thank you very much and great project!

Antoni
Sergey Kornilov admin 4/7/2010

Antoni,
as a first step you need to find what's the exact error message. I guess you need to configure IIS to return error message to the browser.
You can also post your app to demo account and contact support team directly.
T
 		tone21705 author 4/8/2010

Hi,
Thank you for the always quick response.

You were right, I needed to configure IIS7 to show error messages in classic ASP.

The error I receive is:



ADODB.Connection error '800a0e7a'
Provider cannot be found. It may not be properly installed.
/NPAU/include/dbcommon.asp, line 46


It is connecting to a SQL Server 2008 box.

Following the code back from dbcommon.asp, line 43-46 has:



function db_connect()

set dbConnection = server.CreateObject("ADODB.Connection")

dbConnection.ConnectionString = strConnection

dbConnection.Open


Going into dbconnection.asp to look at strConnection:



<%

strConnection = "Provider=SQLNCLI;Server=servername;Uid=NPAU;Pwd=npau;Database=NPAU"

%>


When I input the server name/user/pw into ASPRunner right after selecting SQL Server it connects and I am able to select the proper db.
What could be wrong?
Thanks
Sergey Kornilov admin 4/8/2010

I guess the problem is that your web server doesn't have SQLNCLI (SQL Native Client) provider installed.
You can either install SQL Native Client on the server or copy and paste connection string from v6.1 project to 6.2 project.