Cant start SQL 2005 with /T 1400.

Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
prompt I:
sqlservr.exe -s development\mysql2k5 -T 1400
(also tried /T 1400)
and I get:
Application popup: SQL Server : Your SQL Server installation is either
corrupt or has been tampered with (Error: Instance name exceeds maximum
length.). Please uninstall then re-run setup to correct this problem
I've been trying lots of variations of this, as well as adding the -T to the
end of the startup parameters in the Config Manager. I know that the message
is bogus because I can run this instance of SQL from the Config Manager
without the -T.
Any ideas?
TIA, ChrisRSpecify only the instance name on the command prompt parameter:
sqlservr.exe -s mysql2k5 -T 1400
Also, you don't need trace flag 1400 once you install SQL 2005 SP1.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
> the
> end of the startup parameters in the Config Manager. I know that the
> message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>|||Hi,
Do you need to enable trace flag 1400 to turn on Database Mirroring? That is
no longer needed if you apply Service Pack 1. I would recommend to try SP1
instead.
Ben Nevarez, MCDBA, OCP
Database Administrator
"ChrisR" wrote:
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to the
> end of the startup parameters in the Config Manager. I know that the message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>
>|||Thank you both.
"ChrisR" <ChrisR@.noEmail.com> wrote in message
news:%235OcHtmkGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Howdy all. Im trying to start up SQL 2005 with /T 1400. From the command
> prompt I:
> sqlservr.exe -s development\mysql2k5 -T 1400
> (also tried /T 1400)
> and I get:
> Application popup: SQL Server : Your SQL Server installation is either
> corrupt or has been tampered with (Error: Instance name exceeds maximum
> length.). Please uninstall then re-run setup to correct this problem
> I've been trying lots of variations of this, as well as adding the -T to
the
> end of the startup parameters in the Config Manager. I know that the
message
> is bogus because I can run this instance of SQL from the Config Manager
> without the -T.
> Any ideas?
> TIA, ChrisR
>

Can't shrink a Transaction Log File

I backed up my log file and attempted to shrink it with DBCC
SHRINKFILE. The command executes but leaves the transaction log at
it's current size. I know that an uncommited tansaction can cause this
to occur.
a) How do I test for this?
b)How do I get rid of it?
Regards
John L
Hi Gemel,
Try to backup your transaction log again and then try to shrink the file.
If its possible to loose youre trans log info(i guess you dont) change the
recovery model to simple(you'll loose your log info), shrink your tlog to the
desired size, then change recovery model to full and finally backup youre
database.
Hope that this can help you.
Regards
"gemel" wrote:

> I backed up my log file and attempted to shrink it with DBCC
> SHRINKFILE. The command executes but leaves the transaction log at
> it's current size. I know that an uncommited tansaction can cause this
> to occur.
> a) How do I test for this?
> b)How do I get rid of it?
> Regards
> John L
>
|||If you have a long running open transaction that could prevent the log from
shrinking..
DBCC opentran will show you the oldest transaction still in transaction
state.
You might also try
DBCC SQLPERF(logspace) to see how much space in the log is used
also
DBCC loginfo ( google on this to find more details.)
hope this helps
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"gemel" <jonel@.glenavon1.demon.co.uk> wrote in message
news:gdhm31tl8rs5t2804ibhc9onv36lee5evb@.4ax.com...
>I backed up my log file and attempted to shrink it with DBCC
> SHRINKFILE. The command executes but leaves the transaction log at
> it's current size. I know that an uncommited tansaction can cause this
> to occur.
> a) How do I test for this?
> b)How do I get rid of it?
> Regards
> John L

Can't shrink a Transaction Log File

I backed up my log file and attempted to shrink it with DBCC
SHRINKFILE. The command executes but leaves the transaction log at
it's current size. I know that an uncommited tansaction can cause this
to occur.
a) How do I test for this?
b)How do I get rid of it?
Regards
John LHi Gemel,
Try to backup your transaction log again and then try to shrink the file.
If its possible to loose youre trans log info(i guess you dont) change the
recovery model to simple(you'll loose your log info), shrink your tlog to the
desired size, then change recovery model to full and finally backup youre
database.
Hope that this can help you.
Regards
"gemel" wrote:
> I backed up my log file and attempted to shrink it with DBCC
> SHRINKFILE. The command executes but leaves the transaction log at
> it's current size. I know that an uncommited tansaction can cause this
> to occur.
> a) How do I test for this?
> b)How do I get rid of it?
> Regards
> John L
>|||If you have a long running open transaction that could prevent the log from
shrinking..
DBCC opentran will show you the oldest transaction still in transaction
state.
You might also try
DBCC SQLPERF(logspace) to see how much space in the log is used
also
DBCC loginfo ( google on this to find more details.)
hope this helps
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"gemel" <jonel@.glenavon1.demon.co.uk> wrote in message
news:gdhm31tl8rs5t2804ibhc9onv36lee5evb@.4ax.com...
>I backed up my log file and attempted to shrink it with DBCC
> SHRINKFILE. The command executes but leaves the transaction log at
> it's current size. I know that an uncommited tansaction can cause this
> to occur.
> a) How do I test for this?
> b)How do I get rid of it?
> Regards
> John L

Can't shrink a Transaction Log File

I backed up my log file and attempted to shrink it with DBCC
SHRINKFILE. The command executes but leaves the transaction log at
it's current size. I know that an uncommited tansaction can cause this
to occur.
a) How do I test for this?
b)How do I get rid of it?
Regards
John LHi Gemel,
Try to backup your transaction log again and then try to shrink the file.
If its possible to loose youre trans log info(i guess you dont) change the
recovery model to simple(you'll loose your log info), shrink your tlog to th
e
desired size, then change recovery model to full and finally backup youre
database.
Hope that this can help you.
Regards
"gemel" wrote:

> I backed up my log file and attempted to shrink it with DBCC
> SHRINKFILE. The command executes but leaves the transaction log at
> it's current size. I know that an uncommited tansaction can cause this
> to occur.
> a) How do I test for this?
> b)How do I get rid of it?
> Regards
> John L
>|||If you have a long running open transaction that could prevent the log from
shrinking..
DBCC opentran will show you the oldest transaction still in transaction
state.
You might also try
DBCC SQLPERF(logspace) to see how much space in the log is used
also
DBCC loginfo ( google on this to find more details.)
hope this helps
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"gemel" <jonel@.glenavon1.demon.co.uk> wrote in message
news:gdhm31tl8rs5t2804ibhc9onv36lee5evb@.
4ax.com...
>I backed up my log file and attempted to shrink it with DBCC
> SHRINKFILE. The command executes but leaves the transaction log at
> it's current size. I know that an uncommited tansaction can cause this
> to occur.
> a) How do I test for this?
> b)How do I get rid of it?
> Regards
> John Lsql

Can't Set variable Through Command Line

Hello everyone!

Bit of a problem executing a DTS command from a command line.

I have the following variables defined in my package:

UserVarchar1
UserVarchar2
UserVarchar3

All have a scope of Package, all of the mstrings

The command I'm attempting to run in 1 line is:

DTEXEC /FILE "C:\SSIS Packages\ED-Customers\Package.dtsx"
/SET \Package.Variables[User::UserVarchar1].value;"10"
/SET \Package.Variables[User::UserVarchar2].value;"30719"
/SET \Package.Variables[User::UserVarchar3].value;"BILLTO"

Description: The package path referenced an object that cannot be found: "\Package.Variables[User::UserVarchar1].value". This occurs when an attempt is made to resolve a package path to an object that cannot be found.

DTExec: Could not set \Package.Variables[User::UserVarchar1].value value to 10.

Any idea why?

Thanks for the help!What happens if you try:

\Package.Variables[User::UserVarchar1].Properties[Value];10|||For some reference:
http://blogs.conchango.com/jamiethomson/archive/2007/03/13/SSIS_3A00_-Property-Paths-syntax.aspx|||

How are you validating the path?

Check the path and remember the variables names are case sensitives.

|||

The syntax is wrong.

Check Phil's posts above.

-Jamie

|||I tried that.. Still says it can't assign it the value of 10.

It's case-accurate, in both path and variable names.

Description: The package path referenced an object that cannot be found: "\Package.Variables[User::UserVarchar1].value". This occurs when an attempt is made to resolve a package path to an object that cannot be found.

DTExec: Could not set \Package.Variables[User::UserVarchar1].value value to 10.

Is there something I'm missing in the design of the package, perhaps? All I did was add the variables to the package. Another variable uses these values and evaluates it as an expression. Doesn't seem too complex, yet I'm still miffed about why this won't execute.

Incidently, if I run the package WITHOUT variables, it will in fact run successfully.|||Adam, make sure the scope of that variable is at the package level, not some other component.|||By any chance is the ReadOnly property of the variable set to True? I get the same error if the value is true; if you want ot assign values at run time it should be set to false|||Thanks for the input, everyone! I finally figured it out.

The first reply was correct. I didn't notice .Properties[Value] in the first reply. Don't know how I missed it.

Sorry, it's been one fo those mornings..

Thanks again, everyone!

Can't install SQL Server Express 2005 in quiet mode

I'm trying to use a bootstrapper with SQL Server Express 2005, but I'm having difficulty with the installation. I'm using the command line:
SQLEXPR.EXE /qb INSTANCENAME=myInstanceName SAPWD=mySaPassword

and it seems to fail right at the system configuration check. One of the log files says "Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 0"

I can post the contents of the log files if anyone needs them.Try this. Please also check the file template.ini located at the same directory for setup.exe. You can find sample command line to install SQL Server 2005 in silent mode.

start /wait setup.exe /qb ADDLOCAL=SQL_Engine INSTANCENAME="OneExpress" SQLACCOUNT="<domain\user>" SQLPASSWORD="<strong password>" SQLBROWSERACCOUNT="<domain\user>" SQLBROWSERPASSWORD="<strong password>" SQLAUTOSTART=1 SQLBROWSERAUTOSTART=1|||The following command line installs SQL Server Express 2005 in quiet mode (without any user input):

SQLEXPR.EXE /qb ADDLOCAL=ALL INSTANCENAME=myInstanceName SAPWD=mySaPassword

As you can see, the original command line I was having problems with did not include the "ADDLOCAL=ALL" option.

Cant install MSDE Rel A

I am trying to install MSDE Rel A on a Windows XP SP2 machine with no luck no
matter what I try. I am typing the following at the command line.
setup.exe /L*v C:\MSDElog.txt SAPWD="password" SECURITYMODE=SQL
Below are the portions of the error log that contain RETURN VALUE 3,
including sevral lines before and after. Any help would be appreciated.
Error the following data files were found in data directory:
C:\Program Files\Microsoft SQL Server\MSSQL\Data\msdbdata.mdf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\msdblog.ldf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\modellog.ldf
Setup has detected existing data/log files. Please make sure to delete/move
the files before re-running setup
Ending custom action DetectExistingData
Action ended 13:58:34:
DetectExistingData.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3.
Action ended 13:58:34: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlInstanceName = MSSQLSERVER
Property(S): SqlSecurityMode = SQL
Property(S): SqlSa...
Property(S): SqlDisableNetworkProtocols = 1
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): INSTALLLEVEL = 3
Property(S): LIMITUI = 1
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(S): ProductLanguage = 1033
Property(S): SqlStates = 0
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SqlFeature = SqlRun
MSI (s) (80:D8) [13:58:34:748]: MainEngineThread is returning 1603
MSI (s) (80:A4) [13:58:34:748]: Destroying RemoteAPI object.
MSI (s) (80:60) [13:58:34:748]: Custom Action Manager thread ending.
MSI (c) (3C:E4) [13:58:34:748]: Back from server. Return value: 1603
MSI (c) (3C:E4) [13:58:34:748]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
Action ended 13:58:34: INSTALL. Return value 3.
Property(C): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(C): VersionNT = 501
Property(C): ALLUSERS = 1
Property(C): ARPNOMODIFY = 1
Property(C): DefaultUIFont = Tahoma8
Property(C): INSTALLLEVEL = 3
Property(C): LIMITUI = 1
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Microsoft SQL Server Desktop Engine
Property(C): ProductVersion = 8.00.761
Property(C): MsiHiddenProperties = SqlSa...
Property(S): SqlStates = 0
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SqlFeature = SqlRun
MSI (s) (80:D8) [13:58:34:748]: MainEngineThread is returning 1603
MSI (s) (80:A4) [13:58:34:748]: Destroying RemoteAPI object.
MSI (s) (80:60) [13:58:34:748]: Custom Action Manager thread ending.
MSI (c) (3C:E4) [13:58:34:748]: Back from server. Return value: 1603
MSI (c) (3C:E4) [13:58:34:748]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
Action ended 13:58:34: INSTALL. Return value 3.
Property(C): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(C): VersionNT = 501
Property(C): ALLUSERS = 1
Property(C): ARPNOMODIFY = 1
Property(C): DefaultUIFont = Tahoma8
Property(C): INSTALLLEVEL = 3
Property(C): LIMITUI = 1
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(C): ProductLanguage = 1033
looks like the setup is detecting data from a a previous install of SQL.
"C:\Program Files\Microsoft SQL Server\MSSQL\Data\msdbdata.mdf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\msdblog.ldf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf
C:\Program Files\Microsoft SQL Server\MSSQL\Data\modellog.ldf
"
You can simply delete these assuming they are not needed any more.
Andrew Robinson
www.binaryocean.com
www.bellinghamdotnet.org
"MEI Admin" <MEI Admin@.discussions.microsoft.com> wrote in message
news:325180D7-9B24-4941-B5A7-B4E7351DD83D@.microsoft.com...
>I am trying to install MSDE Rel A on a Windows XP SP2 machine with no luck
>no
> matter what I try. I am typing the following at the command line.
> setup.exe /L*v C:\MSDElog.txt SAPWD="password" SECURITYMODE=SQL
> Below are the portions of the error log that contain RETURN VALUE 3,
> including sevral lines before and after. Any help would be appreciated.
> Error the following data files were found in data directory:
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\msdbdata.mdf
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\msdblog.ldf
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf
> C:\Program Files\Microsoft SQL Server\MSSQL\Data\modellog.ldf
> Setup has detected existing data/log files. Please make sure to
> delete/move
> the files before re-running setup
> Ending custom action DetectExistingData
> Action ended 13:58:34:
> DetectExistingData.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3.
> Action ended 13:58:34: INSTALL. Return value 3.
> Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
> Property(S): SqlDataDir = C:\Program Files\Microsoft SQL Server\
> Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
> Property(S): SqlInstanceName = MSSQLSERVER
> Property(S): SqlSecurityMode = SQL
> Property(S): SqlSa...
> Property(S): SqlDisableNetworkProtocols = 1
> Property(S): VersionNT = 501
> Property(S): ALLUSERS = 1
> Property(S): ARPNOMODIFY = 1
> Property(S): DefaultUIFont = Tahoma8
> Property(S): INSTALLLEVEL = 3
> Property(S): LIMITUI = 1
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
> Property(S): ProductLanguage = 1033
>
> Property(S): SqlStates = 0
> Property(S): ROOTDRIVE = C:\
> Property(S): CostingComplete = 1
> Property(S): OutOfDiskSpace = 0
> Property(S): OutOfNoRbDiskSpace = 0
> Property(S): PrimaryVolumeSpaceAvailable = 0
> Property(S): PrimaryVolumeSpaceRequired = 0
> Property(S): PrimaryVolumeSpaceRemaining = 0
> Property(S): SqlFeature = SqlRun
> MSI (s) (80:D8) [13:58:34:748]: MainEngineThread is returning 1603
> MSI (s) (80:A4) [13:58:34:748]: Destroying RemoteAPI object.
> MSI (s) (80:60) [13:58:34:748]: Custom Action Manager thread ending.
> MSI (c) (3C:E4) [13:58:34:748]: Back from server. Return value: 1603
> MSI (c) (3C:E4) [13:58:34:748]: Decrementing counter to disable shutdown.
> If
> counter >= 0, shutdown will be denied. Counter after decrement: -1
> Action ended 13:58:34: INSTALL. Return value 3.
> Property(C): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
> Property(C): VersionNT = 501
> Property(C): ALLUSERS = 1
> Property(C): ARPNOMODIFY = 1
> Property(C): DefaultUIFont = Tahoma8
> Property(C): INSTALLLEVEL = 3
> Property(C): LIMITUI = 1
> Property(C): Manufacturer = Microsoft Corporation
> Property(C): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
> Property(C): ProductLanguage = 1033
> Property(C): ProductName = Microsoft SQL Server Desktop Engine
> Property(C): ProductVersion = 8.00.761
> Property(C): MsiHiddenProperties = SqlSa...
>
> Property(S): SqlStates = 0
> Property(S): ROOTDRIVE = C:\
> Property(S): CostingComplete = 1
> Property(S): OutOfDiskSpace = 0
> Property(S): OutOfNoRbDiskSpace = 0
> Property(S): PrimaryVolumeSpaceAvailable = 0
> Property(S): PrimaryVolumeSpaceRequired = 0
> Property(S): PrimaryVolumeSpaceRemaining = 0
> Property(S): SqlFeature = SqlRun
> MSI (s) (80:D8) [13:58:34:748]: MainEngineThread is returning 1603
> MSI (s) (80:A4) [13:58:34:748]: Destroying RemoteAPI object.
> MSI (s) (80:60) [13:58:34:748]: Custom Action Manager thread ending.
> MSI (c) (3C:E4) [13:58:34:748]: Back from server. Return value: 1603
> MSI (c) (3C:E4) [13:58:34:748]: Decrementing counter to disable shutdown.
> If
> counter >= 0, shutdown will be denied. Counter after decrement: -1
> Action ended 13:58:34: INSTALL. Return value 3.
> Property(C): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
> Property(C): VersionNT = 501
> Property(C): ALLUSERS = 1
> Property(C): ARPNOMODIFY = 1
> Property(C): DefaultUIFont = Tahoma8
> Property(C): INSTALLLEVEL = 3
> Property(C): LIMITUI = 1
> Property(C): Manufacturer = Microsoft Corporation
> Property(C): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
> Property(C): ProductLanguage = 1033

can't import .sql

i uses sql server 2005 express ,and type command as follow to import data : osql -E -S (local)\NetSDK -i InstNwnd.sql (as in Data Access - Bind Data in a ComboBox sample) but got an error :

D:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Samples\Setup>osql -E -S (lo
cal)\NetSDK -i InstNwnd.sql
[SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance
Specified [xFFFFFFFF].
[SQL Native Client]Login timeout expired
[SQL Native Client]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.

what's is it ? and how i can import data ? thanks

Hi,

if you don′t have SQL Browser Service started, make sure that the instance you want to connect to is on the default port (1433) or you specify the portname after the instancename e.g. (local)\NETSDK,1477. If you have SQL Bworser service started, it should redirect you to the port of the named instance. If that all did not help, meke sure that you enabled remote connections in SQl Server. I have a screencast for this published on my site under Screencast > Enable remote connections.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||ya, the problems is the port , it's ok after i change it . Thanks|||As you are new to the forums, please make sure to mark an answer as correct after the problem is solved with the suggestion within a post.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de