• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SQL Server 2005 not available through the network

Z

Zucarita9000

Golden Member
I've recently installed SQL Server 2005 Standard in order to be able to use the new accounting platform our company is implementing. I'm getting a "Server not found" error while installing the client app, but the server is functioning locally.

Just now I've installed ACT! 2009 (CMS application) which installs an instance of SQL Server Express 2005. Now, THAT instance IS available through the network because I can see it using MS SQL Sever Management Studio from another PC.

So, what did I do wrong? Why isn't the SQL Server Standard instance not available?
 
The client app uses a Borland utility that need to be configured with the SQL server name, but it cannot find it. Using SQL Server Management Studio I can log on to the ACT instance (SQL Server Express) but not to the full fledged SQL Server 2005 Standard instance (wich is the one that contains the accounting's software database).
 
Can you connect remotely via SSMS? If not did you make sure TCP/IP and/or Named Pipes are enabled for that instance?
 
Yes, the Server Browser is running. I don't really know what else to look for. When I open SSMS and browse for a server, all I see in the local servers tab is the ACT instance (SQL Server Express) but NOT the instance I need. However, if I just type "localhost" in the server name field I can connect to it without problems.

If go to network servers, I can see a bunch of other machines that are also running SQL Server Express for various apps.

EDIT: When I installed SQL Server 2005 Standard I left the default instance setting. Was that wrong? Should I have renamed it?
 
Originally posted by: snikt
Is this happening all on clients or just that one? Can you ping the SQL Server by name/IP address from any clients?
Click to expand...

Yes, I can ping the server, see it on the network and browse it's shares. It's just that I cannot connect to the SQL Server.

Is there anything I need to configure after doing a standard, default install?
 
Yes, I can ping the server, see it on the network and browse it's shares. It's just that I cannot connect to the SQL Server.
Click to expand...

All of those things are totally unrelated to the SQL Browser service for that instance.
 
Originally posted by: Zucarita9000
Originally posted by: snikt
Is this happening all on clients or just that one? Can you ping the SQL Server by name/IP address from any clients?
Click to expand...

Yes, I can ping the server, see it on the network and browse it's shares. It's just that I cannot connect to the SQL Server.

Is there anything I need to configure after doing a standard, default install?
Click to expand...

So it doesn't seem like a network connectivity issue. Maybe a mis-configuration somewhere, on the server or client(s).

 
Originally posted by: snikt
Originally posted by: Zucarita9000
Originally posted by: snikt
Is this happening all on clients or just that one? Can you ping the SQL Server by name/IP address from any clients?
Click to expand...

Yes, I can ping the server, see it on the network and browse it's shares. It's just that I cannot connect to the SQL Server.

Is there anything I need to configure after doing a standard, default install?
Click to expand...

So it doesn't seem like a network connectivity issue. Maybe a mis-configuration somewhere, on the server or client(s).
Click to expand...

Exactly, is not a network problem. It's just that I'm completely lost and don't have any ideas on what else to configure.
 
what authentication are you using for that instance? might need to change it to mixed-mode authentication using studio manager (log into localhost, then right click on the instance choose properties than security, change from windows auth mode to sql server and windows auth mode). See if that helps.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top