I have been searching on this topic and trying different variations for the last 3 days and can not see what I am doing wrong.
I have a site written in Classic ASP (was written long ago, just got involved, and I know nothing about Classic ASP) that calls to a SQL database. Right now it goes through an ODBC connector to connect using this snippet of code:
Dim MM_CMS_STRING
MM_CMS_STRING = "Provider=MSDASQL; Driver={SQL Native Client}; Server=lawdata02; Database=ALG; UID=user; PWD=pass"
I am trying to migrate them to a new server. I have setup IIS on a Windows 7 Pro machine. I have successfully moved over all the files, and migrated the SQL DB to SQL Server 2012 Express. I have installed System DSN File (SQL Server) and configured that to connect to the database. When I try to use the same connection string above, I get:
An error occurred on the server when processing the URL. Please contact the system administrator.
If you are the system administrator please click here to find out more about this error.
I have gone through so many configurations, and tried to all the debugging guides I have found around the internet and I think I am super close, but brain power is low at this point. This is what my connection string looks like now:
Dim MM_CMS_STRING
MM_CMS_STRING = "Provider=SQLNCLI11;Data Source=ALG-CMS-SERVER;Initial Catalog=ALG; Integrated Security=SSPI;"
This is the error I am getting:
Microsoft SQL Server Native Client 11.0 error '80004005'
TCP Provider: No connection could be made because the target machine actively refused it.
Files and DB are all on same machine.
IIS 7.5 | Windows 7 Pro | SQL Server Express 2012 | Classic ASP | Connection String
Related
SQL Server 2008 R2 runs on Windows Server 2008 R2 in a domain and using the same
domain accounts (Windows authentication) to allow the connection between the client PCs and the SQL Server, created and ODBC source(System DSN named Renta_Equipos) which connects to the database and and the solution. Example: BD <---- DSN <---- WinForm Solution.
The Connection String is an Application.Settings:
Name: ConnectionString_RentaEquipos
Type: (Connection string)
Scope: Application
Value: DSN=Renta_Equipos
Now this is, normally the users log in without problems, but sometimes the connections gets closed for them (not all at the same time, 1-2 of 6 users experiment this) and the only way they can connect again is restarting the client's PC, it happens randomly.
Error it gaves me:
ERROR [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB] the SQL
server does not exist or access has been denied. ERROR
[01000][Microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
(Connect())
I cannot find the problem, I know nothing about configuring an SQL server nor a professional programmer (all I know is from the Internet, books and some little help from other people), so I'm guessing it might be the server, but I can't get it, everything seems to be perfect (for me)
Here is a link for the Github source code: https://github.com/DarkLS/RentaEquipos.git
The error: http://i.stack.imgur.com/O20ls.jpg
Are all 6 of your client PCs desktops? If so, do the 1-2 users whom are having issues use a wired and/or wireless connection (some of the newer desktop towers have wireless capabilities)?
If it's going as far as denying access, you might be hitting your SQL user license cap (hard to say for sure)... Might want to review your SQL Server 2008 R2 environment with your IT guys.
EDIT: Check this site
I've been trying for a few days to work out what's wrong with connecting to our SAP server from a workstation installed with a client.
My setup:
server:
Win 2008 R2
SQL Server 2008 R2
SAP B1 8.82 PL 14
Workstation:
Win 7 64bit
SQL Native Client 2008 R2 (same as on the server as recommended)
Situation:
I can see the companies\DBs from the client side but when I enter the right credentials it stalls for a few seconds then throws out the dreaded "Internal Error 1102 131-183".
Firewall has been completely turned off.
Communication is working perfectly fine on all ports.
I made sure both TCPIP and Piping have been enabled on CLICONFG.
When using Process Monitor I noticed 2 missing keys the SAP Business One.exe attempts to access but fails as they do not exist:
HKLM\SOFTWARE\Wow6432Node\SAP\SAP Manage
HKLM\SOFTWARE\Wow6432Node\Microsoft\CTF\KnownClasses
I have no idea where to get them from...
I'd appreciate all help I can get.
Thanks
Environment
Windows 7 machine running VS2012 Update 2
Server 2008 box running SQL Express 2012
Happily modifying existing Lightswitch application that connects to the SQL Server Express system using SQL Authentication. All of a sudden I start to get all sorts of funny errors (something weird happened at this point) so I stopped what I'm doing and restart both server and Win7 system.
When I now try to run/build my LS application it gets an error stating that login to the SQL Server failed because login is from an untrusted domain and windows authentication failed.
Problem is I am using SQL authentication??? I have triple checked my web.config settings and the connection string is definitely set for SQL auth. I created another "test" application, again using SQL auth and it works fine. (I compared the config files from app to app and the connection strings are identical.
In the VS IDE I have Data Connections defined to the SQL server using SQL auth and it works fine. If I do an "update" of the data source and check connection dialog it uses SQL auth and the update works fine.
But when I try to build/run the app it wants to use Windows Authentication.
(I am not using any application/screen level security in my app).
Got me stumped.
Any ideas?
I moved to a new Windows 7 PC and now I need to specify "Network Library=DBMSSOCN" in my connection string. On my old Windows 7 PC, my connection string is
Provider=SQLOLEDB.1;Persist Security Info=False;Initial Catalog=;Data Source=;User ID=;Password=" and that works just fine. However, on my new computer if I run that connection string I get the error message "[DBNMPNTW]Connection broken." I know this is the DLL for named pipes. For some reason my pc is defaulting to the named pipes dll instead of tcp.
I have a lot of old apps out there and don't want to have to change and recompile everything to work on my pc. How do I change my system to default to tcp? The only differences between the two pcs are:
Old - Windows 7 x86 New - Windows 7 x64
Old - SQL Server 2008R2 New - SQL Server 2012
Try:
Click Start -> Run
Type cliconfg
click OK
Does Named Pipes have a higher priority than TCP/IP?
Alternatively, you could disable named pipes for SQL Server. To do this:
Click Start -> Programs -> Microsoft SQL Server -> Configuration Tools -> SQL Server Configuration Manager
Expand SQL Server Network Configuration
Disable Named Pipes.
Good day StackOverFlowlers,
I´m a little stuck (really stuck) with an issue with a legacy application on my organization.
I have a Windows 7 Enterprise 64 Bit machine, Access 2000 Installed and the Legacy App (Is built with something like VB but older) The App uses System ODBC in order to connect to a SQL 2000 DataBase on a Remote Server.
I created the ODCB using C:\Windows\SysWOW64\odbcad32.exe app in order to create a System DSN. I did not use the Windows 7 because it is not visible to the Legacy App.
I tested the ODBC connection with Access and worked ok, I can access the remote database.
Then I run the legacy App as Administrator and the App can see the ODBC, but I´m getting errors on credential validation and I´m getting this error:
DIAG [08001] [Microsoft][ODBC SQL Server Driver][Multi-Protocol]SQL Server does not exist or access denied. (17)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][Multi-Protocol]ConnectionOpen (Connect()). (53)
DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)
I use Trusted Connection on the ODBC in order to validate the user by Domain Controller.
I think that the credentials are not being sent by the Legacy App to the ODBC, or something like that. I don´t have the source code of the Legacy App in order to debug the connection.
Also, I turned off the Firewall.
Any ideas??
Thanks in advance!
When you run it as administrator is it your same account elevated or is it a second account all together?
Try running Access 2000 under that same method and see if it can still access the database. You can also check the SQL server logs to see who the app is trying to authenticate as. This should help you identity where to start looking.