• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 428
  • Last Modified:

Can't see databases on remote SQL server since upgrading to MS Server 2008

good morning

We run a student management application called ICAS that uses a Borland system to connect to a remote SQL server on the lan. Problem is since we upgraded our server from 2005 to 2008 we can't see the databases anymore. The wizard we use to connect our PC's to the datbase see the sql server just fine but we can't browse the databases.

I have switched off the firewall and it is still not visible so I assume it is a service or setting within the new SQl server that needs to change?

If I manually edit the config files of the application to point to the database name it works so the connection is open but the browsing is not working. the problem is the people do their own installtions and are not always tech savvy so we can't expect them to edit their config files manually.


Here are screenshots:

Search for Server:
Search for DB from application
Next page after server is found search for DB to connect to:
Next page after server is found search for DB to connect to
0
QuintusSmit
Asked:
QuintusSmit
3 Solutions
 
jogosCommented:
Checked the permissions of hte login where you want to login with?
0
 
Deepak ChauhanSQL Server DBACommented:
Hi,

After upgrade sometime it is possible that sql server browser service is disable pelase check it.
2. check tcp ip is enable in sql sever network configuration.
3.you can use ip address in place of server name.

Hope so it may be work for you..
0
 
QuintusSmitAuthor Commented:
Hi

Are the browsing and log on permissions separate? The reason I ask is the login I use can access the database if I specifically point it it tot he right name but I can t browse all available databases.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Eugene ZCommented:
can you ping this sql server from the box where from you setup?
if 'not' - open port
are you using service account for setup?
if 'yes' can ypu login withis account via SSMS on this sql server and see DB? if not permissions
0
 
Ramesh Babu VavillaCommented:
it looks like the login credential error for a database,
you can resolve this
0
 
QuintusSmitAuthor Commented:
everyone who said permissions - thank you, turns out that was it.

Long explanation for those interested:

The application we use has a master client running on the server that connects to the database. It seems this is how they control their licensing. Client applications on the network connects to this master, authenticates and then get the data from the sql server. The master application uses a special login and that one did not have the required permissions.

everything working now
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now