Just the other day I have not been able to connect to SQL Server 2005 Express Edition. NOTHING has changed. All I have noticed is that in the Surface Area Configurator the Local Connections only radio button it selected. So I try selecting the Remote radio button and Apply and Ok and then exit the Surface Area Configurator program and then come back in again and the Local Only is selected.
Is this normal behavior? Is Remote connections allowed or not? How verify?
Thanks.
hi,
do you mean you set the "Allow remote connections" setting and suddenly (the other day) it turned it OFF by magic? and since then (the other day) you are no longer able to enable "remote connections"?
please verify via the SQL Server Configuration Manager you do have a network protocol enabled, restart the SQL Server engine service and, via SAC check remote connections are enabled..
regards
|||TCP/IP and Shared memory are enabled, and the engine and browser are running.
Remote connections where working, so yes the other day all stopped!
When I start up SAC the Local Only radio button is enabled. So I enabled remote and applied and ok'd.
Come back into SAC again and the Local Only radio button is enabled.
Is this proper behavior, meaning the program never saves the setting?
|||hi,
Expressman wrote:
Is this proper behavior, meaning the program never saves the setting?
actually not.. did you try restarting the service?
regards
|||Yes I restart the engine and browser!
I wonder if there could be a virus or hack out now doing it?!
When installing 2005 Express Edition does it associate the
ip address with the database even though ya used a name?
I installed the MS SSEUtil program.
'sseutil - listsrv' command *without quotes' doesn't show any server running. lolol
Yet my program can access the database using the 'computername and instance name'.
Any ideas?
Could a system service not be running?
|||hi,
I installed the MS SSEUtil program.
'sseutil - listsrv' command *without quotes' doesn't show any server running. lolol
Yet my program can access the database using the 'computername and instance name'.
Any ideas?
Could a system service not be running?
you are probably using a "User Instance"... User Instances do not allow remote connections..
have a look at http://msdn.microsoft.com/sql/default.aspx?pull=/library/en-us/dnsse/html/sqlexpuserinst.asp for further info about this feature..
regards
|||My new and my old applications used to work remotely without problems.
Both could connect using the server name or ip address.
Now neither one works now, meaning they can't connect.
Message is that the server doesn't exist.
I can only connect using the server name now, NOT the ip address.
I even tried connection with fire wall off. Buggers!
|||Well I re-installed the database and all works. Thanks to all helping.
Expressman wrote: