Can't find Folders that I hid in List View

To all,

I checked the box "hide in list view" for a particular folder under the folder properties. Does anybody know how I get my folder back in the list view again? I cannot seem to find any information pertaining to "unhiding" a folder that was hidden.

Thank you,

blyonsd

In Report Manager, get to a level one above the Folder (where you would have seen it if not hidden ...). Click Show Details on the upper right bar. When the folder appears in the list, re-enter it, go to the Properties tab, and uncheck Hide in list view. Apply, and it should re-appear with Details Hidden ...

Good Luck.

Bill

William E. Pearson III
CPA, CMA, CIA, MCSE, MCDBA
Island Technologies Inc.
931 Monroe Drive
Suite 102-321
Atlanta, GA 30308

404.872.5972 Office

wep3@.islandtechnologies.com

wep3@.reporting-services-architect.com
www.reporting-services-architect.com
-- -- --

Publisher Sites:

http://www.databasejournal.com/article.php/1459531

http://www.sql-server-performance.com/bill_pearson.asp

http://www.informit.com/authors/bio.asp?a=862acd62-4662-49ae-879d-541c8b4d656f

http://www.2000trainers.com/section.aspx?sectionID=17

|||Thank you very much for your help!! It worked like a charm.

Can't figure out how to pass a comma delimeted value?

I am trying to pass a comma delimited value from an input box "attempting to
allow for multple entries within a string" and have the results returned from
the report. The stored procedure that I created will allow me to get what I
want but when I try to make the report make use of the sproc from within a
parameter I get nothing returned if I enter multiple values seperated by a
comma into the input box. If I put in just a single entry, it works.
Again, when I run the stored procedure within the database it works with
multiple values, when I run and test within the data view in the report it
runs and accepts multiple entries when prompted. Only when I run the report
does it fail?
Here is the sproc...
USE [mydatabase]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER OFF
GO
CREATE PROCEDURE [dbo].[usp_TestRprtArray]
@.subscriberarray varchar(500)
as
declare @.sql varchar(8000)
set @.subscriberarray = "'" + replace(@.subscriberarray,',',"','") + "'"
set @.sql = "select SUBSCRIBER, OID, CODE, OFFERCODE, EFFECTIVE_DATE,
EXPIRATION_DATE from subscription where (subscriber in (" + @.subscriberarray
+ "))"
exec (@.sql)
--
Anthony E. Castro - MCDBAIf the comma seperated value is passed from thr UI screen of a web
page.. try url encoding the page...
acmcdba68 wrote:
> I am trying to pass a comma delimited value from an input box "attempting to
> allow for multple entries within a string" and have the results returned from
> the report. The stored procedure that I created will allow me to get what I
> want but when I try to make the report make use of the sproc from within a
> parameter I get nothing returned if I enter multiple values seperated by a
> comma into the input box. If I put in just a single entry, it works.
> Again, when I run the stored procedure within the database it works with
> multiple values, when I run and test within the data view in the report it
> runs and accepts multiple entries when prompted. Only when I run the report
> does it fail?
> Here is the sproc...
> USE [mydatabase]
> GO
> SET ANSI_NULLS ON
> GO
> SET QUOTED_IDENTIFIER OFF
> GO
> CREATE PROCEDURE [dbo].[usp_TestRprtArray]
> @.subscriberarray varchar(500)
> as
> declare @.sql varchar(8000)
> set @.subscriberarray = "'" + replace(@.subscriberarray,',',"','") + "'"
> set @.sql = "select SUBSCRIBER, OID, CODE, OFFERCODE, EFFECTIVE_DATE,
> EXPIRATION_DATE from subscription where (subscriber in (" + @.subscriberarray
> + "))"
> exec (@.sql)
> --
> Anthony E. Castro - MCDBA|||try putting in a textbox in your report that shows what parameter RS is
sending your sproc. that can be helpfule in seeing just what is passing in
the back end. Are you using a Multi-value parameter box? that format is
usually '<value>,<value>,...'
What works for me is to loop through the string, parsing out each value and
inserting the results into a temp table that can then be sorted, filtered,
etc as you like.
"acmcdba68" wrote:
> I am trying to pass a comma delimited value from an input box "attempting to
> allow for multple entries within a string" and have the results returned from
> the report. The stored procedure that I created will allow me to get what I
> want but when I try to make the report make use of the sproc from within a
> parameter I get nothing returned if I enter multiple values seperated by a
> comma into the input box. If I put in just a single entry, it works.
> Again, when I run the stored procedure within the database it works with
> multiple values, when I run and test within the data view in the report it
> runs and accepts multiple entries when prompted. Only when I run the report
> does it fail?
> Here is the sproc...
> USE [mydatabase]
> GO
> SET ANSI_NULLS ON
> GO
> SET QUOTED_IDENTIFIER OFF
> GO
> CREATE PROCEDURE [dbo].[usp_TestRprtArray]
> @.subscriberarray varchar(500)
> as
> declare @.sql varchar(8000)
> set @.subscriberarray = "'" + replace(@.subscriberarray,',',"','") + "'"
> set @.sql = "select SUBSCRIBER, OID, CODE, OFFERCODE, EFFECTIVE_DATE,
> EXPIRATION_DATE from subscription where (subscriber in (" + @.subscriberarray
> + "))"
> exec (@.sql)
> --
> Anthony E. Castro - MCDBA

Can't enable Full Text on database

Got a strange problem.
Had a SQL 7.0 Box with FTS on a database. Worked fine except for one quirk
we never tracked down. Starting up the MSSearch Service would fail 1/2 the
time due to timeout. Other 1/2 would take a long time (like sometimes an
hour) to start.
Upgraded to SQL 2000, no SP.
Upgrade went fine, similar startup problems.
Applied SP4.
Got the usual warning about having to recreate indices, etc. Not a problem
since we were releasing new code specifically for SQL 2000 FT.
Now... well it just doesn't work.
For example, if I try to start an index build on a table, I get Error 15601:
Full-Text Search is not enabled for the current database...
Ok, no problem.. try
sp_fulltext_database 'enable'
get
Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line 46
The Microsoft Search service cannot be administered under the present user
account
First thought was try to synchronize the passwords (i.e. start/stop SQL
Server, change to local account and then back to the domain account so that
MSSearch can talk to it.)
No Joy.
So, at this point I'm either facing calling Microsoft, or taking the server
offline for a day while I uninstall SQL 2000, reinstall it and re-attach the
databases and hope that works.
Suggestions?
--
Greg D. Moore
President Green Mountain Software
Personal: http://stratton.greenms.com
SQL Server Consulting sql at greenms.com
Hi Greg,
Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
7.0 was problematic at best...
In regards to error "The Microsoft Search service cannot be administered
under the present user account", have you removed or altered the
BUILTIN\Administrators login? If so, then this breaks FTS as the MSSearch
service uses this account to login into SQL Server. If you cannot add back
this login or cannot alter the login back to all of its default for security
reasons, you can use the following SQL code to enable the localsystem
account to have the proper security as a workaround:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
See KB article 263712 "INF: How To Prevent Windows NT Administrators From
Administering a Clustered SQL Server" at
http://support.microsoft.com/default...;EN-US;q263712 for details.
Hope that helps,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
> Got a strange problem.
> Had a SQL 7.0 Box with FTS on a database. Worked fine except for one
> quirk
> we never tracked down. Starting up the MSSearch Service would fail 1/2
> the
> time due to timeout. Other 1/2 would take a long time (like sometimes an
> hour) to start.
> Upgraded to SQL 2000, no SP.
> Upgrade went fine, similar startup problems.
> Applied SP4.
> Got the usual warning about having to recreate indices, etc. Not a
> problem
> since we were releasing new code specifically for SQL 2000 FT.
> Now... well it just doesn't work.
> For example, if I try to start an index build on a table, I get Error
> 15601:
> Full-Text Search is not enabled for the current database...
> Ok, no problem.. try
> sp_fulltext_database 'enable'
> get
> Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line
> 46
> The Microsoft Search service cannot be administered under the present user
> account
> First thought was try to synchronize the passwords (i.e. start/stop SQL
> Server, change to local account and then back to the domain account so
> that
> MSSearch can talk to it.)
> No Joy.
> So, at this point I'm either facing calling Microsoft, or taking the
> server
> offline for a day while I uninstall SQL 2000, reinstall it and re-attach
> the
> databases and hope that works.
> Suggestions?
>
>
> --
> --
> Greg D. Moore
> President Green Mountain Software
> Personal: http://stratton.greenms.com
> SQL Server Consulting sql at greenms.com
>
|||"John Kane" <jt-kane@.comcast.net> wrote in message
news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Hi Greg,
> Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
> 7.0 was problematic at best...
Oh good. :-)

> In regards to error "The Microsoft Search service cannot be administered
> under the present user account", have you removed or altered the
> BUILTIN\Administrators login?
Not that I am aware of.

> If so, then this breaks FTS as the MSSearch
> service uses this account to login into SQL Server. If you cannot add back
> this login or cannot alter the login back to all of its default for
security
> reasons, you can use the following SQL code to enable the localsystem
> account to have the proper security as a workaround:
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
Tried this, still no joy.
Did notice the database in question the name dbo was mapped to a login
called MONITOR (one of our internal accounts) instead of sa or
domain\administrator.
I've removed that mapping. So far hasn't helped.

> See KB article 263712 "INF: How To Prevent Windows NT Administrators From
> Administering a Clustered SQL Server" at
> http://support.microsoft.com/default...;EN-US;q263712 for
details.
>
Nothing here stood out.
Thanks though.

> Hope that helps,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
message[vbcol=seagreen]
> news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
an[vbcol=seagreen]
Line[vbcol=seagreen]
user
>
|||Hi Greg,
Hmm... It is possible it is something new &/or affected by SP4. I take it
you upgraded to SP4 directly from RTM, and not RTM to SP3 then to SP4.
Correct? I've not heard of any new FTS related bugs in SP4 that are
directly related to this error. However, there are two FIX kb articles
(http://support.microsoft.com/?kbid=900390 - post-SP4 and
http://support.microsoft.com/default...b;en-us;890043 - post SP3)
that I've blogged about in August, neither are well written IMHO.
The below workaround has in the past resolved this issue, however, in all
cases it was pre-SP4. As this is related to a possible SP4 issue, you might
want to open that support issue with MS PSS SQL Server support... :-(
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:zFP0f.9074$vw6.4605@.newsread1.news.atl.earthl ink.net...
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Oh good. :-)
>
> Not that I am aware of.
> security
> Tried this, still no joy.
> Did notice the database in question the name dbo was mapped to a login
> called MONITOR (one of our internal accounts) instead of sa or
> domain\administrator.
> I've removed that mapping. So far hasn't helped.
>
> details.
> Nothing here stood out.
> Thanks though.
> message
> an
> Line
> user
>

cant drop rowguid or msrepl_tran_version

sql2k sp3
Ive got these columns on a previously replicated table and
I cant get rid of them. I went so far as to disable
Publisheing from the box and still no luck. I also removed
the default values and the indexes from them. I also tried
sp_repldropcolumn. Any ideas?
TIA, ChrisR
Chris,
there is a stored procedure to do this called sp_MSunmarkreplinfo which
takes a tablename as a parameter. Alternatively, setting replinfo to 0 in
sysobjects for the particular table should do it. Finally, running
sp_removedbreplication can be used to remove all traces of replication in
the subscriber database, but obviously must only be done if this database is
not also configured as a publisher.
HTH,
Paul Ibison
|||I appreciate the help. I had already run the
sp_MSunmarkreplinfo. I have dropped the Subscription db's.
And I ran sp_removedbreplication on the Publisher. I still
cant drop them. Any other ideas?

>--Original Message--
>Chris,
>there is a stored procedure to do this called
sp_MSunmarkreplinfo which
>takes a tablename as a parameter. Alternatively, setting
replinfo to 0 in
>sysobjects for the particular table should do it.
Finally, running
>sp_removedbreplication can be used to remove all traces
of replication in
>the subscriber database, but obviously must only be done
if this database is
>not also configured as a publisher.
>HTH,
>Paul Ibison
>
>.
>

Can't Disable, getting Server Cannot obtain LOCK

Internet merge replication. Need to detach to move to a new box. Deleted
all the publication, now when I try to disable it as the publisher. I tried
to run sp_removedbreplication 'db_name' and get the same message.
Any thoughts?
Thanks
After lots more reading and searching, I found low memory could cause this.
I added another 512 to the box, and it worked.
"SteveInBeloit" wrote:

> Internet merge replication. Need to detach to move to a new box. Deleted
> all the publication, now when I try to disable it as the publisher. I tried
> to run sp_removedbreplication 'db_name' and get the same message.
> Any thoughts?
> Thanks
|||I would have bounced the server and then tried this - this is abnormal.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:17E5CBD0-5D2A-444A-97BD-4629B2AE3559@.microsoft.com...[vbcol=seagreen]
> After lots more reading and searching, I found low memory could cause
> this.
> I added another 512 to the box, and it worked.
>
> "SteveInBeloit" wrote:

can't disable a job in sql2k

Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/defaul...b;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/defaul...kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/defaul...b;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>|||In addition to the other posts:
http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...[v
bcol=seagreen]
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedul
e)
> that originated from an MSX server.the job was not saved.
> Thanks
>[/vbcol]

can't disable a job in sql2k

Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
Thanks
This problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default...;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>
|||Thats an easy one:
http://support.microsoft.com/default...b;en-us;281642
HTH, jens Suessmeyer.
|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default...;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>
|||In addition to the other posts:
http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>

can't disable a job in sql2k

Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
--
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>> Hi all,
>> I have a job in sql2k box. After the box network name changed. I can't do
>> any modification to that job anymore.
>> It says, error 14274 can't update, add or delete a job(or steps or
>> schedule) that originated from an MSX server.the job was not saved.
>> Thanks
>|||In addition to the other posts:
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>

Can't delete orphaned Mirror because the principal server is decommissioned

Hoping someone can help me with this. I have a SQL 2005 box which was
formerly in a '2005 mirror.' The SQL server containing the
'principal' is now dead (ceased to exist). That is not the problem.
The problem is that I now want to delete the mirror as it is no longer
needed. The status of the mirror is 'Disconnected / In Recovery.'
Problem is that when I try to delete it, I get the message "Database x
is enabled for Database Mirroring, Database Mirroring must be removed
before dropping the database. (Microsoft SQL Server, Error: 3743).
O.K., this is another fine mess you've gotten me into Olly.... Ho do I
delete the 'mirroring relationship' if the server containing the
Principal has 'gone to a better life?' Until I work out how, I will
have to just ignore it and continue to put he server into production.
Not a great option. Thanks in advance.On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> Hoping someone can help me with this. I have a SQL 2005 box which was
> formerly in a '2005mirror.' The SQL server containing the
> 'principal' is now dead (ceased to exist). That is not the problem.
> The problem is that I now want todeletethemirroras it is no longer
> needed. The status of themirroris 'Disconnected / In Recovery.'
> Problem is that when I try todeleteit, I get the message "Database x
> is enabled for Database Mirroring, Database Mirroring must be removed
> before dropping the database. (Microsoft SQL Server, Error: 3743).
> O.K., this is another fine mess you've gotten me into Olly.... Ho do Ideletethe 'mirroring relationship' if the server containing the
> Principal has 'gone to a better life?' Until I work out how, I will
> have to just ignore it and continue to put he server into production.
> Not a great option. Thanks in advance.
Here is what I have done with this. I know it is not nice but it has
partially worked. I simply stopped SQL server, renamed the mdf file
and restarted the server. This has worked. I actually thought I
would have to still delete the artifact of the database in a 'suspect
state.' But I didn't even have to do this. It was just gone. One
problem - though - the event log still contains an error "FCB::Open
failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
for file number 1. OS error: 2(error not found)." Anybody have any
ideas of how I can get rid of this?|||Try to restore over it with any old database backup and use overwrite
database while restoring.
Make sure you no longer need this database before performing above step.
Manu Jaidka
"togbabe" wrote:
> On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> > Hoping someone can help me with this. I have a SQL 2005 box which was
> > formerly in a '2005mirror.' The SQL server containing the
> > 'principal' is now dead (ceased to exist). That is not the problem.
> > The problem is that I now want todeletethemirroras it is no longer
> > needed. The status of themirroris 'Disconnected / In Recovery.'
> > Problem is that when I try todeleteit, I get the message "Database x
> > is enabled for Database Mirroring, Database Mirroring must be removed
> > before dropping the database. (Microsoft SQL Server, Error: 3743).
> > O.K., this is another fine mess you've gotten me into Olly.... Ho do Ideletethe 'mirroring relationship' if the server containing the
> > Principal has 'gone to a better life?' Until I work out how, I will
> > have to just ignore it and continue to put he server into production.
> > Not a great option. Thanks in advance.
> Here is what I have done with this. I know it is not nice but it has
> partially worked. I simply stopped SQL server, renamed the mdf file
> and restarted the server. This has worked. I actually thought I
> would have to still delete the artifact of the database in a 'suspect
> state.' But I didn't even have to do this. It was just gone. One
> problem - though - the event log still contains an error "FCB::Open
> failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
> for file number 1. OS error: 2(error not found)." Anybody have any
> ideas of how I can get rid of this?
>

Can't delete orphaned Mirror because the principal server is decommissioned

Hoping someone can help me with this. I have a SQL 2005 box which was
formerly in a '2005 mirror.' The SQL server containing the
'principal' is now dead (ceased to exist). That is not the problem.
The problem is that I now want to delete the mirror as it is no longer
needed. The status of the mirror is 'Disconnected / In Recovery.'
Problem is that when I try to delete it, I get the message "Database x
is enabled for Database Mirroring, Database Mirroring must be removed
before dropping the database. (Microsoft SQL Server, Error: 3743).
O.K., this is another fine mess you've gotten me into Olly.... Ho do I
delete the 'mirroring relationship' if the server containing the
Principal has 'gone to a better life?' Until I work out how, I will
have to just ignore it and continue to put he server into production.
Not a great option. Thanks in advance.
On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> Hoping someone can help me with this. I have a SQL 2005 box which was
> formerly in a '2005mirror.' The SQL server containing the
> 'principal' is now dead (ceased to exist). That is not the problem.
> The problem is that I now want todeletethemirroras it is no longer
> needed. The status of themirroris 'Disconnected / In Recovery.'
> Problem is that when I try todeleteit, I get the message "Database x
> is enabled for Database Mirroring, Database Mirroring must be removed
> before dropping the database. (Microsoft SQL Server, Error: 3743).
> O.K., this is another fine mess you've gotten me into Olly.... Ho do Ideletethe 'mirroring relationship' if the server containing the
> Principal has 'gone to a better life?' Until I work out how, I will
> have to just ignore it and continue to put he server into production.
> Not a great option. Thanks in advance.
Here is what I have done with this. I know it is not nice but it has
partially worked. I simply stopped SQL server, renamed the mdf file
and restarted the server. This has worked. I actually thought I
would have to still delete the artifact of the database in a 'suspect
state.' But I didn't even have to do this. It was just gone. One
problem - though - the event log still contains an error "FCB::Open
failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
for file number 1. OS error: 2(error not found)." Anybody have any
ideas of how I can get rid of this?
|||Try to restore over it with any old database backup and use overwrite
database while restoring.
Make sure you no longer need this database before performing above step.
Manu Jaidka
"togbabe" wrote:

> On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> Here is what I have done with this. I know it is not nice but it has
> partially worked. I simply stopped SQL server, renamed the mdf file
> and restarted the server. This has worked. I actually thought I
> would have to still delete the artifact of the database in a 'suspect
> state.' But I didn't even have to do this. It was just gone. One
> problem - though - the event log still contains an error "FCB::Open
> failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
> for file number 1. OS error: 2(error not found)." Anybody have any
> ideas of how I can get rid of this?
>

Can't delete orphaned Mirror because the principal server is decommissioned

Hoping someone can help me with this. I have a SQL 2005 box which was
formerly in a '2005 mirror.' The SQL server containing the
'principal' is now dead (ceased to exist). That is not the problem.
The problem is that I now want to delete the mirror as it is no longer
needed. The status of the mirror is 'Disconnected / In Recovery.'
Problem is that when I try to delete it, I get the message "Database x
is enabled for Database Mirroring, Database Mirroring must be removed
before dropping the database. (Microsoft SQL Server, Error: 3743).
O.K., this is another fine mess you've gotten me into Olly.... Ho do I
delete the 'mirroring relationship' if the server containing the
Principal has 'gone to a better life?' Until I work out how, I will
have to just ignore it and continue to put he server into production.
Not a great option. Thanks in advance.On Jul 13, 12:53 pm, togbabe <togb...@.yahoo.co.uk> wrote:
> Hoping someone can help me with this. I have a SQL 2005 box which was
> formerly in a '2005mirror.' The SQL server containing the
> 'principal' is now dead (ceased to exist). That is not the problem.
> The problem is that I now want todeletethemirroras it is no longer
> needed. The status of themirroris 'Disconnected / In Recovery.'
> Problem is that when I try todeleteit, I get the message "Database x
> is enabled for Database Mirroring, Database Mirroring must be removed
> before dropping the database. (Microsoft SQL Server, Error: 3743).
> O.K., this is another fine mess you've gotten me into Olly.... Ho do Idel
etethe 'mirroring relationship' if the server containing the
> Principal has 'gone to a better life?' Until I work out how, I will
> have to just ignore it and continue to put he server into production.
> Not a great option. Thanks in advance.
Here is what I have done with this. I know it is not nice but it has
partially worked. I simply stopped SQL server, renamed the mdf file
and restarted the server. This has worked. I actually thought I
would have to still delete the artifact of the database in a 'suspect
state.' But I didn't even have to do this. It was just gone. One
problem - though - the event log still contains an error "FCB::Open
failed: Could not open file D:\Microsoft SQL Server\MSSQL\Data\x.mdf
for file number 1. OS error: 2(error not found)." Anybody have any
ideas of how I can get rid of this?

Can't delete or overwrite report

When I try to delete this report from the admin it times out, same if I try
to republish from the report designer. I am admin on the box and in reporting
services.
Error looks like:
System.Web.Services.Protocols.SoapException: Server was unable to process
request. --> System.Data.SqlClient.SqlException: Timeout expired. The
timeout period elapsed prior to completion of the operation or the server is
not responding. at
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior,
RunBehavior runBehavior, Boolean returnStream) at
System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
at Microsoft.ReportingServices.Library.DBInterface.DeleteObject(String
objectName) at
Microsoft.ReportingServices.Library.RSService._DeleteItem(String item) at
Microsoft.ReportingServices.Library.RSService.DeleteItem(CallParameters
parameters) at
Microsoft.ReportingServices.Library.RSService.ExecuteBatch(Guid batchId) at
Microsoft.ReportingServices.WebServer.ReportingService.ExecuteBatch() --
End of inner exception stack trace --
How can I delete the report?I have the exact same problem. I can move the report to another folder but
any attempt to delete it or overwrite it via Designer results in the Server
going to 100% CPU utilisation and everything grinding to a halt until the
timeout error below appears.
Can someone please help us? Thanks.
"bmurtha" wrote:
> When I try to delete this report from the admin it times out, same if I try
> to republish from the report designer. I am admin on the box and in reporting
> services.
> Error looks like:
> System.Web.Services.Protocols.SoapException: Server was unable to process
> request. --> System.Data.SqlClient.SqlException: Timeout expired. The
> timeout period elapsed prior to completion of the operation or the server is
> not responding. at
> System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior,
> RunBehavior runBehavior, Boolean returnStream) at
> System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at
> Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> at Microsoft.ReportingServices.Library.DBInterface.DeleteObject(String
> objectName) at
> Microsoft.ReportingServices.Library.RSService._DeleteItem(String item) at
> Microsoft.ReportingServices.Library.RSService.DeleteItem(CallParameters
> parameters) at
> Microsoft.ReportingServices.Library.RSService.ExecuteBatch(Guid batchId) at
> Microsoft.ReportingServices.WebServer.ReportingService.ExecuteBatch() --
> End of inner exception stack trace --
> How can I delete the report?|||I finally deleted the culprit report by removing it from the ReportServer
database. First identify the datasource it is using and then delete the
datasource from this table:
reportserver.dbo.[datasource]
If it's shared you will have to recreate it again afterwards.
Then delete the offending report from:
reportserver.dbo.[catalog]
That did it for me, but obviously I have no idea what the consequences might
be!
"bmurtha" wrote:
> When I try to delete this report from the admin it times out, same if I try
> to republish from the report designer. I am admin on the box and in reporting
> services.
> Error looks like:
> System.Web.Services.Protocols.SoapException: Server was unable to process
> request. --> System.Data.SqlClient.SqlException: Timeout expired. The
> timeout period elapsed prior to completion of the operation or the server is
> not responding. at
> System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior,
> RunBehavior runBehavior, Boolean returnStream) at
> System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at
> Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> at Microsoft.ReportingServices.Library.DBInterface.DeleteObject(String
> objectName) at
> Microsoft.ReportingServices.Library.RSService._DeleteItem(String item) at
> Microsoft.ReportingServices.Library.RSService.DeleteItem(CallParameters
> parameters) at
> Microsoft.ReportingServices.Library.RSService.ExecuteBatch(Guid batchId) at
> Microsoft.ReportingServices.WebServer.ReportingService.ExecuteBatch() --
> End of inner exception stack trace --
> How can I delete the report?

Can't connect with Upgrade Advisor

I'm having trouble connecting the Upgrade Advisor to a SQL 2000 box at a client. Here's the setup:

1> I'm running UA on a Virtual PC image

2> I can run UA against other SQL machines on the same domain

3> I can register and administer the SQL server I'm having trouble with in Enterprise Manager

4> I have SA rights on the SQL box I'm having trouble with.

5> The problem is when entering the server name and clicking "detect," it errors out with "The network path not found (mscorlib)."

6> I've tried server name, FQDN and IP address.

This is a fairly convoluted layout, so there could be a firewall issue that I'm not aware of (but I don't think so).

Any help would be appreciated!

Bob

Bob, have you tried running UA directly on the target server? It shouldn't be a problem unless the OS level on the server doesn't support UA.|||

Hey, Allen. Thanks for the feedback...as we discussed Thursday (but I mention here in case anyone else is interested), I don't want to add the .Net Framework to the server at this point.

Bob

Can't connect to SQL Server through a box in the DMZ

Hello,
I am running an NT server in the DMZ and need to connect to SQL Server 2000
on another box. I am unable to try to ping the SQL box because ping is
disabled within the DMZ. Everytime I try to connect I get a Timed-out
error. Does anyone know how would I be able to connect to SQL Server?
Thanks in advance,
BelindaAssume the SQL server is in DMZ domain. You'll need trust relationship set
up betweenDMZ and your domain.
"Belinda Rodriguez" <rodrigub@.symbol.com> wrote in message
news:Oxe8ZhqVDHA.1780@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I am running an NT server in the DMZ and need to connect to SQL Server
2000
> on another box. I am unable to try to ping the SQL box because ping is
> disabled within the DMZ. Everytime I try to connect I get a Timed-out
> error. Does anyone know how would I be able to connect to SQL Server?
> Thanks in advance,
> Belinda
>|||Thank you for the response, but I was able to figure out the problem. The
login time-out was at 4 sec and I increased it to 20. I also added the ip
and server name to the host file, which seemed to do the trick.
Thanks again,
Belinda
"Richard Ding" <dingr@.cleanharbors.com> wrote in message
news:%236D0RVrVDHA.2052@.TK2MSFTNGP10.phx.gbl...
> Assume the SQL server is in DMZ domain. You'll need trust relationship set
> up betweenDMZ and your domain.
> "Belinda Rodriguez" <rodrigub@.symbol.com> wrote in message
> news:Oxe8ZhqVDHA.1780@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I am running an NT server in the DMZ and need to connect to SQL Server
> 2000
> > on another box. I am unable to try to ping the SQL box because ping is
> > disabled within the DMZ. Everytime I try to connect I get a Timed-out
> > error. Does anyone know how would I be able to connect to SQL Server?
> >
> > Thanks in advance,
> >
> > Belinda
> >
> >
>

Can't connect to Reporting Services after I rename my computer

Hi,
I have installed SQL 2005 on my Windows 2003 box. After I install SQL
2005, I have configured the Reporting Services and I can connect using
the Management Studio. I had to rename my machine and after I renamed I
can still connect to Database Services from Management Studio. However
I am getting error while I connect to Reporting Services. I have also
tried sp_dropserver <old> and sp_addserver <new>,'local'. It still
doesn't help.
Can someone help me out with fixing this issue.
Thanks,
Prasanna.Prasanna,
When I had the same problem, I ran RSConfig.exe.
Check it for the apprpriate paraemters.
Alan
<csoprasanna@.gmail.com> wrote in message
news:1147394767.664213.99720@.j33g2000cwa.googlegroups.com...
> Hi,
> I have installed SQL 2005 on my Windows 2003 box. After I install SQL
> 2005, I have configured the Reporting Services and I can connect using
> the Management Studio. I had to rename my machine and after I renamed I
> can still connect to Database Services from Management Studio. However
> I am getting error while I connect to Reporting Services. I have also
> tried sp_dropserver <old> and sp_addserver <new>,'local'. It still
> doesn't help.
> Can someone help me out with fixing this issue.
> Thanks,
> Prasanna.
>

Cant connect to Report Server Database

Hello All,
I have my Reportservices installed at a windows 2000 box (RSBox) and a
reportserver Database at a windows 2000 box (DBbox).
I am using Windows authentication.
I have been successully Deploying and viewing MS enterprise Reports .. but
suddenly i got a issue...
When ever I try to deploy or view the deployed reports I get an error message
"The report server cannot open a connection to the report server database. A
connection to the database is required for all requests and processing.
(rsReportServerDatabaseUnavailable) Get Online Help Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection. "
I have checked my Report server database which is running and Reporting
services are also running also I am able to browse to reports level but when
I try to view it I get this error.
Any Idea how I can track this issue. There are other people too who are
owner of these production boxes. I need to trace where the issue is...
any Idea wil be highly appreciated..
Cheers,
siajHello ...
I could solve my Issue .. The userID and Password was locked. I got it
unlocked and restarted the IIS .. bingo it worked
cheers,
siaj
"siaj" wrote:
> Hello All,
> I have my Reportservices installed at a windows 2000 box (RSBox) and a
> reportserver Database at a windows 2000 box (DBbox).
> I am using Windows authentication.
> I have been successully Deploying and viewing MS enterprise Reports .. but
> suddenly i got a issue...
> When ever I try to deploy or view the deployed reports I get an error message
> "The report server cannot open a connection to the report server database. A
> connection to the database is required for all requests and processing.
> (rsReportServerDatabaseUnavailable) Get Online Help Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection. "
> I have checked my Report server database which is running and Reporting
> services are also running also I am able to browse to reports level but when
> I try to view it I get this error.
> Any Idea how I can track this issue. There are other people too who are
> owner of these production boxes. I need to trace where the issue is...
> any Idea wil be highly appreciated..
> Cheers,
> siaj
>

Cant connect to Report server database

Hello All,
I have my Reportservices installed at a windows 2000 box (RSBox) and a
reportserver Database at a windows 2000 box (DBbox).
I am using Windows authentication.
I have been successully Deploying and viewing MS enterprise Reports .. but
suddenly i got a issue...
When ever I try to deploy or view the deployed reports I get an error message
"The report server cannot open a connection to the report server database. A
connection to the database is required for all requests and processing.
(rsReportServerDatabaseUnavailable) Get Online Help Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection. "
I have checked my Report server database which is running and Reporting
services are also running also I am able to browse to reports level but when
I try to view it I get this error.
Any Idea how I can track this issue. There are other people too who are
owner of these production boxes. I need to trace where the issue is...
any Idea wil be highly appreciated..
Cheers,
siajCheck documentation on RSConfig. Set connection related information to what
you think it should be. If it still wouldn't work after that try using SQL
Query analyzer to connect to that database using same connection
information, see if that works.
--
Dmitry Vasilevsky, SQL Server Reporting Services Developer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
---
"siaj" <siaj@.discussions.microsoft.com> wrote in message
news:7E87933B-AF63-4B9D-A187-2D3BA9FBA507@.microsoft.com...
> Hello All,
> I have my Reportservices installed at a windows 2000 box (RSBox) and a
> reportserver Database at a windows 2000 box (DBbox).
> I am using Windows authentication.
> I have been successully Deploying and viewing MS enterprise Reports .. but
> suddenly i got a issue...
> When ever I try to deploy or view the deployed reports I get an error
message
> "The report server cannot open a connection to the report server database.
A
> connection to the database is required for all requests and processing.
> (rsReportServerDatabaseUnavailable) Get Online Help Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection. "
> I have checked my Report server database which is running and Reporting
> services are also running also I am able to browse to reports level but
when
> I try to view it I get this error.
>
> Any Idea how I can track this issue. There are other people too who are
> owner of these production boxes. I need to trace where the issue is...
> any Idea wil be highly appreciated..
> Cheers,
> siaj
>|||Thanks Dmitry...
Do u have any idea from where can I find the username used for the Report
server in clear text as the RSreportServer.config stores it in encrypted
form.
I want to know this as I suspect if this account has got locked due to some
reasons.
cheers
siaj
"Dmitry Vasilevsky [MSFT]" wrote:
> Check documentation on RSConfig. Set connection related information to what
> you think it should be. If it still wouldn't work after that try using SQL
> Query analyzer to connect to that database using same connection
> information, see if that works.
> --
> Dmitry Vasilevsky, SQL Server Reporting Services Developer
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> ---
> "siaj" <siaj@.discussions.microsoft.com> wrote in message
> news:7E87933B-AF63-4B9D-A187-2D3BA9FBA507@.microsoft.com...
> > Hello All,
> >
> > I have my Reportservices installed at a windows 2000 box (RSBox) and a
> > reportserver Database at a windows 2000 box (DBbox).
> > I am using Windows authentication.
> >
> > I have been successully Deploying and viewing MS enterprise Reports .. but
> > suddenly i got a issue...
> >
> > When ever I try to deploy or view the deployed reports I get an error
> message
> > "The report server cannot open a connection to the report server database.
> A
> > connection to the database is required for all requests and processing.
> > (rsReportServerDatabaseUnavailable) Get Online Help Login failed for user
> > '(null)'. Reason: Not associated with a trusted SQL Server connection. "
> > I have checked my Report server database which is running and Reporting
> > services are also running also I am able to browse to reports level but
> when
> > I try to view it I get this error.
> >
> >
> > Any Idea how I can track this issue. There are other people too who are
> > owner of these production boxes. I need to trace where the issue is...
> >
> > any Idea wil be highly appreciated..
> >
> > Cheers,
> > siaj
> >
>|||Hello ...
I could solve my Issue .. The userID and Password was locked. I got it
unlocked and restarted the IIS .. bingo it worked
cheers,
siaj
"siaj" wrote:
> Hello All,
> I have my Reportservices installed at a windows 2000 box (RSBox) and a
> reportserver Database at a windows 2000 box (DBbox).
> I am using Windows authentication.
> I have been successully Deploying and viewing MS enterprise Reports .. but
> suddenly i got a issue...
> When ever I try to deploy or view the deployed reports I get an error message
> "The report server cannot open a connection to the report server database. A
> connection to the database is required for all requests and processing.
> (rsReportServerDatabaseUnavailable) Get Online Help Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection. "
> I have checked my Report server database which is running and Reporting
> services are also running also I am able to browse to reports level but when
> I try to view it I get this error.
>
> Any Idea how I can track this issue. There are other people too who are
> owner of these production boxes. I need to trace where the issue is...
> any Idea wil be highly appreciated..
> Cheers,
> siaj
>

Can't connect to new sql server instance

I installed sql server 2000 on a box that already has sql server 2005
installed. I used an instance name of "{machine name}/mssql2k" and I'm
trying to connect using {machine name}/mssql2k. When I open SQL Server
Management Studio and try to connect to the new instance, I get the message
shown below. Please let me know what I need to do to connect.
Thanks,
Keith
TITLE: Connect to Server
Cannot connect to LT-E48643/mssql2k.
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
For help, click:
http://go.microsoft.com/fwlink?ProdN...3&LinkId=20476
BUTTONS:
OK
Change the forward slash to a backward slash, and try again.
Linchi
"Keithb" wrote:

> I installed sql server 2000 on a box that already has sql server 2005
> installed. I used an instance name of "{machine name}/mssql2k" and I'm
> trying to connect using {machine name}/mssql2k. When I open SQL Server
> Management Studio and try to connect to the new instance, I get the message
> shown below. Please let me know what I need to do to connect.
> Thanks,
> Keith
> TITLE: Connect to Server
> --
> Cannot connect to LT-E48643/mssql2k.
> --
> 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: Named Pipes Provider, error: 40 - Could not open a connection to
> SQL Server) (Microsoft SQL Server, Error: 53)
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...3&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
>
|||That did it.
Thanks,
Keith
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:9321139D-EDCF-4D8B-9C06-D67A8A1005E1@.microsoft.com...[vbcol=seagreen]
> Change the forward slash to a backward slash, and try again.
> Linchi
> "Keithb" wrote:

Can't connect to new sql server instance

I installed sql server 2000 on a box that already has sql server 2005
installed. I used an instance name of "{machine name}/mssql2k" and I'm
trying to connect using {machine name}/mssql2k. When I open SQL Server
Management Studio and try to connect to the new instance, I get the message
shown below. Please let me know what I need to do to connect.
Thanks,
Keith
TITLE: Connect to Server
--
Cannot connect to LT-E48643/mssql2k.
--
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
--
BUTTONS:
OK
--Change the forward slash to a backward slash, and try again.
Linchi
"Keithb" wrote:
> I installed sql server 2000 on a box that already has sql server 2005
> installed. I used an instance name of "{machine name}/mssql2k" and I'm
> trying to connect using {machine name}/mssql2k. When I open SQL Server
> Management Studio and try to connect to the new instance, I get the message
> shown below. Please let me know what I need to do to connect.
> Thanks,
> Keith
> TITLE: Connect to Server
> --
> Cannot connect to LT-E48643/mssql2k.
> --
> 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: Named Pipes Provider, error: 40 - Could not open a connection to
> SQL Server) (Microsoft SQL Server, Error: 53)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
>|||That did it.
Thanks,
Keith
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:9321139D-EDCF-4D8B-9C06-D67A8A1005E1@.microsoft.com...
> Change the forward slash to a backward slash, and try again.
> Linchi
> "Keithb" wrote:
>> I installed sql server 2000 on a box that already has sql server 2005
>> installed. I used an instance name of "{machine name}/mssql2k" and I'm
>> trying to connect using {machine name}/mssql2k. When I open SQL Server
>> Management Studio and try to connect to the new instance, I get the
>> message
>> shown below. Please let me know what I need to do to connect.
>> Thanks,
>> Keith
>> TITLE: Connect to Server
>> --
>> Cannot connect to LT-E48643/mssql2k.
>> --
>> 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: Named Pipes Provider, error: 40 - Could not open a connection
>> to
>> SQL Server) (Microsoft SQL Server, Error: 53)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
>> --
>> BUTTONS:
>> OK
>> --
>>

Can't connect to new sql server instance

I installed sql server 2000 on a box that already has sql server 2005
installed. I used an instance name of "{machine name}/mssql2k" and I'm
trying to connect using {machine name}/mssql2k. When I open SQL Server
Management Studio and try to connect to the new instance, I get the message
shown below. Please let me know what I need to do to connect.
Thanks,
Keith
TITLE: Connect to Server
--
Cannot connect to LT-E48643/mssql2k.
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
For help, click:
http://go.microsoft.com/fwlink?Prod...53&LinkId=20476
BUTTONS:
OK
--Change the forward slash to a backward slash, and try again.
Linchi
"Keithb" wrote:

> I installed sql server 2000 on a box that already has sql server 2005
> installed. I used an instance name of "{machine name}/mssql2k" and I'
m
> trying to connect using {machine name}/mssql2k. When I open SQL Serve
r
> Management Studio and try to connect to the new instance, I get the messag
e
> shown below. Please let me know what I need to do to connect.
> Thanks,
> Keith
> TITLE: Connect to Server
> --
> Cannot connect to LT-E48643/mssql2k.
> --
> 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: Named Pipes Provider, error: 40 - Could not open a connection t
o
> SQL Server) (Microsoft SQL Server, Error: 53)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...53&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
>|||That did it.
Thanks,
Keith
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:9321139D-EDCF-4D8B-9C06-D67A8A1005E1@.microsoft.com...[vbcol=seagreen]
> Change the forward slash to a backward slash, and try again.
> Linchi
> "Keithb" wrote:
>