Connection Issues To Report Services

Hello all,

I just installed the SQL 2k5 standard suite of services on a w2k3 enterprise edition server. All went well except for the connection to the reporting server. I get the error below.

"No connection could be made because the target machine actively refused it"

I can't seem to find any information on this error and have no clue where to even start. I've done 10+ installations of this software on various machines and have not encountered this error on any of them.

I have uninstalled, then reinstalled the reporting services and still no solution. All connection attempts are being made on the actual server, not from a desktop. sp1 for sql 2k5 is also installed, if that helps.

Windows Firewall is off.

What web searches I've done have turned up nothing useful. I'm pretty good at figuring this stuff out but this error provides very little of any use.

Anyone out there have any ideas?

Thanks in advance,

Greg

Have you seen this page: http://www.sqljunkies.com/WebLog/edwardm/ ?|||

First, thanks for the link. I'll make note of the ports used by SSAS and some of the other information in there.

I did figure this out, though. Not a very scientific approach so I'll have to run into this problem again to verify but, at a minimum, backing up the encryption key from within Reporting Services Configuration seemed to do the trick. I had a few other things out of whack, too.

At one point, the Backup option was disabled, but disabling "Web Server and HTTP Access" via SQL Server Surface Area Configuration -> Surface Area Configuration for Feature -> Reporting Services enabled the Backup button (kind of a round-about way of making that happen).

After backing up the encryption key, I enabled that option and could connect after that. Problem Solved!

This was further complicated by the fact that the reporting services install didn't conform to some "default" system configuration and performed only a "files-only" install. I really didn't pay that much attention during the install and the difference never really registered in my mind. So, I had to manually configure the reporting server (web directories, db connections, dbs and all).

So, chalk this up to experience and I'll know the next time I run into this.

Other things I addressed, but I'm not sure were relevant were:

the state of the IIS Admin and WWW publishing services (these were stopped and in manual mode during the install - I would think the install would start these if needed)

The execution permissions and application protection modes of the reporting server virtual directories (these were different on the problem installation than a "default" installation - an install on another machine that did work fine)

I don't think I needed to do the reporting services re-install.

When creating the databases manually, I ended up having to do that with scripts. For some reason, the database creation was timing out. The creation of the two databases was ok, but the reporting server temp db did not have any objects in it (no tables, views, etc).

There are a myriad of other things, but I'm almost certain these weren't relevant. All-in-all, a hassle.

Greg

|||Greg: Thanks for your post. I have a problem getting SSRS to work on one of my servers, too. I posted on Sunday:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1215786&SiteID=1
but no one answered. In my case, the local SSRS does not even appear in the list of servers to initialize, within the RS Config Manager. When I installed SSRS, I got the message "Reporting Services was installed, but not configured". This was on a reinstall of SQL05 needed to place the files on a drive other than C:

I will see if backing up the key fixes my problem, next time I'm at that site.|||I'm back at the server with the problem. When I run RS Config Mgr, the button to back up the encryption key is disabled. The only enabled buttons on that page are the 'Restore' button, and the 'Delete' (delete encrypted content) button.

I tried disabling HTTP and Web Access using the Surface Area tool, but the 'Backup' button is still disabled.

Any ideas on how to diagnose and fix this?|||

Hmm. That's what I did. One other thing you might try is deleting the encrypted content. At some point in my troubleshooting process, I pressed that button. I would assume that if encrypted content did exist, and you didn't have the proper encryption key to restore from, the encrypted content would be un-accessible (that's rather obvious). I was comfortable deleting encrypted content because the installation was new and there was nothing to lose.

After doing that, you could then go throught the HTTP and Web Access routine again.

|||No luck for me. Could not get the 'Backup' button enabled on the Encryption Key page. I found in the event log I'm getting EventID 7000 from the RS Service saying "...cannot connect to the report server database". I tried scripting out the DB creation and running that separately. The script ran without errors, but I still get the connection failure event.

I tried running "rsconfig.exe -t -c -d SSRS -a windows -s mssqlserver", where SSRS is my RS db name and mssqlserver is the SQL Server instance name (the default instance), and it came back with "The command completed successfully"

Now since running rsconfig, in the GUI version, RS Configuration Mgr, I'm getting error popups saying it can't connect to SQL Server at all. The popups say it was trying to connect using named pipes. I went to the Surface Area tool and enabled named pipes on remote connections, but RS Config Mgr still can't connect.

It seems like my installation is hosed. I thought Crystal Enterprise was hard to use, but this SSRS is worse! I'm open to suggestions. Does anyone know a reliable way to configure the db connection for Reporting Services?|||I uninstalled and reinstalled the Reporting Services components. This at least allowed RS Config Mgr to connect to SQL Server. However, when I attempt to create a new database for RS, each step succeeds except the last one. For the "Setting Connection Info for the Reporting Server" task, there

was a yellow '!', with the explanation, "Although saving the database

connection succeeded, the report server cannot access internal

information about this deployment to determine if the current

configuration is valid for this edition. ..." The RS Service is still logging errors in the event log saying it cannot connect. I give up.

connection issue with enterprise manager but works with management studio

Hi,

I have an interesting scenario.

I have a SQL Server 2000 Standard Edition instance running on Computer A. I'm trying to access it through computers B and C.

Computer B has Sql Server 2005 Express Edition installed and I was able to use its Management Studio and
connect to instance on Computer A.

Computer C has SQL Server 2000 Standard Edition installed. When I try to connect to the instance on Computer A,
I get connection failed message.

I checked some settings. Both TCP/IP and Named pipes are enabled on the instance in A. The TCP/IP port is set to 1433 for
both client and server.

Please give me some ideas as to how I can solve this problem.

-Thanks

What is the error message that is displayed?|||I am assuming all three are on the same network then it is a simple right click at the top of Management Studio and register the 2000 then it becomes local to you. I have registered 68 7/2000 in one box so it works . Hope this helps.|||

The error said something like

Invalid Connection.ConnetionOpen(Invalid Instance)

|||

I figured it out.

Both A and C had Sql Server 2000 instances. When you try to connect to one Sql Server 2000 instance from another, Enterprise Manager automatically sets "Dynamically determine port" option and hence the connection fails. What you can do is use the Client Network Utility in C and create a new TCP/IP alias and uncheck the "dynamically determine port" option and manually set it to 1433. Then u can use Enterprise Manager in C and select the new alias that you created and finish registering the 2000 instance from A.

Thanks for your replies.

|||

shiversticks:

I figured it out.

Both A and C had Sql Server 2000 instances. When you try to connect to one Sql Server 2000 instance from another, Enterprise Manager automatically sets "Dynamically determine port" option and hence the connection fails. What you can do is use the Client Network Utility in C and create a new TCP/IP alias and uncheck the "dynamically determine port" option and manually set it to 1433. Then u can use Enterprise Manager in C and select the new alias that you created and finish registering the 2000 instance from A.

Thanks for your replies.

(on the same network then it is a simple right click at the top of Management Studio and register the 2000 then it becomes local to you. I have registered 68 7/2000 in one box so it works )

For the reference of future readers of this thread you just right click and register the other SQL Server as I originally posted and leave your port setings alone in eigth years I have not had reason to touch port settings it is not needed. Port settings could lead to SQL injection attacks.

connection history to SQL server?

Is there any way to see in Enterprise Manager a history of
connections (also via Enterprise Manager) to a db? I'm
trying to track down connections to our db that were done
by a consultant remotely through Enterprise Manager via
the Internet. The consultant had direct access and didn't
need to log onto our domain.
Thanks.Not unless you had SQL login auditing set to All or are auditing security
events on the server, in which case you should be able to see logons in the
NT Security event log
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Brian" <anonymous@.discussions.microsoft.com> wrote in message
news:09f301c3b372$868347a0$a001280a@.phx.gbl...
Is there any way to see in Enterprise Manager a history of
connections (also via Enterprise Manager) to a db? I'm
trying to track down connections to our db that were done
by a consultant remotely through Enterprise Manager via
the Internet. The consultant had direct access and didn't
need to log onto our domain.
Thanks.|||OK, so if I have SQL login auditing set to All where would
I see the events? In the server event log or somewhere in
Enterprise Manager?
>--Original Message--
>Not unless you had SQL login auditing set to All or are
auditing security
>events on the server, in which case you should be able to
see logons in the
>NT Security event log
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Brian" <anonymous@.discussions.microsoft.com> wrote in
message
>news:09f301c3b372$868347a0$a001280a@.phx.gbl...
>Is there any way to see in Enterprise Manager a history of
>connections (also via Enterprise Manager) to a db? I'm
>trying to track down connections to our db that were done
>by a consultant remotely through Enterprise Manager via
>the Internet. The consultant had direct access and didn't
>need to log onto our domain.
>Thanks.
>
>.
>|||In the SQL Error log (In Enterprise Manager this will be in the Management
subfolder for a server)
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Brian" <anonymous@.discussions.microsoft.com> wrote in message
news:660601c3b377$eb660e00$a601280a@.phx.gbl...
OK, so if I have SQL login auditing set to All where would
I see the events? In the server event log or somewhere in
Enterprise Manager?
>--Original Message--
>Not unless you had SQL login auditing set to All or are
auditing security
>events on the server, in which case you should be able to
see logons in the
>NT Security event log
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Brian" <anonymous@.discussions.microsoft.com> wrote in
message
>news:09f301c3b372$868347a0$a001280a@.phx.gbl...
>Is there any way to see in Enterprise Manager a history of
>connections (also via Enterprise Manager) to a db? I'm
>trying to track down connections to our db that were done
>by a consultant remotely through Enterprise Manager via
>the Internet. The consultant had direct access and didn't
>need to log onto our domain.
>Thanks.
>
>.
>|||Jasper,
Thanks for your responses. It didn't help me out, but I
had SQL login auditing set to Success (not All). When I
changed it to Success, I get this in the error
log "Configuration option 'show advanced options' changed
from 1 to 1. Run the RECONFIGURE statement to install..",
so I'm thinking something else is going on I have to
resolve.
I still need to catch our consultant connecting to the
server without first checking with us (which they are
supposed to do).
Brian
>--Original Message--
>In the SQL Error log (In Enterprise Manager this will be
in the Management
>subfolder for a server)
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Brian" <anonymous@.discussions.microsoft.com> wrote in
message
>news:660601c3b377$eb660e00$a601280a@.phx.gbl...
>OK, so if I have SQL login auditing set to All where would
>I see the events? In the server event log or somewhere in
>Enterprise Manager?
>>--Original Message--
>>Not unless you had SQL login auditing set to All or are
>auditing security
>>events on the server, in which case you should be able to
>see logons in the
>>NT Security event log
>>--
>>HTH
>>Jasper Smith (SQL Server MVP)
>>I support PASS - the definitive, global
>>community for SQL Server professionals -
>>http://www.sqlpass.org
>>"Brian" <anonymous@.discussions.microsoft.com> wrote in
>message
>>news:09f301c3b372$868347a0$a001280a@.phx.gbl...
>>Is there any way to see in Enterprise Manager a history
of
>>connections (also via Enterprise Manager) to a db? I'm
>>trying to track down connections to our db that were done
>>by a consultant remotely through Enterprise Manager via
>>the Internet. The consultant had direct access and
didn't
>>need to log onto our domain.
>>Thanks.
>>
>>.
>
>.
>|||Yes, I should have mentioned, it's one of the options that requires a SQL
Service restart (don't know how practical that is for you). Another option
would be to use a server side trace capturing the audit login and logout
events. If they have a specific login, you can filter on that also.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:122401c3b37a$6ed460a0$a501280a@.phx.gbl...
Jasper,
Thanks for your responses. It didn't help me out, but I
had SQL login auditing set to Success (not All). When I
changed it to Success, I get this in the error
log "Configuration option 'show advanced options' changed
from 1 to 1. Run the RECONFIGURE statement to install..",
so I'm thinking something else is going on I have to
resolve.
I still need to catch our consultant connecting to the
server without first checking with us (which they are
supposed to do).
Brian
>--Original Message--
>In the SQL Error log (In Enterprise Manager this will be
in the Management
>subfolder for a server)
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Brian" <anonymous@.discussions.microsoft.com> wrote in
message
>news:660601c3b377$eb660e00$a601280a@.phx.gbl...
>OK, so if I have SQL login auditing set to All where would
>I see the events? In the server event log or somewhere in
>Enterprise Manager?
>>--Original Message--
>>Not unless you had SQL login auditing set to All or are
>auditing security
>>events on the server, in which case you should be able to
>see logons in the
>>NT Security event log
>>--
>>HTH
>>Jasper Smith (SQL Server MVP)
>>I support PASS - the definitive, global
>>community for SQL Server professionals -
>>http://www.sqlpass.org
>>"Brian" <anonymous@.discussions.microsoft.com> wrote in
>message
>>news:09f301c3b372$868347a0$a001280a@.phx.gbl...
>>Is there any way to see in Enterprise Manager a history
of
>>connections (also via Enterprise Manager) to a db? I'm
>>trying to track down connections to our db that were done
>>by a consultant remotely through Enterprise Manager via
>>the Internet. The consultant had direct access and
didn't
>>need to log onto our domain.
>>Thanks.
>>
>>.
>
>.
>

connection failure

Hi all,
Everything is fine until today.
I have two instances(both msde databases, but I have enterprise manager and
analyser installed) on my computer one instance is mssql and the other is
mssql$netsdk (asp.net starter kit database)
somehow the connection to mssql$netsdk is failed which display in enterprise
manager.
So I removed the origianl server registration and start a new one, I type
"BETTYPC\NETSDK" as server and using windows authentication when doing the
registration, but the message display at the last step:
sql server registration failed because of connection failure displayed
below:sqldumpexceptionhandler :process 53 generated a fatal exception
c0000005 EXCEPTION_ACCESS_VIOLATION, sql server is terminating this process.
what's the problem?
Can you help and I am desperated
Betty
Hi Bettys,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you are not able to connect the SQL
Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
If I have misunderstood your concern, please feel free to point it out.
AV errors could be caused by various reasons, please perform the steps
below and let me know the result
1. Check the log file of NETSDK instance, make sure whether the instance
was started correctly.
Defautly, the log will be located at C:\Program Files\Microsoft SQL
Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
v-mingqc@.ONLINEmicrosoft.com if you have concerns on security. (Note that
REMOVE ONLINE in my email address before you click SEND)
2. Is it possible to connect the instance via OSQL and Query Analyzer?
3. Is it possible for you to connect via SQL Authentication?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael,
Thank you, this is the first post on this forum. I didn't know what went
wrong. The only thing I can do is googling. Then it came to my mind that I
can stop the mssql@.netsdk sql server then and I restarted. It just started
and stopped again somehow. And then I have to restart the computer. After
that I saw both instances have sqlservr.exe process. This time I register the
server again and it looks fine. Connection is OK.
(I didn't try to use osql and did try to use sql authentication, but when I
supplied one userID and password to this server, this password is set up to a
database on this server, it should be OK right? it didn't work either.)
If you can tell what was going on, that will be great.
Here is the paste from errorLog:
2006-02-02 13:12:54.28 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2006-02-02 13:12:54.28 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-02-02 13:12:54.28 server All rights reserved.
2006-02-02 13:12:54.28 server Server Process ID is 2988.
2006-02-02 13:12:54.28 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2006-02-02 13:12:54.32 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-02-02 13:12:54.50 server SQL Server configured for thread mode
processing.
2006-02-02 13:12:54.50 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-02-02 13:12:54.52 spid4 Starting up database 'master'.
2006-02-02 13:12:54.57 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-02-02 13:12:54.57 spid5 Starting up database 'model'.
2006-02-02 13:12:54.57 spid4 Server name is 'BETTYPC\NETSDK'.
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 4
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 5
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 6
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 7
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 8
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 9
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 10
2006-02-02 13:12:54.57 spid4 Skipping startup of clean database id 11
2006-02-02 13:12:54.57 spid4 Starting up database 'subway'.
2006-02-02 13:12:54.66 spid5 Clearing tempdb database.
2006-02-02 13:12:55.72 server SQL server listening on .
2006-02-02 13:12:55.72 server Error: 17826, Severity: 18, State: 1
2006-02-02 13:12:55.72 server Could not set up Net-Library 'SSNETLIB'..
2006-02-02 13:12:55.72 server Unable to load any netlibs.
2006-02-02 13:12:55.72 server SQL Server could not spawn FRunCM thread.
Here is the sqldump file
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 8.00.760
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Betty
"Michael Cheng [MSFT]" wrote:

> Hi Bettys,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you are not able to connect the SQL
> Server named instance NETSDK with error message EXCEPTION_ACCESS_VIOLATION.
> If I have misunderstood your concern, please feel free to point it out.
> AV errors could be caused by various reasons, please perform the steps
> below and let me know the result
> 1. Check the log file of NETSDK instance, make sure whether the instance
> was started correctly.
> Defautly, the log will be located at C:\Program Files\Microsoft SQL
> Server\MSSQL$NETSDK\log, you may paste them here or send to me directly
>if you have concerns on security. (Note that
> REMOVE ONLINE in my email address before you click SEND)
> 2. Is it possible to connect the instance via OSQL and Query Analyzer?
> 3. Is it possible for you to connect via SQL Authentication?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Hi Betty,
It seems your SQL Server is not stable. From the startup log, I believe
something internal is wrong. We may noticed "netlibs" is not loaded and
Dump file were also generated.
Although you could register SQL Server now, I would recommend you backup
all the data in this instnace and perform a reinstallation of NETSDK
instance. You may follow the link below to perform a complete uninstall
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/kb/290991
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

connection failure

Hi,
We have just installed sql server 8
while using the enterprise manager, as we clicked on the
server icon the following error was issued:
"An error 1069 (the service did not start due to a logon
failure) ocurred while performing this service operation
on then MSSQL Server Service." In a related dialog we
found out that its default login procedure is by means of
the windows login. Another option was to
provide 'independent' login/password. In older versions I
was always able to login using sa as login with empty
password...
Which one should we use? what is missing?
tia
paco
tia,
FranciscoYour problem is not the login from EM to SQL Server. The problem is that SQL Server didn't event
start. Check out the Service Account for the SQL Server service, and the password specified for
this.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Francisco" <anonymous@.discussions.microsoft.com> wrote in message
news:09dd01c3aec7$002f4a50$a001280a@.phx.gbl...
> Hi,
> We have just installed sql server 8
> while using the enterprise manager, as we clicked on the
> server icon the following error was issued:
> "An error 1069 (the service did not start due to a logon
> failure) ocurred while performing this service operation
> on then MSSQL Server Service." In a related dialog we
> found out that its default login procedure is by means of
> the windows login. Another option was to
> provide 'independent' login/password. In older versions I
> was always able to login using sa as login with empty
> password...
> Which one should we use? what is missing?
> tia
> paco
>
> tia,
> Francisco
>

Connection failed:

Hi Guys,

I encountered an error while opening my third SQL Connection in Enterprise Manager

--------
Microsoft SQL Server Login
--------
Connection failed:
SQLState: '01000'
SQL Server Error: 232
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionWrite (WrapperWrite()).
Connection failed:
SQLState: '08S01'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.

--------
OK
--------

I am using the following
SQL Server 2000 Enterprise Edition (SP4)
Windows 2000 Professional (SP4)

first two connections are with Query Analyzer, the third attempt is when opening a table inside Enterprise Manager

anyone experienced this?Sounds like you have to enable the shared memory protocol for the instance in cliconfg.exe.|||hi MCrowley

yeah, but the problem is, I can't remember what I did (gosh, too much for making experiments :) )

Is there a way on how to reverse this effect?

Thanks|||Is the Shared Memory protocol enabled in Cliconfg.exe?|||Is the Shared Memory protocol enabled in Cliconfg.exe? ;)|||The first thing I would do if I were in your position would be to check the setting of Shared Memory Protocol in cliconfg.exe and make sure it is enabled.

Just my .02 :)|||gosh,

sorry for the very late reply

yes, its enabled, what does this option do by the way?

thanks|||Shared memory is a protocol that can be used by applications running on the same box as SQL Server. Now that it is enabled, do you still get the same error?

Connection error

Hello......
I have a weird thing going on, I can see my server through the manager(Enterprise) but when I try to access it a warning comes up
A connection could not be established to (Server Name)
Reason: Cannot generate SSPI context.
Please verify SQL Server is running and check your SQL Server registration properties.
I have access to all my other servers using the same authentication (Windows). Any ideas?
Robert,
HOW TO: Troubleshoot the "Cannot Generate SSPI Context" Error Message
http://support.microsoft.com/default.aspx?id=811889
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"robert salazar" <rsalazar@.cbbank.com> wrote in message
news:6E0CB220-31C2-44F7-A797-45A0C37804DE@.microsoft.com...
> Hello......
> I have a weird thing going on, I can see my server through the
manager(Enterprise) but when I try to access it a warning comes up
> A connection could not be established to (Server Name)
> Reason: Cannot generate SSPI context.
> Please verify SQL Server is running and check your SQL Server registration
properties.
> I have access to all my other servers using the same authentication
(Windows). Any ideas?

Connection error

Hello.....
I have a weird thing going on, I can see my server through the manager(Enterprise) but when I try to access it a warning comes up
A connection could not be established to (Server Name
Reason: Cannot generate SSPI context
Please verify SQL Server is running and check your SQL Server registration properties
I have access to all my other servers using the same authentication (Windows). Any ideas?Robert,
HOW TO: Troubleshoot the "Cannot Generate SSPI Context" Error Message
http://support.microsoft.com/default.aspx?id=811889
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"robert salazar" <rsalazar@.cbbank.com> wrote in message
news:6E0CB220-31C2-44F7-A797-45A0C37804DE@.microsoft.com...
> Hello......
> I have a weird thing going on, I can see my server through the
manager(Enterprise) but when I try to access it a warning comes up
> A connection could not be established to (Server Name)
> Reason: Cannot generate SSPI context.
> Please verify SQL Server is running and check your SQL Server registration
properties.
> I have access to all my other servers using the same authentication
(Windows). Any ideas?

Connection error

Hello......
I have a weird thing going on, I can see my server through the manager(Enter
prise) but when I try to access it a warning comes up
A connection could not be established to (Server Name)
Reason: Cannot generate SSPI context.
Please verify SQL Server is running and check your SQL Server registration p
roperties.
I have access to all my other servers using the same authentication (Windows
). Any ideas?Robert,
HOW TO: Troubleshoot the "Cannot Generate SSPI Context" Error Message
http://support.microsoft.com/default.aspx?id=811889
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"robert salazar" <rsalazar@.cbbank.com> wrote in message
news:6E0CB220-31C2-44F7-A797-45A0C37804DE@.microsoft.com...
> Hello......
> I have a weird thing going on, I can see my server through the
manager(Enterprise) but when I try to access it a warning comes up
> A connection could not be established to (Server Name)
> Reason: Cannot generate SSPI context.
> Please verify SQL Server is running and check your SQL Server registration
properties.
> I have access to all my other servers using the same authentication
(Windows). Any ideas?

connection broken

Hi,
I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
The Server was successfully registered.
But when I try to show the servers properties, or to insert a new login
there is always the following error:
"Error 22528 [SQL-DMO]This server connection has been unexpectedly broke
n
and cannot be reconnected."
What is the problem, and how could I solve it?
Help me, please. Thanks, ChristofWhat OS is it running on? You might want to try running SQL client
configuration utility on the Enterpise Manager PC and see what happens when
you connect with different protocols (eg tcp/ip sockets vs named pipes).
You should also check firewall programs and anti-virus programs to see if
they are blocking named pipes.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
> The Server was successfully registered.
> But when I try to show the servers properties, or to insert a new login
> there is always the following error:
> "Error 22528 [SQL-DMO]This server connection has been unexpectedly bro
ken
> and cannot be reconnected."
> What is the problem, and how could I solve it?
> Help me, please. Thanks, Christof
>
>|||Hi Andy,
My problem is already solved - I've installed the service-pack 3 of MSDE,
and now, it works fine.
Thanks anyway,
Christof
"Andy Svendsen" <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:eaucXcWgEHA.1196@.TK2MSFTNGP11.phx.gbl...
> What OS is it running on? You might want to try running SQL client
> configuration utility on the Enterpise Manager PC and see what happens
when
> you connect with different protocols (eg tcp/ip sockets vs named pipes).
> You should also check firewall programs and anti-virus programs to see if
> they are blocking named pipes.
> --
> ****************************************
***************************
> Andy S.
> MCSE NT/2000, MCDBA SQL 7/2000
> andymcdba1@.NOMORESPAM.yahoo.com
> Please remove NOMORESPAM before replying.
> Always keep your antivirus and Microsoft software
> up to date with the latest definitions and product updates.
> Be suspicious of every email attachment, I will never send
> or post anything other than the text of a http:// link nor
> post the link directly to a file for downloading.
> This posting is provided "as is" with no warranties
> and confers no rights.
> ****************************************
***************************
> "Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
> news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
broken[vbcol=seagreen]
>|||Do you resolved them? Please tell me how!
Thanks.
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...

Connection Broken

I am updating records in my database with the procedure below. The data is
updated as it should but the Enterprise Manager (SQL Query Analyzer) gives
the error:
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
It looks like this error is blocking the SQL Server from responding to new
requests immediately (3-4 seconds) after an update.
Any ideas of what can cause this problem?
The sql call with belonging SQL procedure (below) has been tested on several
SQL servers and is working OK, but on this server I am running it against at
the moment it gives error above.
p_kontaktpersoner_endre 44, 'Tor Inge', 'Rislaa', 'TIR', 840, 'IT Manager',
'Adm', '38 15 44 30', '38 15 44 35', '900 90 700', 'myemail@.vef.no', '', 1,
'Test note', 1
CREATE PROCEDURE p_kontaktpersoner_endre
@.kp_id int = 1 ,
@.fornavn varchar(50) = '' ,
@.etternavn varchar(50) = '' ,
@.initialer varchar(3) = '' ,
@.ko_id int = 0 ,
@.stilling varchar(50) = '' ,
@.avdeling varchar(50) = '' ,
@.telefon varchar(30) = '' ,
@.telefaks varchar(30) = '' ,
@.mobiltelefon varchar(30) = '' ,
@.e_post varchar(50) = '' ,
@.kategori varchar(100) = '' ,
@.prioritet int = 1 ,
@.merknad text = '' ,
@.aktiv int = 1
AS
UPDATE kontaktpersoner
SET fornavn = @.fornavn,
etternavn = @.etternavn,
initialer = @.initialer,
ko_id = @.ko_id,
stilling = @.stilling,
avdeling = @.avdeling,
telefon = @.telefon,
telefaks = @.telefaks,
mobiltelefon = @.mobiltelefon,
e_post= @.e_post,
kategori = @.kategori,
prioritet = @.prioritet,
merknad = @.merknad,
aktiv= @.aktiv
FROM kontaktpersoner
WHERE kp_id = @.kp_idHi
You don't give the version information for SQL Server, but this may be one
cause!
http://support.microsoft.com/defaul...kb;en-us;903742
John
"Tor Inge Rislaa" <tor.ingenospam@.rislaa.no> wrote in message
news:OWme0eT3FHA.636@.TK2MSFTNGP10.phx.gbl...
>I am updating records in my database with the procedure below. The data is
>updated as it should but the Enterprise Manager (SQL Query Analyzer) gives
>the error:
>
> [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
> It looks like this error is blocking the SQL Server from responding to new
> requests immediately (3-4 seconds) after an update.
>
> Any ideas of what can cause this problem?
>
> The sql call with belonging SQL procedure (below) has been tested on
> several SQL servers and is working OK, but on this server I am running it
> against at the moment it gives error above.
>
>
> p_kontaktpersoner_endre 44, 'Tor Inge', 'Rislaa', 'TIR', 840, 'IT
> Manager', 'Adm', '38 15 44 30', '38 15 44 35', '900 90 700',
> 'myemail@.vef.no', '', 1, 'Test note', 1
> CREATE PROCEDURE p_kontaktpersoner_endre
> @.kp_id int = 1 ,
> @.fornavn varchar(50) = '' ,
> @.etternavn varchar(50) = '' ,
> @.initialer varchar(3) = '' ,
> @.ko_id int = 0 ,
> @.stilling varchar(50) = '' ,
> @.avdeling varchar(50) = '' ,
> @.telefon varchar(30) = '' ,
> @.telefaks varchar(30) = '' ,
> @.mobiltelefon varchar(30) = '' ,
> @.e_post varchar(50) = '' ,
> @.kategori varchar(100) = '' ,
> @.prioritet int = 1 ,
> @.merknad text = '' ,
> @.aktiv int = 1
> AS
> UPDATE kontaktpersoner
> SET fornavn = @.fornavn,
> etternavn = @.etternavn,
> initialer = @.initialer,
> ko_id = @.ko_id,
> stilling = @.stilling,
> avdeling = @.avdeling,
> telefon = @.telefon,
> telefaks = @.telefaks,
> mobiltelefon = @.mobiltelefon,
> e_post= @.e_post,
> kategori = @.kategori,
> prioritet = @.prioritet,
> merknad = @.merknad,
> aktiv= @.aktiv
> FROM kontaktpersoner
> WHERE kp_id = @.kp_id
>|||Thanks. Do you know where to find what version or SP my server has
TIRislaa
"John Bell" <jbellnewsposts@.hotmail.com> skrev i melding
news:%23m$JfcU3FHA.2196@.tk2msftngp13.phx.gbl...
> Hi
> You don't give the version information for SQL Server, but this may be one
> cause!
> http://support.microsoft.com/defaul...kb;en-us;903742
> John
> "Tor Inge Rislaa" <tor.ingenospam@.rislaa.no> wrote in message
> news:OWme0eT3FHA.636@.TK2MSFTNGP10.phx.gbl...
>|||Hi
Try http://www.aspfaq.com/show.asp?id=2160 and
http://www.aspfaq.com/sql2000builds.asp
In your update statement you don't need the from clause as it is the
same table as the one being updated.
John
Tor Inge Rislaa wrote:
> Thanks. Do you know where to find what version or SP my server has
> TIRislaa
> "John Bell" <jbellnewsposts@.hotmail.com> skrev i melding
> news:%23m$JfcU3FHA.2196@.tk2msftngp13.phx.gbl...

connection broken

Hi,
I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
The Server was successfully registered.
But when I try to show the servers properties, or to insert a new login
there is always the following error:
"Error 22528 [SQL-DMO]This server connection has been unexpectedly broken
and cannot be reconnected."
What is the problem, and how could I solve it?
Help me, please. Thanks, Christof
What OS is it running on? You might want to try running SQL client
configuration utility on the Enterpise Manager PC and see what happens when
you connect with different protocols (eg tcp/ip sockets vs named pipes).
You should also check firewall programs and anti-virus programs to see if
they are blocking named pipes.
************************************************** *****************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
************************************************** *****************
"Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I,ve tried to manage an SQL Server (MSDE) with Enterprise Manager.
> The Server was successfully registered.
> But when I try to show the servers properties, or to insert a new login
> there is always the following error:
> "Error 22528 [SQL-DMO]This server connection has been unexpectedly broken
> and cannot be reconnected."
> What is the problem, and how could I solve it?
> Help me, please. Thanks, Christof
>
>
|||Hi Andy,
My problem is already solved - I've installed the service-pack 3 of MSDE,
and now, it works fine.
Thanks anyway,
Christof
"Andy Svendsen" <andymcdba1@.NOMORESPAM.yahoo.com> wrote in message
news:eaucXcWgEHA.1196@.TK2MSFTNGP11.phx.gbl...
> What OS is it running on? You might want to try running SQL client
> configuration utility on the Enterpise Manager PC and see what happens
when[vbcol=seagreen]
> you connect with different protocols (eg tcp/ip sockets vs named pipes).
> You should also check firewall programs and anti-virus programs to see if
> they are blocking named pipes.
> --
> ************************************************** *****************
> Andy S.
> MCSE NT/2000, MCDBA SQL 7/2000
> andymcdba1@.NOMORESPAM.yahoo.com
> Please remove NOMORESPAM before replying.
> Always keep your antivirus and Microsoft software
> up to date with the latest definitions and product updates.
> Be suspicious of every email attachment, I will never send
> or post anything other than the text of a http:// link nor
> post the link directly to a file for downloading.
> This posting is provided "as is" with no warranties
> and confers no rights.
> ************************************************** *****************
> "Christof Schdeli" <ch.schaedeli@.gmx.ch> wrote in message
> news:ObPgv06fEHA.1972@.TK2MSFTNGP09.phx.gbl...
broken
>
|||Do you resolved them? Please tell me how!
Thanks.
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

Connection between Principal and Mirror servers

Hi guys, right now I am facing this scenario several times and I wonder why it can be happen. Both SQL servers are in Enterprise SP1 edition. The mirroring setup can be work fine to me. Once my principal get attacking by DDOS, then mirroring session change the status to 'DISCONNECTED'. However, after DDOS attack solved and line connection gets back on the principal server, the mirroring session still remain to the status ('DISCONNECTED'). If I restart the SQL services on principal server or mirror server, then only the mirroring session change to 'SYNCHRONIZING' status. Does anyone faced this happen before? I need some assistance on it and hope able to get any explanation or solution from you guys. Thanx and have a nice day.

Best Regards,

Hans

Are the SQL server services set to BOOT or enabled to restart on the failure.

Also chekc the SQL server error log in this case.

Connection

When I try to connect to my database using enterprise manager I get this error:
A connection could not be established to DBSERVER
Reason: Cannot open user default database. Login failed..
I have know that the server is running and the agent is running. There is
no login issues because I was able to login just mins before this happen. I
tried to change the default db with osql utility. I have restarted the
dbserver and still have the same issue. Can anyone if me an idea of what I
need to do.
The SQL login you're trying to use to connect to your SQL server has a
default database defined that either they don't have access to or does
not exist. To get yourself going again you can probably just login to
your server using osql with:
(assuming it's your trusted login you're having problems with)
osql -S MyServer -d master -E
or
(assuming it's a particular SQL login you're having trouble with)
osql -S MyServer -d master -U MyUsername -P MyPassword
And then change your the default DB for that login:
(assuming it's your trusted login...)
1> exec sp_defaultdb @.loginame='MyDomain\MyLogin', @.defdb='master'
2> go
or
(assuming it's a SQL login you're having problems with)
1> exec sp_defaultdb @.loginame='MyUsername', @.defdb='master'
2> go
This should fix up the login you're having issues with by virtue of the
fact that every login on the server can access the master DB.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
new admin wrote:

>When I try to connect to my database using enterprise manager I get this error:
>A connection could not be established to DBSERVER
>Reason: Cannot open user default database. Login failed..
>I have know that the server is running and the agent is running. There is
>no login issues because I was able to login just mins before this happen. I
>tried to change the default db with osql utility. I have restarted the
>dbserver and still have the same issue. Can anyone if me an idea of what I
>need to do.
>
>
|||Thank you soooo much that got me in and now I see that my default db is
(subspect)
"Mike Hodgson" wrote:

> The SQL login you're trying to use to connect to your SQL server has a
> default database defined that either they don't have access to or does
> not exist. To get yourself going again you can probably just login to
> your server using osql with:
> (assuming it's your trusted login you're having problems with)
> osql -S MyServer -d master -E
> or
> (assuming it's a particular SQL login you're having trouble with)
> osql -S MyServer -d master -U MyUsername -P MyPassword
> And then change your the default DB for that login:
> (assuming it's your trusted login...)
> 1> exec sp_defaultdb @.loginame='MyDomain\MyLogin', @.defdb='master'
> 2> go
> or
> (assuming it's a SQL login you're having problems with)
> 1> exec sp_defaultdb @.loginame='MyUsername', @.defdb='master'
> 2> go
> This should fix up the login you're having issues with by virtue of the
> fact that every login on the server can access the master DB.
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> new admin wrote:
>

Connection

When I try to connect to my database using enterprise manager I get this err
or:
A connection could not be established to DBSERVER
Reason: Cannot open user default database. Login failed..
I have know that the server is running and the agent is running. There is
no login issues because I was able to login just mins before this happen. I
tried to change the default db with osql utility. I have restarted the
dbserver and still have the same issue. Can anyone if me an idea of what I
need to do.The SQL login you're trying to use to connect to your SQL server has a
default database defined that either they don't have access to or does
not exist. To get yourself going again you can probably just login to
your server using osql with:
(assuming it's your trusted login you're having problems with)
osql -S MyServer -d master -E
or
(assuming it's a particular SQL login you're having trouble with)
osql -S MyServer -d master -U MyUsername -P MyPassword
And then change your the default DB for that login:
(assuming it's your trusted login...)
1> exec sp_defaultdb @.loginame='MyDomain\MyLogin', @.defdb='master'
2> go
or
(assuming it's a SQL login you're having problems with)
1> exec sp_defaultdb @.loginame='MyUsername', @.defdb='master'
2> go
This should fix up the login you're having issues with by virtue of the
fact that every login on the server can access the master DB.
*mike hodgson*
blog: http://sqlnerd.blogspot.com
new admin wrote:

>When I try to connect to my database using enterprise manager I get this er
ror:
>A connection could not be established to DBSERVER
>Reason: Cannot open user default database. Login failed..
>I have know that the server is running and the agent is running. There is
>no login issues because I was able to login just mins before this happen. I
>tried to change the default db with osql utility. I have restarted the
>dbserver and still have the same issue. Can anyone if me an idea of what I
>need to do.
>
>|||Thank you soooo much that got me in and now I see that my default db is
(subspect)
"Mike Hodgson" wrote:

> The SQL login you're trying to use to connect to your SQL server has a
> default database defined that either they don't have access to or does
> not exist. To get yourself going again you can probably just login to
> your server using osql with:
> (assuming it's your trusted login you're having problems with)
> osql -S MyServer -d master -E
> or
> (assuming it's a particular SQL login you're having trouble with)
> osql -S MyServer -d master -U MyUsername -P MyPassword
> And then change your the default DB for that login:
> (assuming it's your trusted login...)
> 1> exec sp_defaultdb @.loginame='MyDomain\MyLogin', @.defdb='master'
> 2> go
> or
> (assuming it's a SQL login you're having problems with)
> 1> exec sp_defaultdb @.loginame='MyUsername', @.defdb='master'
> 2> go
> This should fix up the login you're having issues with by virtue of the
> fact that every login on the server can access the master DB.
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> new admin wrote:
>
>

Connection

When I try to connect to my database using enterprise manager I get this error:
A connection could not be established to DBSERVER
Reason: Cannot open user default database. Login failed..
I have know that the server is running and the agent is running. There is
no login issues because I was able to login just mins before this happen. I
tried to change the default db with osql utility. I have restarted the
dbserver and still have the same issue. Can anyone if me an idea of what I
need to do.This is a multi-part message in MIME format.
--020006020604030204030608
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
The SQL login you're trying to use to connect to your SQL server has a
default database defined that either they don't have access to or does
not exist. To get yourself going again you can probably just login to
your server using osql with:
(assuming it's your trusted login you're having problems with)
osql -S MyServer -d master -E
or
(assuming it's a particular SQL login you're having trouble with)
osql -S MyServer -d master -U MyUsername -P MyPassword
And then change your the default DB for that login:
(assuming it's your trusted login...)
1> exec sp_defaultdb @.loginame='MyDomain\MyLogin', @.defdb='master'
2> go
or
(assuming it's a SQL login you're having problems with)
1> exec sp_defaultdb @.loginame='MyUsername', @.defdb='master'
2> go
This should fix up the login you're having issues with by virtue of the
fact that every login on the server can access the master DB.
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
new admin wrote:
>When I try to connect to my database using enterprise manager I get this error:
>A connection could not be established to DBSERVER
>Reason: Cannot open user default database. Login failed..
>I have know that the server is running and the agent is running. There is
>no login issues because I was able to login just mins before this happen. I
>tried to change the default db with osql utility. I have restarted the
>dbserver and still have the same issue. Can anyone if me an idea of what I
>need to do.
>
>
--020006020604030204030608
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>The SQL login you're trying to use to connect to your SQL server
has a default database defined that either they don't have access to or
does not exist. To get yourself going again you can probably just
login to your server using osql with:<br>
</tt>
<blockquote><tt>(assuming it's your trusted login you're having
problems with)<br>
osql -S MyServer -d master -E<br>
<br>
or<br>
<br>
(assuming it's a particular SQL login you're having trouble with)<br>
osql -S MyServer -d master -U MyUsername -P MyPassword<br>
</tt></blockquote>
<tt>And then change your the default DB for that login:<br>
</tt>
<blockquote><tt>(assuming it's your trusted login...)<br>
1> exec sp_defaultdb @.loginame='MyDomain\MyLogin', @.defdb='master'<br>
2> go<br>
<br>
or<br>
<br>
(assuming it's a SQL login you're having problems with)<br>
1> </tt><tt>exec sp_defaultdb @.loginame='MyUsername',
@.defdb='master'<br>
2> go<br>
</tt></blockquote>
<tt>This should fix up the login you're having issues with by virtue of
the fact that every login on the server can access the master DB.</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
new admin wrote:
<blockquote cite="midAE6D082D-667E-4F2E-817A-A603BA650462@.microsoft.com"
type="cite">
<pre wrap="">When I try to connect to my database using enterprise manager I get this error:
A connection could not be established to DBSERVER
Reason: Cannot open user default database. Login failed..
I have know that the server is running and the agent is running. There is
no login issues because I was able to login just mins before this happen. I
tried to change the default db with osql utility. I have restarted the
dbserver and still have the same issue. Can anyone if me an idea of what I
need to do.
</pre>
</blockquote>
</body>
</html>
--020006020604030204030608--|||Thank you soooo much that got me in and now I see that my default db is
(subspect)
"Mike Hodgson" wrote:
> The SQL login you're trying to use to connect to your SQL server has a
> default database defined that either they don't have access to or does
> not exist. To get yourself going again you can probably just login to
> your server using osql with:
> (assuming it's your trusted login you're having problems with)
> osql -S MyServer -d master -E
> or
> (assuming it's a particular SQL login you're having trouble with)
> osql -S MyServer -d master -U MyUsername -P MyPassword
> And then change your the default DB for that login:
> (assuming it's your trusted login...)
> 1> exec sp_defaultdb @.loginame='MyDomain\MyLogin', @.defdb='master'
> 2> go
> or
> (assuming it's a SQL login you're having problems with)
> 1> exec sp_defaultdb @.loginame='MyUsername', @.defdb='master'
> 2> go
> This should fix up the login you're having issues with by virtue of the
> fact that every login on the server can access the master DB.
> --
> *mike hodgson*
> blog: http://sqlnerd.blogspot.com
>
> new admin wrote:
> >When I try to connect to my database using enterprise manager I get this error:
> >
> >A connection could not be established to DBSERVER
> >
> >Reason: Cannot open user default database. Login failed..
> >
> >I have know that the server is running and the agent is running. There is
> >no login issues because I was able to login just mins before this happen. I
> >tried to change the default db with osql utility. I have restarted the
> >dbserver and still have the same issue. Can anyone if me an idea of what I
> >need to do.
> >
> >
> >
> >
>

Connecting using Enterprise Manager

Running SQL2000 on Windows NT. Using Enterprise Manager I
have registered a new server. When I register the server
using the wizard, I set the authentication to Windows.
This allows connection using Enterprise Manager.
For a number of reasons I want to change the
authentication to allow 'Mixed mode' but if I go to the
server properties, security tab and try and change the
authentication to SQL and Windows, the change is not saved
(I cant change the authentication this way)
If I edit the server registration to SQL and specify a Log
in and password, I get the message " Not associated with
Trusted SQL server connection"
Can anyone tell me how to set up the server to allow mixed
mode working. Other servers on the network are fine
Thanks in advance for any helpDid you restart the SQL Server service after changing the security mode?
When you make a change in SQL configuration, it becomes a configured value,
but you have to restart for it becoming a running value.
You may want to check the SQL errorlog and Windows Event viewer as well for
detail. You are definitely going to the right place in Enterprise Manager.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Duncan Stott" <Duncan@.intracite.com> wrote in message
news:74bf01c3e747$79074640$a501280a@.phx.gbl...

quote:

---

> Running SQL2000 on Windows NT. Using Enterprise Manager I
> have registered a new server. When I register the server
> using the wizard, I set the authentication to Windows.
> This allows connection using Enterprise Manager.
> For a number of reasons I want to change the
> authentication to allow 'Mixed mode' but if I go to the
> server properties, security tab and try and change the
> authentication to SQL and Windows, the change is not saved
> (I cant change the authentication this way)
> If I edit the server registration to SQL and specify a Log
> in and password, I get the message " Not associated with
> Trusted SQL server connection"
> Can anyone tell me how to set up the server to allow mixed
> mode working. Other servers on the network are fine
> Thanks in advance for any help
>

---

|||It sounds like the account that you are logged on as does not have
permission to change the registry.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Andy
Thanks for the ideas, but I had already tried this. I have
also tried deleting the registration and setting it from
scratch. Same problem. As soon as I specify that I want to
log in usin SQL( not windows) I get the 'Not associated
with Trusted SQL server connection"
I looked in the SQL log as you suggested and there is the
following message
"Configuration option 'show advanced option' changed from
1 to 1. Run the RECONFIGURE statement to instal."
Any ideas
Duncan

quote:

---

>--Original Message--
>Did you restart the SQL Server service after changing the

---

security mode?

quote:

---

>When you make a change in SQL configuration, it becomes a

---

configured value,

quote:

---

>but you have to restart for it becoming a running value.
>You may want to check the SQL errorlog and Windows Event

---

viewer as well for

quote:

---

>detail. You are definitely going to the right place in

---

Enterprise Manager.

quote:

---

>--
> ****************************************
******************

---

*********

quote:

---

>Andy S.
>MCSE NT/2000, MCDBA SQL 7/2000
>andymcdba1@.NOMORESPAM.yahoo.com
>Please remove NOMORESPAM before replying.
>Always keep your antivirus and Microsoft software
>up to date with the latest definitions and product

---

updates.

quote:

---

>Be suspicious of every email attachment, I will never send
>or post anything other than the text of a http:// link nor
>post the link directly to a file for downloading.
>This posting is provided "as is" with no warranties
>and confers no rights.
> ****************************************
******************

---

*********

quote:

---

>"Duncan Stott" <Duncan@.intracite.com> wrote in message
>news:74bf01c3e747$79074640$a501280a@.phx.gbl...
I[QUOTE]
saved[QUOTE]
Log[QUOTE]
mixed[QUOTE]
>
>.
>

---

connecting to the sql 2005 server

I'm wondering if anyone installed the 180 day fully functional trial
SQL 2005 (enterprise edition) and used the client tool (from a
workstation) to connect to it? I installed the server/client
components (on the server) and client tool on my workstation. I can
connect to server using the sql management studio on the server itself,
but not from my workstation. Does anyone know if that's the limitation
of the 180day trial software?
thank youThere is no limitation.
Go to SQL Server Configuration Manager on the server, look for Network
Configuration and check if TCP/IP is enabled.
Ben Nevarez, MCDBA, OCP
Database Administrator
"=== Steve L ===" wrote:

> I'm wondering if anyone installed the 180 day fully functional trial
> SQL 2005 (enterprise edition) and used the client tool (from a
> workstation) to connect to it? I installed the server/client
> components (on the server) and client tool on my workstation. I can
> connect to server using the sql management studio on the server itself,
> but not from my workstation. Does anyone know if that's the limitation
> of the 180day trial software?
> thank you
>|||yeah! it's working! Thank you!!
(yes, the TCP/IP was disabled by default)

Connecting to SQLServer 2000 (sqlsrv32.dll)

Hello,

I am having problem with our network. We run a clinic database system that uses SQLServer 2000 Enterprise as the backend, and Microsoft Access on the front end.

I have had a running problem with all our newer machines (which run Windows 2000 or XP) in that while it connects to the server and retrieves some of the info properly, on some of the pages it doesnt. It will take 2 or 3 minutes for a page of the database to load, and even then not all the information will be retrieved properly.

I was able to fix the problem on the Windows 2000 machines by replacing the Sqlsrv32.dll file with an older version (usually with 3.70.06.23). And then the W2000 machines would work. But for some reason, the XP machines wont accept the older sqlsrv32.dll file...it gives me this error:
SQLState: 'HY000'
SQL Server Error: 126 Unable to load communication module driver correctly.

...and i cant seem to downgrade the MDAC...

any ideas on what I can do?

thanksYou didnt test it properly before it was rolled out for XP, did you?

Tut tut....

Best check technet & see if there is a work around. Failing that, best roll XP boxes back to W2000. Quick, easy & saves face....then I'd spend a LOT of time ironing out the XP issue BEFORE it goes near the client again.

HTH,

Cheers,|||no they are the new computers we got in...they come with XP loaded on them already...

i'll check technet...and then possibly put W2K on them...

thanks...

Connecting to SQL Server OVer Internet

I know it is possible to establish a connection to an SQL Server over
the Internet via Enterprise Manager. My question is, how secure is this
connection? Is there a best practices document for this type of
connection?

Here is my scenario:

We are looking to outsource our web hosting. Currently, we upload
client sensitive data to our SQL Server databases within our internal
network. If we outsource, the SQL server will be on a different
network. We are behind a firewall here and the dedicated hosted SQL
Server will also be behind a firewall. Is the Enterprise Manager
connection succeptable to hackers? If so any reccomendations on how to
accomplish this would be appreciated.

Another scenario is connecting to the SQL Server through a DSN. Can
this be accomplished from inside our network to outsourced server? How
secure would that connection be?

Thanks in Advance.As an ISP with over 700 sites connecting to various SQL and mySQL databases,
I can tell you that there are many ways to accomplish this. The most common
method that we use is SQL replication. Assuming that your new ISP has a SQL
Server they can setup replication and sync the data. This scenario will
allow you (the publisher) to control which tables can be accessed by the
subscriber (your Internet Service Provider).
Another method would be for you to write the communication layer and expose
it to your ISP via .NET web service or COM+.

-Greg

On 2/10/05 1:58 PM, in article
1108061917.584144.223910@.c13g2000cwb.googlegroups. com, "Matt"
<matt_marshall@.manning-napier.com> wrote:

> I know it is possible to establish a connection to an SQL Server over
> the Internet via Enterprise Manager. My question is, how secure is this
> connection? Is there a best practices document for this type of
> connection?
> Here is my scenario:
> We are looking to outsource our web hosting. Currently, we upload
> client sensitive data to our SQL Server databases within our internal
> network. If we outsource, the SQL server will be on a different
> network. We are behind a firewall here and the dedicated hosted SQL
> Server will also be behind a firewall. Is the Enterprise Manager
> connection succeptable to hackers? If so any reccomendations on how to
> accomplish this would be appreciated.
> Another scenario is connecting to the SQL Server through a DSN. Can
> this be accomplished from inside our network to outsourced server? How
> secure would that connection be?
> Thanks in Advance.|||Thank you for your reply Greg. Is SQL Replication secure?|||On 2/10/05 2:48 PM, in article
1108064886.517091.265990@.l41g2000cwc.googlegroups. com, "Matt"
<matt_marshall@.manning-napier.com> wrote:

> Thank you for your reply Greg. Is SQL Replication secure?

I haven't had a security breech (*knock on wood*).
I think just like anything else it's as secure as long as the service packs
are all up to date.

-Greg|||"Matt" <matt_marshall@.manning-napier.com> wrote in message
news:1108061917.584144.223910@.c13g2000cwb.googlegr oups.com...
> I know it is possible to establish a connection to an SQL Server over
> the Internet via Enterprise Manager. My question is, how secure is this
> connection? Is there a best practices document for this type of
> connection?
> Here is my scenario:
> We are looking to outsource our web hosting. Currently, we upload
> client sensitive data to our SQL Server databases within our internal
> network. If we outsource, the SQL server will be on a different
> network. We are behind a firewall here and the dedicated hosted SQL
> Server will also be behind a firewall. Is the Enterprise Manager
> connection succeptable to hackers? If so any reccomendations on how to
> accomplish this would be appreciated.
> Another scenario is connecting to the SQL Server through a DSN. Can
> this be accomplished from inside our network to outsourced server? How
> secure would that connection be?
> Thanks in Advance.

If you are worried about it being secure, then why not set up a VPN
connection between the two sites. This is really quite straight forward with
Windows.

Brian.

www.cryer.co.uk/brian|||Thanks Brian. Can you point me in the direction of establishing a VPN?
The server will be a 2003 server running SQL Server.

Brian Cryer wrote:
> "Matt" <matt_marshall@.manning-napier.com> wrote in message
> news:1108061917.584144.223910@.c13g2000cwb.googlegr oups.com...
> > I know it is possible to establish a connection to an SQL Server
over
> > the Internet via Enterprise Manager. My question is, how secure is
this
> > connection? Is there a best practices document for this type of
> > connection?
> > Here is my scenario:
> > We are looking to outsource our web hosting. Currently, we upload
> > client sensitive data to our SQL Server databases within our
internal
> > network. If we outsource, the SQL server will be on a different
> > network. We are behind a firewall here and the dedicated hosted SQL
> > Server will also be behind a firewall. Is the Enterprise Manager
> > connection succeptable to hackers? If so any reccomendations on how
to
> > accomplish this would be appreciated.
> > Another scenario is connecting to the SQL Server through a DSN. Can
> > this be accomplished from inside our network to outsourced server?
How
> > secure would that connection be?
> > Thanks in Advance.
> If you are worried about it being secure, then why not set up a VPN
> connection between the two sites. This is really quite straight
forward with
> Windows.
> Brian.
> www.cryer.co.uk/brian