Home/ Questions/Q 816071
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T01:46:30+00:00

I am migrating a classic ASP web app to new servers. The database back

  • 0

I am migrating a classic ASP web app to new servers. The database back end is migrating from SQL Server 2000 to SQL Server 2008, and the app is moving from Win2000 x86 to Win2003R2 x64. I am getting the above error on every single stored procedure call within the application.

I have verified:

  • Yes, the SQL user is set up, using correct username and password
  • Yes, the SQL user has execute permissions on the stored procedures in the database
  • Yes, I have updated the TypeLib references to the new UUID
  • Yes, I have logged into the database via SSMS with the SQL user id and it can see and execute the stored procedures just fine in SSMS, but not from the web app.
  • Yes, the SQL user has the database set as its default database.

The most frustrating thing is it works fine on the DEV server, but not on the production server. I have gone through every IIS setting 5 or 6 times and the web app is set up precisely the same in both environments. The only difference is the database server name in the connection string (DEV vs prod)

EDIT: I have also tried pointing the prod web box at the dev database server and get the same error so I’m fairly sure the issue isn’t on the database side.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Are you sure that you are really connected to the instance and database you think you are (in the App)? It only takes the wrong DB in the connection string to override the default database for the user.

    Can you execute some inline SQL on the connection like:

    SELECT @@SERVERNAME AS SERVERNAME
    ,DB_NAME() AS [DB_NAME]
    ,CURRENT_USER AS [CURRENT_USER]
    • 0