Cannot Connect to SQL 2000

I recently reinstalled SQL Server and now I am unable to
create the DSN through CF Admin. The name of the SQL instance was
changed during the reinstall. I have attempted to use the new name
in CFAdmin but get the following error:
"java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver][Macromedia][SQLServer JDBC Driver]The requested instance is
either invalid or not running.
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver][Macromedia][SQLServer JDBC
Driver]The requested instance is either invalid or not running."
The instance is running and I can create a connection through
the Data Source (ODBC) tool in Admin Tools but I can set it up in
CFAdmin.
Thanks in advance for your advise!

> In any case applying the SP probably wouldn't hurt.
Yep. Patch it up, and try again.
I realise Lynda said that the computer in question is a local
PC, so
probably is not outwardly facing (ie: onto the 'net). But
this warning
could still be relevant:
A couple of years ago - long after SQL Slammer had done the
rounds, so one
might think it was no longer a problem - one of our jr
developers was
tasked with setting up a new SQL Server instance which ended
up being
outwardly facing. She didn't remember to patch it (and I -
the box was my
responsibility - forgot to check).
It took about half an hour of uptime for it to get infected,
and about
15min after that before our LAN was flattened by
virus-enabled traffic
trying to find other machines to infect. Suddenly 20-odd
people could not
work whilst we cleaned out their machines, and checked for
any number of
other infections. I was not popular that day (not least of
all with
myself!).
Always... ALWAYS... make sure your SQL Servers are fully
patched.
I would *never* attach a machine with non-patched SQL Server
even to a LAN,
let alone the outside world.
I cannot stress that enough.
Adam

Similar Messages

Cannot connect to SQL 2000 Analysis Service cube form 32bit 2010 excel

Excel 2010 32bit is running on windows 7 64bit PC. User has new PC updated from XP where there was no connection issue.
Initial Error
"The following system error occurred: No connection could be made because the target machine actively refused it"
I installed Office web component 2003 as advised in forums.
Next Error
"initialization of the data source failed. Check the database server or contact your database administrator. Make sure the external database is available, and then try the operation again. If you see this message again, create a new datasource
to connect tot he database."
I have trawled the forums for the past 2 days looking for a solution. Any help would be appreciated.
Niall

Hello,
Please check the below link.May be this can Help You
https://fawzi.wordpress.com/2013/05/15/sql-2012-analysis-services-error-no-connection-could-be-made-because-the-target-machine-actively-refused-it/

How to Connect Microsoft SQL 2000 database using JDBC

Hi all..
I want to connect Microsoft SQL 2000 database using JDBC. I want from initial steps also. (about JDBC driver & its installation)
Thankz

Just checkout the SQL Server JDBC Driver Documentation at the manfacturer's site: http://msdn2.microsoft.com/en-us/data/aa937724.aspx

SQL 2012 Linked Server connection from SQL 2000

Hi,
Does anyone know if it's possible to create a linked server connection in SQL 2000 to a SQL 2012 instance?
If so, which provider should I use?
Many Thanks,
Phil

Hi Shanky,
I'm afraid you misunderstood my Q. The above posts show how to create a linked server connection FROM SQL2012 --> SQL 2000.
I'm trying to create a linked server connection FROM SQL 2000 --> SQL 2012.
Does anyone know if it's possible?
Many Thanks,
Phil
I guess you dont read posts patiently below link ,which i also posted in my first reply, has details about the same
http://social.msdn.microsoft.com/Forums/en-US/2e02c603-e28d-49eb-b073-548c59732b5d/linked-server-from-sql2012-to-sql2000?forum=sqlsetupandupgrade
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Critical Error: Cannot Connect to SQL Server. {SQL Server} not found. Timeout expired.

Greetings,
I have been having some issues with various areas in a SharePoint 2013 farm. While working my way through a bazillion errors in the event logs, I have found the following error. It looks to be happening every hour; almost exactly 5 minutes after
every hour.
"Cannot connect to SQL Server. A_PROD_SP01 not found. Additional error information from SQL Server is included below.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
I also find, a health analyzer rule that is failing at the same time:
Availability: One or more servers is not responding.
However, there isn't any server listed in the Failing Servers section.
Any thoughts?
Thank you,
Bob

Hi Bob,
For your issue, it can be caused by that the SharePoint database access account might not have the necessary permissions to communicate with the SQL Server. Please grant correct permissions to the database access account:
You must be a member of the Farm Administrators group to perform this task.
Assign the database access account:
On the Central Administration home page, click Security and in the
General Security section click Configure service accounts.
On the Service Accounts page, in the Credential Management section, in the upper drop-down list click the correct Web application pool for your Web application.
In the Select an account for this component drop-down list, click the domain account that you want to associate with this Web application pool, or click
Register new managed account to associate a new domain account with this application pool.
Click OK to save changes.
Reference:
https://technet.microsoft.com/en-in/library/ee513066(v=office.14).aspx
http://blogs.technet.com/b/wbaer/archive/2009/10/06/intermittent-database-server-connectivity-and-microsoft-sharepoint-products-and-technologies.aspx
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Unable to Connect to SQL 2000 Instance from Windows Server 2012 environment

We have a windows server (TEST) 2012 environment , where our test SQL Server 2012 instance is hosted.
We have a different (DEV) Server (windows 2000) where a SQL Server 2000 instance is present.
When I RDP to our Windows Server 2012 box, I cannot connect to the SQL 2000 server instance from SQL Management Studio. (whereas I can connect to
the same server from my local machine which has windows 7 and SQL 2012 installed).
This is the error i see -
"A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name
is no longer available.) (.Net SqlClient Data Provider)"
When run from SQL Agent Service from TEST (A Job which tries to connect to that SQL 2000 instance to read some data using SSIS) , we get the following
error -
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionRead
(recv()).]General network error. Check your network documentation.".
The same SSIS package runs successfully from my local machine.
Please, could someone advice how to resolve this situation?

Thanks Olaf.
Its just that we have legacy systems here in our company, who, for some reason haven't upgraded their older infrastructure, whereas they have set up new Windows 2012/SQL 2012 environments for the newer sql instances where they want to transition to !
Not sure what the solution is honestly. It is affecting our timelines now. The infrastructure team needs to take a decision now, as to what to do.
I do have to add, we were able to connect to these "older" servers from our Windows 7 client machines which have SQL 2012 - both from SQL management studio & SSIS (using OLE-DB Provider for SQL Server).

BPC 7.0 Install error - Cannot connect to SQL server

Hi,
I am in the process of installing BPC 7.0 and encountered the following error after filling the "Advanced settings" details on the server info screen:
*Cannot connect SQL server.
Please check the SQL server connection or check System Admin ID to access the sql server.*
I know that the System Admin ID I provided in the previous (service type accounts) screen is correct. What am I missings? Appreciate the help asap!

BPC installation user has to be SysAdmin into SQl Server.
Also make sure that SQL Server was installed having Windows authentication enable otherwise the connection to SQL Server can not be establish.
Into Application Server (the server where you are trying to install BPC) open Management Studio and see if you can connect to SQL Server.
Are you using special ports or instances fro SQL Server?
Please make sure you are providing all these information into BPC setup.
Regards
Sorin Radulescu

2012 r2 rds deployment cannot connect to sql server after reboot

We have a ha connection broker setup with 2 connection brokers and everything was working fine up untill the servers were rebooted for updates. Now users cannot connect to thier collections and I have an error in the event log that the deployment could not
connect to the sql database.
at this point I am assume that the issue is related to security. I am able to query the database as admin from the effected servers and other services that use other databases in the same sql instance are no5 having issues.
I have checked the security group that both cb servers should be in and they are in the group and the group has sysadmin and dbo within sql
any ideas?
Please remember to mark my replies as answers if they help

Hi,
Thank you for posting in Windows Server Forum.
Can you please create the database manually with below command and verify.
PS C:\> Set-RDConnectionBrokerHighAvailability –DatabaseConnectionString
"DRIVER=SQL Server Native Client 11.0;SERVER=<SQL Server
Name>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;
DATABASE=<DB Name>" -DatabaseFilePath "C:\DbFiles\<DbName>.mdf"
-ClientAccessName "<DNS RR Name>"
Grant DBO permissions to the service account on the RDS server and try to run your wizard again.
More information.
RD Connection Broker High Availability in Windows Server 2012
http://blogs.msdn.com/b/rds/archive/2012/06/27/rd-connection-broker-high-availability-in-windows-server-2012.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Cannot connect to SQL Azure

Hello,
I have tried everything I could think of and still did not manage to connect to SQL Azure server instance I have created.
1) Using the SQL Server Management Studio 2008 R2 -
    I get: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. ...."
    I have the 1433 port allowed by my firewall (even placed a machine in the DMZ) and I have added my IP address to the SQL Azure firewall.
2) Using this app: https://onlinedemo.cerebrata.com/SQLAzureClient/default.aspx
   I get "Unable to retrieve the list of databases...."
   Now, in this case enabling the TCP port 1433 from my network is not even required as I this tools connects directly to SQL Azure. And yes, I have added the firewall rule on my SQL Azure Server.
3) Using this tool: http://hanssens.org/tools/sqlazuremanager/
   I get a message similar to what I get at 1)
The only thing that works is the "Test Connection" performed on SQL Azure site.
Can someone please help?
Regards,
Luc

I cannot connect either using that Omega tool but I have no problem from SSMS R2.
Let's try something simple: connecting from Project Houston:
Check "Allow Microsoft Services access to this database"
Go to http://sqlazurelabs.com. Click Project Houston CTP 1 on left.
When asked for data center, click the one where your db is deployed.
Agree to terms
Enter full database name - somename.database.windows.net -
along with database name, username, and password. Note: if you didn't allow Microsoft Services access to your database, you'll get an error
You should now be connected to your database.
If that worked, at least you know your database is up and running correctly. Now try connecting from SSMS R2. The parameters should be identical,
except you don't have to specify which database to connect to.

Connection using sql 2000

i try to connect t o database using sql 2000
this my code and the execptions
can anyone help me to tell me what is the right code to connect to database
package javaapplication37;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.SQLException;
import java.sql.*;
* @author ed
public class Main {
/** Creates a new instance of Main */
public Main() {
* @param args the command line arguments
public static void main(String[] args) throws SQLException {
// try {
// TODO code application logic here
//String url = "jdbc:ODBC:Northwind";
//try {
// Connection con=DriverManager.getConnection(url,"sa","remo");
// } catch (SQLException ex) {
// ex.printStackTrace();
// System.out.println("remo hi");
Connection con;
try {
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
// Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
con=DriverManager.getConnection("odbc:microsoft:sqlserver://localhost:1433;databaseName=Northwind;selectMethod=cursor");
// System.out.println("elk");
} catch (ClassNotFoundException ex) {
ex.printStackTrace();
// } catch (ClassNotFoundException ex) {
// ex.printStackTrace();
the exception is
init:
deps-jar:
compile:
Exception in thread "main" java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:545)
at java.sql.DriverManager.getConnection(DriverManager.java:193)
at javaapplication37.Main.main(Main.java:47)
Java Result: 1
debug:
BUILD SUCCESSFUL (total time: 1 second)
Message was edited by:
romee

W3hy did you give up with the type 4 driver? Why did you not use Google? Your basic question has been asked and answered repeatedly.
I will say this a JDBC-ODBC URL begins with jdbc:odbc and not just odbc though I have some doubts about the rest of the stuff you'e crammed in there.

Cannot connect to sql server after re installing IIS 6?

I re installed IIS 6, after the restart i couldn't connect to sql server engine nor seeing it when using browse for me, i was trying to install team foundation server, at first it could see that i have an sql server running after re installing IIS it can't
see it also. I'm using windows server 2003 SP2. Also i cannot remotely access it after the re installation

Just type the IP or name of the server (localhost) and try to connect.. SSRS 2005 requires IIS but how does it relate to SQL Server connection?
What error are you getting? Make sure that SQL Server is running up.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

SQLDeveloper cannot connect to SQL Server named instances

I'm trying to connect to a SQL Server 2005 named instance on my local PC but SQLDeveloper is failing to connect as there is no way to specify the named instance on the connection screen.
For comparison I set up a jdbc connection in JDeveloper and
the connection URL which works in JDeveloper is jdbc:jtds:sqlserver://127.0.0.1:8020;instance=WESTERNEUROPE
Without the instance property JDeveloper gets a connection refused

Set up the connection through SQL developer, then exit the software.
For a sqlserver database like GABRIEL\angel
Modify the URL property in the IDEConnections.xml file
<URL>jdbc:jtds:sqlserver://GABRIEL:1433;instance=angel</URL>
You cannot use Windoze authenrication, and will need a SQL Server named user to connect.

Cannot Connect to SQL 2008 Database Error

I am on Windows Server 2008 with SQL Server 2008 database and even after enabling the "TCP/IP" protocol and also "Named pipes" continue to get "EPMCFG-10368: Cannot connect to database..." error. Any additional troubleshooting steps would be greatly appreciated.

I am trying to connect to a SQL Server 2008 database. I provided the correct server name, port, db name, user and pswd. When using an ODBC connection I connect without issue. However, when trying to connect via the EPM System Configurator I get an error.

Leo cannot connect to WIN 2000 SP4 Server via AFP!

Dear folks,
I set up an PowerMac G4 MDD as a first Leopard-Test Machine for our production environment. Mac OS X 10.5 was installed on a clean HD without any old stuff on it.
My serious problem ist that this Mac cannot establish a connection to a WIN2000 Server (SP 4) via AFP.
I am able to enter cmd-K, server IP, and in the following dialogue login and password.
Instead of showing the available shares I get an error -41 (unknown error) an should contact the server admin.
Interestingly, I have absolutely no probs to connect via AFP to another Win2000 machine with SP 2 installed.
Also I tried several manipulations on the appleshare plist file I found here and in other forums. With no luck.
I have no idea anymore what else to try.
With Tiger and Panther everything is fine.
Thanks in advance for your help!
Regards,
Stefan

I have not been able to reproduce error -41, but I have been able to reproduce a failure to connect on Windows 2000 SP4.
On the windows server, make sure you are using either 'Microsoft Only', 'Apple Encrypted', or 'Apple Encrypted or Microsoft'.
You can check this by right clicking on 'My Computer', selecting 'Manage', right clicking on 'Shared Folders' under 'System Tools' and selecting 'Configure File Server for Macintosh'. It will be on that first screen that comes up.
If you just MUST use unencrypted passwords, or can't access the NT server, you can set the following and it seems to work fine.
Err:~ eb$ defaults write com.apple.AppleShareClient "afpcleartextwarn" -bool YES
Err:~ eb$ defaults write com.apple.AppleShareClient "afpcleartextallow" -bool YES

Connect to SQL 2000 and 2012

We have two interfaces. Once connects to 2000 and the other to 2012. Which JDBC drivers do I need to deploy. is it both sqljdbc.jar and sqljdbc4.jar?
Pls advice.
Thanks

Resolved.
Used sqljdbc4.jar for SQL servers 2005 onwards.
Though microsoft says JDBC driver 3.0 supports connection with 2000, we were getting errors.
As an alternative we used mssqlserver.jar, msbase.jar and msutils.jar to connect to SQL server 2000 and it works fine.
So we have more than one driver installed on pur PI system.
Thanks.

Cannot Connect to SQL 2000

Similar Messages

Maybe you are looking for