interesting connection problem

I am having a problem connecting with SQL server management . I get the error I have posted at the end of the message. However, I can successfully connect with my application. I use the same connection attributes with no success. Same login, same protocol, from the same machine.

Any Ideas?

Thanks!

Tracy

TITLE: Connect to Server

Cannot connect to DEEPSHEEP\SQLEXPRESS.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

BUTTONS:

OK

Can you connect to the instance locally by using ".\SQLEXPRESS" instead of "DEEPSHEEP\SQLEXPRESS"?

Do you have SP1 installed with the SSMS Express Edition management tools?

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server
http://blogs.msdn.com/sqlrem/

Integrity Check From Maintenance Plan Fails - Error 22029

Hello,
I created a Maintenance plan and the only thing I have it do is perform an
Integrity Check on the database. It's been running successfully for 2 years.
I recently Added Replication to this server, having the data from this
server replicated onto a backup server. During that setup, I had to let
SQLServer Agent run as a different user than the system Administrator for
some reason. So I changed it to run as a different Windows User that has
Administrator privileges.
The command for the check is:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
D2A9902D-1F5F-4FCB-8819-62609F141FD5 -WriteHistory -CkDBRepair '
Now the Integrity Check won't run.
The user is set as a user on the Server with Admin privileges with Access to
the database in question.
Since I'm trying to let it do the minor repair, could it be that Agent
running as a different user doesn't get the exclusive access it needs?
Thanks for any help.
John
Specify a report file for the job and check for the specific errors in the report file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"John Manion" <JohnManion@.discussions.microsoft.com> wrote in message
news:E77351D7-DA36-43B4-9C61-C31FCF1EBA99@.microsoft.com...
> Hello,
> I created a Maintenance plan and the only thing I have it do is perform an
> Integrity Check on the database. It's been running successfully for 2 years.
> I recently Added Replication to this server, having the data from this
> server replicated onto a backup server. During that setup, I had to let
> SQLServer Agent run as a different user than the system Administrator for
> some reason. So I changed it to run as a different Windows User that has
> Administrator privileges.
> The command for the check is:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> D2A9902D-1F5F-4FCB-8819-62609F141FD5 -WriteHistory -CkDBRepair '
> Now the Integrity Check won't run.
> The user is set as a user on the Server with Admin privileges with Access to
> the database in question.
> Since I'm trying to let it do the minor repair, could it be that Agent
> running as a different user doesn't get the exclusive access it needs?
> Thanks for any help.
> John

Integrity Check From Maintenance Plan Fails - Error 22029

Hello,
I created a Maintenance plan and the only thing I have it do is perform an
Integrity Check on the database. It's been running successfully for 2 years
.
I recently Added Replication to this server, having the data from this
server replicated onto a backup server. During that setup, I had to let
SQLServer Agent run as a different user than the system Administrator for
some reason. So I changed it to run as a different Windows User that has
Administrator privileges.
The command for the check is:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
D2A9902D-1F5F-4FCB-8819-62609F141FD5 -WriteHistory -CkDBRepair '
Now the Integrity Check won't run.
The user is set as a user on the Server with Admin privileges with Access to
the database in question.
Since I'm trying to let it do the minor repair, could it be that Agent
running as a different user doesn't get the exclusive access it needs?
Thanks for any help.
JohnSpecify a report file for the job and check for the specific errors in the r
eport file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"John Manion" <JohnManion@.discussions.microsoft.com> wrote in message
news:E77351D7-DA36-43B4-9C61-C31FCF1EBA99@.microsoft.com...
> Hello,
> I created a Maintenance plan and the only thing I have it do is perform an
> Integrity Check on the database. It's been running successfully for 2 yea
rs.
> I recently Added Replication to this server, having the data from this
> server replicated onto a backup server. During that setup, I had to let
> SQLServer Agent run as a different user than the system Administrator for
> some reason. So I changed it to run as a different Windows User that has
> Administrator privileges.
> The command for the check is:
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> D2A9902D-1F5F-4FCB-8819-62609F141FD5 -WriteHistory -CkDBRepair '
> Now the Integrity Check won't run.
> The user is set as a user on the Server with Admin privileges with Access
to
> the database in question.
> Since I'm trying to let it do the minor repair, could it be that Agent
> running as a different user doesn't get the exclusive access it needs?
> Thanks for any help.
> John