August 3, 2005 at 12:49 am
Is there a compatability issue trying to connect to a 64-bit SQL Server via IIS 5?
It's just that it just doesn't want to make the MDAC connection.
August 8, 2005 at 8:00 am
This was removed by the editor as SPAM
August 8, 2005 at 9:34 am
There shouldn't be any issues that are related to the 64bit platform since IIS doesn't "know" that it's talking to a 64bit machine, it just connects to SQL Server.
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
August 8, 2005 at 2:26 pm
Are you getting any specific error message?
August 8, 2005 at 4:27 pm
There's no error message, the ASP code tries to make the connection and then just hangs.
August 9, 2005 at 11:22 am
Nick,
I replied yesterday at the same postage on 2005 part of the forum with the following, you just replied on part of the question, but take a look at network libraries. My yesterday's post:
............Please describe the connection string. Also, no error message is posted where? Is it the web page that don't show error message or is it something else?
You may find helpful http://www.connectionstrings.com
Try to change the type of connection string: ODBC, OLEDB via TCP/IP, OLEDB via Named Pipes
Did you try to use Query Analyzer? Can you connect using Enterprise Manager? What is you Client network Utility is set up to: Named Pipes or TCP/IP by default? Did you create Client Network Utility alias?
Can you connect from VBscript? From MS Access?
How Firewall is implemented in your company? Ask your network admin check Firewall log for dropped connections.
Check Server Network Utility what port is used for SQL Server. Check what Protocols are enabled.
Yelena
Regards,Yelena Varsha
August 9, 2005 at 7:34 pm
TCPIP (port 1433) and Named pipes are the enabled protocols.
There is no problem connecting to the server with other applications, only via IIS. The connections string if fine, it's set up in a file and read in by a COM object installed on the server. That way we can change the server easily.
August 10, 2005 at 1:14 am
But somewhere there must be an error message swallowed, most probably in the COM object then. If you looked for that it migt be easier to understand what is failing.
Can you use those other applications from from the machine where IIS is running to connect to the server?
How do you refer to the server in the connection string?
August 10, 2005 at 1:17 am
The COM object isn't swallowing the error code, it just cannot connect to the server. It reaches the line to connect then never returns.
The problem is not with the connection string.
August 10, 2005 at 1:28 am
Ok, so break down the problem then. Create a simple VBScript file on the server running IIS and try to connect to the server. See where that goes.
August 10, 2005 at 4:34 pm
Nick,
Check the identity.
When you run anything including VB script you are mostly is who you are (login name) unless specified explicitly. When you connect through IIS it is how IIS web site is set up, for example, could be IUSR_MachineName.
Is IIS and SQL machines are different servers? Then it should be domain or SQL credentials that leave IIS machine.
Did you check Security log on both servers for the time you try to run script?
Yelena
Regards,Yelena Varsha
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply