April 10, 2009 at 12:21 pm
Hi,
My client has 2 servers running Windows Server 2003 R2.
They already have SQL 2005 installed.
On the first (named FS02) I ran SQLEXPR32 and created the SQLExpress instance.
Attached my database, which I could see through SSMSE.
However, when I tried to login through my VB6 programme, it was unable to find the instance.
Came back with the SQL login screen with (local) in the text box.
When I clicked on the down arrow to view the available servers, it showed only FS02 (and the two on the other server) but not FS02\SQLEXPRESS.
So I did the same exercise on the other server (TS01)
There was already an SQLEXPRESS instance so I changed the name from default to SBSRENT.
Attached the database and could see the tables OK
This time when I tried to login through my programme, I got the error message "SQL Server doesn't exist or access denied"
Firewall, I thought. Port 1433, I thought.
Went to Control Panel, and Firewall - came back with a message something to the order that the process was being used by some higher entity!!
I presume this is to do with Windows Server 2003's security settings . . .
Could you please give me some idea as to what settings to look at, or what to allow?
Many thanks,
Tony Pitwood (pitters)
April 11, 2009 at 10:54 am
Few things come to mind ...
1) Express edition does not allow remote connections by default; you must enable it.
2) If you already have an instance running on serer your second instance will not get port 1433; SQL Server by default assigns port dynamically. If you connect to local server and check the error logs for SQL Server you will see what port it is listing on.
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
April 11, 2009 at 12:12 pm
Hi
In addition you have to enable TCP/IP in Configuration Manager. By default only shared memory is enabled.
Edited: Maybe you have to restart the service after that.
Greets
Flo
April 11, 2009 at 3:04 pm
I think I should add that Win2003 SP2 fixed many MDAC issues so I think you need to make sure you are running at least Win2003 SP2 in your installation.
http://support.microsoft.com/default.aspx?scid=kb;en-us;328306
Kind regards,
Gift Peddie
April 22, 2009 at 12:07 pm
Hi guys,
I tried doing this over the phone, but it was impossible!
So here I am back in Swaziland . . .
The servers are both set for remote connections, TCP-IP and Browser and running Win2003 SP2.
We have removed the instances and reinstalled them.
The databases are linked and the tables visible in Management Server, and we can link in through my VB6 programme running on the server.
But we cannot link in through my VB6 programme from the workstations. The SQL login screen does not show the instance that we are looking for - SBSFS02\SBSRENT.
It does seem to be a Win2003 security issue.
We have tried setting the permissions in Windows Explorer, first on the whole Rent folder, and then on the SBS.mdf database but to no avail.
Any suggestions would be most gratefully received.
Regards
Pitters
April 22, 2009 at 12:23 pm
SQL Server Express in Winform application allows only local connection no remote connection by default, and if you connected only MDF it maybe a user instance which is a single user database that can only be used locally. I think you need to install the Express with Advanced services and also install management studio and configure both Windows and SQL authentication and add all your users manually before connecting the application with Data Link property in VS6.
Kind regards,
Gift Peddie
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply