Can not connect to non-default instance from remote computer

I installed SQL2005 as default instance.
After that I installed SQL2000 with instance name "SQL2K". Then I installed
SP4.
I can'not connect to SQL2K instance from remote machine. But if I log on at
machine on which SQL Server installed I can connect to instance.
And I can connect to default instance (SQL2005) from remote machine.
How to solve this problem?
Is the SQL Server Browser service running? It helps resolve names of named
instances to the port number. Since SQL Server 2005 is the default instance,
it is probably using port 1433. Therefore SQL Server 2000 must be using some
other port, but you don't know which port, but the SQL Server Browser
service will know.
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Alexey Rokhin" <ar@.hotmail.com> wrote in message
news:%23PF4wc16FHA.1416@.TK2MSFTNGP09.phx.gbl...
>I installed SQL2005 as default instance.
> After that I installed SQL2000 with instance name "SQL2K". Then I
> installed SP4.
> I can'not connect to SQL2K instance from remote machine. But if I log on
> at machine on which SQL Server installed I can connect to instance.
> And I can connect to default instance (SQL2005) from remote machine.
> How to solve this problem?
>

Can not connect to non-default instance from remote computer

I installed SQL2005 as default instance.
After that I installed SQL2000 with instance name "SQL2K". Then I installed
SP4.
I can'not connect to SQL2K instance from remote machine. But if I log on at
machine on which SQL Server installed I can connect to instance.
And I can connect to default instance (SQL2005) from remote machine.
How to solve this problem?Is the SQL Server Browser service running? It helps resolve names of named
instances to the port number. Since SQL Server 2005 is the default instance,
it is probably using port 1433. Therefore SQL Server 2000 must be using some
other port, but you don't know which port, but the SQL Server Browser
service will know.
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Alexey Rokhin" <ar@.hotmail.com> wrote in message
news:%23PF4wc16FHA.1416@.TK2MSFTNGP09.phx.gbl...
>I installed SQL2005 as default instance.
> After that I installed SQL2000 with instance name "SQL2K". Then I
> installed SP4.
> I can'not connect to SQL2K instance from remote machine. But if I log on
> at machine on which SQL Server installed I can connect to instance.
> And I can connect to default instance (SQL2005) from remote machine.
> How to solve this problem?
>

Can not browse sql 2000 tables from SSMS

Hello,

I get an error message( see below) when I try to browse tables of a SQL2k server from SSMS, but I can browse those tables in sql query analyzer with no problems.

Do I need to change any settings in SSMS to work around this error?

TITLE: Microsoft SQL Server Management Studio

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

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

ADDITIONAL INFORMATION:

Lock request time out period exceeded. (Microsoft SQL Server, Error: 1222)

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

BUTTONS:

OK

thanks,
Saptagiri

Please file a defect report for this issue here: http://lab.msdn.microsoft.com/productfeedback/Default.aspx

Reports filed on the feedback center are used to prioritize work in future versions and service packs. You can even vote for other the bugs reports filed by other people. The more votes a defect gets, the higher its priority is for being fixed.

Thanks,
Steve

Can not attach MDF from HDS LUN

Hi..

We are trying to attach a database (MDF File without LDF File) in SQL2K SP4

MDF File is in HDS (Hitachi Data Storage) Lun or SAN Storage.

When we try attach the MDF File, we are getting an error. The error message is :

" Error 1813: Could not open new database 'Test'. CREATE DATABASE is aborted.

Device activation error. The physical file name 'F:\SQLData\Test_log.ldf' maybe incorrect "

When We try attach the MDF File, but We move the MDF File into Local Hard Drive (Drive C:), then We success to attached the MDF File and the LDF File is automaticlly generated without error.

i'm waiting for the solution

Thank's.

Brgds,

Dwiharto

How did you attach it? Try using sp_attach_single_file_db stored procedure instead.

Whether the data file resides on the SAN or not should not matter here.|||

I had try it before, but it is still doesn't working and still had same error message.

btw thanks for ur advice.

maybe u can tell me another way?

Thank's a lot Friend ...

|||Can you post the exact attach statement.|||

the statement :

sp_attach_single_file_db @.dbname = 'test',
@.physname = 'F:\SQLData\Test.mdf'

Thank's..

|||

The statement looks valid. (F:\) is a locally attached SAN, right? If this is a network attached san, you need to turn on trace flag (1807). Also, does the account used to start sqlserver service has full right to the SAN?