Error executing extended stored procedure: Invalid Parameter

When I try to connect to sql server instance I received this error:
TITLE: Microsoft SQL Server Management Studio
--
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
ADDITIONAL INFORMATION:
Error executing extended stored procedure: Invalid Parameter
Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
Server, Error: 22001)
when i click refresh button i am able to see my schema, but i can't see the
properties of my base and any table properties. I receive error:
TITLE: Microsoft SQL Server Management Studio
--
Cannot show requested dialog.
--
ADDITIONAL INFORMATION:
Cannot show requested dialog. (SqlMgmt)
--
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
Error executing extended stored procedure: Invalid Parameter
Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
Server, Error: 22001)
--
BUTTONS:
OK
--
also the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names is
locked and can not be opened.
After a reboot the key is now readable and the 2005 instance can be
connected to without these messages.
But after a while it does it again.
does anyone have any idea what is going wrong?Hi
My guess is that you have some group policy or Anti-virus/ISD system that is
locking down this registry key.
John
"nikolakg" wrote:
> When I try to connect to sql server instance I received this error:
> TITLE: Microsoft SQL Server Management Studio
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> ADDITIONAL INFORMATION:
> Error executing extended stored procedure: Invalid Parameter
> Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
> Server, Error: 22001)
>
> when i click refresh button i am able to see my schema, but i can't see the
> properties of my base and any table properties. I receive error:
> TITLE: Microsoft SQL Server Management Studio
> --
> Cannot show requested dialog.
> --
> ADDITIONAL INFORMATION:
> Cannot show requested dialog. (SqlMgmt)
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Error executing extended stored procedure: Invalid Parameter
> Error executing extended stored procedure: Invalid Parameter (Microsoft SQL
> Server, Error: 22001)
>
> --
> BUTTONS:
> OK
> --
>
> also the registry key
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names is
> locked and can not be opened.
> After a reboot the key is now readable and the 2005 instance can be
> connected to without these messages.
> But after a while it does it again.
> does anyone have any idea what is going wrong?

Error during Instance Install

Building an Active/Active/Passive SQL 2000 cluster on top of a 3 node 2003
server cluster. As I go to install I end up getting a "An error occured
while creating virtual server resources for clustering. The system cannot
find the file specified."
I've gone through KB 815431 and made sure the named piped alias is
configured properly and it appears to be working correctly. Let me know if
anyone has any ideas. Here's my sqlstp.log up to the point of the error.
16:12:58 Begin Setup
16:12:58 8.00.194
16:12:58 Mode = Normal
16:12:58 ModeType = NORMAL
16:12:58 GetDefinitionEx returned: 0, Extended: 0x0
16:12:58 ValueFTS returned: 1
16:12:58 ValuePID returned: 1
16:12:58 ValueLic returned: 1
16:12:58 System: Windows NT Enterprise Server
16:12:58 SQL Server ProductType: Enterprise Edition [0x3]
16:12:58 IsNTCluster returned: 1
16:12:58 Begin Action: SetupInitialize
16:12:58 End Action SetupInitialize
16:12:58 Begin Action: SetupInstall
16:12:58 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
16:12:58 CommonFilesDir=C:\Program Files\Common Files
16:12:58 Windows Directory=C:\WINDOWS\
16:12:58 Program Files=C:\Program Files\
16:12:58 TEMPDIR=C:\WINDOWS\TEMP\
16:12:58 Begin Action: SetupInstall
16:12:58 digpid size : 256
16:12:58 digpid size : 164
16:12:58 Begin Action: CheckFixedRequirements
16:12:58 Platform ID: 0xf00000
16:12:58 Version: 5.2.3790
16:12:58 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.279
16:12:58 End Action: CheckFixedRequirements
16:12:58 Begin Action: ShowDialogs
16:12:58 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
16:12:58 Begin Action ShowDialogsHlpr: 0x1
16:12:58 Begin Action: DialogShowSdWelcome
16:13:01 End Action DialogShowSdWelcome
16:13:01 Dialog 0x1 returned: 1
16:13:01 End Action ShowDialogsHlpr
16:13:01 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
16:13:01 Begin Action ShowDialogsHlpr: 0x2
16:13:01 Begin Action: DialogShowSdMachineName
16:13:15 ShowDlgMachine returned: 1
16:13:15 Name = NPBSQLC7, Type = 0x10000008
16:13:15 Begin Action: CheckRequirements
16:13:15 Processor Architecture: x86 (Pentium)
16:13:15 ComputerName: NPBSQL6
16:13:15 User Name: <Removed>
16:13:15 IsAllAccessAllowed returned: 1
16:13:15 OS Language: 0x409
16:13:15 End Action CheckRequirements
16:13:15 This combination of Package and Operating System allows a full
product install.
16:13:15 End Action DialogShowSdMachineName
16:13:15 begin ShowDialogsUpdateMask
16:13:15 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0
16:13:15 Updated Dialog Mask: 0xbf3c037, Disable Back = 0x1
16:13:15 Dialog 0x2 returned: 0
16:13:15 End Action ShowDialogsHlpr
16:13:15 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
16:13:15 Begin Action ShowDialogsHlpr: 0x4
16:13:15 Begin Action: DialogShowSdInstallMode
16:13:15 InstallMode : 0x1
16:13:15 End Action DialogShowSdInstallMode
16:13:15 begin ShowDialogsUpdateMask
16:13:15 nFullMask = 0xbf3c037, nCurrent = 0x4, nDirection = 1
16:13:15 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
16:13:15 Dialog 0x4 returned: 1
16:13:15 End Action ShowDialogsHlpr
16:13:15 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
16:13:15 Begin Action ShowDialogsHlpr: 0x10
16:13:15 Begin Action: DialogShowSdRegisterUserEx
16:13:17 End Action DialogShowSdRegisterUserEx
16:13:17 begin ShowDialogsUpdateMask
16:13:17 nFullMask = 0x1bf7c037, nCurrent = 0x10, nDirection = 1
16:13:17 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
16:13:17 Dialog 0x10 returned: 1
16:13:17 End Action ShowDialogsHlpr
16:13:17 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
16:13:17 Begin Action ShowDialogsHlpr: 0x20
16:13:17 Begin Action: DialogShowSdLicense
16:13:17 End Action DialogShowSdLicense
16:13:17 Dialog 0x20 returned: 1
16:13:17 End Action ShowDialogsHlpr
16:13:17 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14
16:13:17 Begin Action ShowDialogsHlpr: 0x4000
16:13:17 Begin Action: DialogShowSdVirtualServer
16:13:27 ShowDlgVirtualServer returned: 0
16:13:27 Ipaddress = 10.10.0.58,255.255.252.0,SQL2 Public Team
16:13:27 szNewList = 10.10.0.58,255.255.252.0,SQL2 Public Team
16:13:27 szModifiedList =
16:13:27 szRemovedList =
16:13:27 End Action DialogShowSdVirtualServer
16:13:27 begin ShowDialogsUpdateMask
16:13:27 nFullMask = 0x1bf7c037, nCurrent = 0x4000, nDirection = 1
16:13:27 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
16:13:27 Dialog 0x4000 returned: 1
16:13:27 End Action ShowDialogsHlpr
16:13:27 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15
16:13:27 Begin Action ShowDialogsHlpr: 0x8000
16:13:27 Begin Action : DialogShowSdDiskGroups
16:13:30 ShowDlgDiskGroups returned: 1
16:13:30 Disk Group = NPBSQLC7
16:13:30 End Action : DialogShowSdDiskGroups
16:13:30 begin ShowDialogsUpdateMask
16:13:30 nFullMask = 0x1bf7c037, nCurrent = 0x8000, nDirection = 1
16:13:30 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
16:13:30 Dialog 0x8000 returned: 1
16:13:30 End Action ShowDialogsHlpr
16:13:30 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16
16:13:30 Begin Action ShowDialogsHlpr: 0x10000
16:13:30 Begin Action: DialogShowSdClusterDef
16:13:31 ShowDlgClusterDef returned: 1
16:13:31 PrefOwners = NPBSQL6,NPBSQL7,NPBSQL8, NumIp = 3
16:13:31 Begin Action : ValidateNodeActions
16:13:31 Begin Action : ValidateNodeActions
16:13:31 End Action : ValidateNodeActions
16:13:31 End Action : ValidateNodeActions
16:13:31 End Action DialogShowSdClusterDef
16:13:31 begin ShowDialogsUpdateMask
16:13:31 nFullMask = 0x1bf7c037, nCurrent = 0x10000, nDirection = 1
16:13:31 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
16:13:31 Dialog 0x10000 returned: 1
16:13:31 End Action ShowDialogsHlpr
16:13:31 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17
16:13:31 Begin Action ShowDialogsHlpr: 0x20000
16:13:31 Begin Action : Cluster Security - DlgAcct
16:13:39 ShowDlgAcct returned: 1
16:13:39 [DlgAccount]
16:13:39 Domain = <Removed>
16:13:40 DomainAcct = <Removed>
16:13:40 DomainPwd
16:13:40 Result = 1
16:13:40 End Action : Cluster Security - DlgAcct
16:13:40 begin ShowDialogsUpdateMask
16:13:40 nFullMask = 0x1bf7c037, nCurrent = 0x20000, nDirection = 1
16:13:40 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
16:13:40 Dialog 0x20000 returned: 1
16:13:40 End Action ShowDialogsHlpr
16:13:40 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
16:13:40 Begin Action ShowDialogsHlpr: 0x40000
16:13:40 Begin Action: DialogShowSdCliSvr
16:13:40 DisplaySystemPreReq
16:13:40 ShowDlgClientServerSelect returned: 1
16:13:40 Type : 0x2
16:13:40 End Action DialogShowSdCliSvr
16:13:40 begin ShowDialogsUpdateMask
16:13:40 nFullMask = 0x1bf7c037, nCurrent = 0x40000, nDirection = 1
16:13:40 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
16:13:40 Dialog 0x40000 returned: 1
16:13:40 End Action ShowDialogsHlpr
16:13:40 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
16:13:40 Begin Action ShowDialogsHlpr: 0x80000
16:13:40 Begin Action: DialogShowSdInstanceName
16:13:40 Begin Action: ShowDlgInstanceName
16:13:46 End Action: ShowDlgInstanceName
16:13:46 ShowDlgInstanceName returned : 1
16:13:46 InstanceName : INSTANCEC7
16:13:46 End Action DialogShowSdInstanceName
16:13:46 begin ShowDialogsUpdateMask
16:13:46 nFullMask = 0x1bffc037, nCurrent = 0x80000, nDirection = 1
16:13:46 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
16:13:46 Dialog 0x80000 returned: 1
16:13:46 End Action ShowDialogsHlpr
16:13:46 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
16:13:46 Begin Action ShowDialogsHlpr: 0x100000
16:13:46 Begin Action: DialogShowSdSetupType
16:13:46 Begin Action: Setup Type
16:13:50 [SetupTypeSQL]
16:13:50 szDir = C:\Program Files\Microsoft SQL Server
16:13:50 szDir = C:\Program Files\Microsoft SQL Server
16:13:50 Result = 303
16:13:50 szDataDir = R:\Program Files\Microsoft SQL Server
16:13:50 szDataDir = R:\Program Files\Microsoft SQL Server
16:13:50 End Action: Setup Type
16:13:50 Setup Type: Custom (303)
16:13:50 End Action DialogShowSdSetupType
16:13:50 begin ShowDialogsUpdateMask
16:13:50 nFullMask = 0x1bffc037, nCurrent = 0x100000, nDirection = 303
16:13:50 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
16:13:50 Dialog 0x100000 returned: 303
16:13:50 End Action ShowDialogsHlpr
16:13:50 ShowDialogsGetDialog returned: nCurrent=0x200000,index=21
16:13:50 Begin Action ShowDialogsHlpr: 0x200000
16:13:50 Begin Action: DialogShowSdComponentMult
16:13:50 basesys = 0, baseinst = 0, basedata = 0
16:13:50 Begin Action: Component Handler
16:13:54 SQL program folder: C:\Program Files\Microsoft SQL
Server\MSSQL$INSTANCEC7
16:13:54 SQL data folder: R:\Program Files\Microsoft SQL
Server\MSSQL$INSTANCEC7
16:13:54 Windows system folder: C:\WINDOWS\system32\
16:13:54 Prog req: 22162, Data req: 34432, Sys req: 181286
16:13:54 Prog avail: 28555808, Data avail: 61083436, Sys avail: 28555808
16:13:54 Prog req vs. avail, 203448, 28555808
16:13:54 Data req vs. avail, 34432, 61083436
16:13:54 Sys req vs. avail, 181286, 28555808
16:13:54 DisplaySystemPreReq
16:13:54 [SQLComponentMult]
16:13:56 Component =
16:13:56 Result = 1
16:13:56 End Action: Component Handler
16:13:56 End Action DialogShowSdComponentMult
16:13:56 begin ShowDialogsUpdateMask
16:13:56 nFullMask = 0x1bffc037, nCurrent = 0x200000, nDirection = 1
16:13:56 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
16:13:56 Dialog 0x200000 returned: 1
16:13:56 End Action ShowDialogsHlpr
16:13:56 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
16:13:56 Begin Action ShowDialogsHlpr: 0x400000
16:13:56 Begin Action: DlgServices
16:14:15 ShowDlgServices returned: 1
16:14:15 [DlgServices]
16:14:15 Local-Domain= 61680
16:14:15 AutoStart= 0
16:14:15 SQLDomain= <Removed>
16:14:15 SQLDomainAcct= <Removed>
16:14:15 SQLDomainPwd
16:14:15 AgtDomain= <Removed>
16:14:15 AgtDomainAcct= <Removed>
16:14:15 AgtDomainPwd
16:14:15 Result= 1
16:14:15 End Action DlgServices
16:14:15 begin ShowDialogsUpdateMask
16:14:15 nFullMask = 0x1bffc037, nCurrent = 0x400000, nDirection = 1
16:14:15 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
16:14:15 Dialog 0x400000 returned: 1
16:14:15 End Action ShowDialogsHlpr
16:14:15 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
16:14:15 Begin Action ShowDialogsHlpr: 0x800000
16:14:15 Begin Action: DlgSQLSecurity
16:14:19 ShowDlgSQLSecurity returned: 1
16:14:19 LoginMode = 1,szPwd
16:14:19 End Action DlgSQLSecurity
16:14:19 begin ShowDialogsUpdateMask
16:14:19 nFullMask = 0x1bffc037, nCurrent = 0x800000, nDirection = 1
16:14:19 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
16:14:19 Dialog 0x800000 returned: 1
16:14:19 End Action ShowDialogsHlpr
16:14:19 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
16:14:19 Begin Action ShowDialogsHlpr: 0x1000000
16:14:19 Begin Action: DlgCollation
16:14:24 ShowDlgCollation returned: 1
16:14:24 collation_name = SQL_Latin1_General_CP1_CI_AS,locale_name = ,lcid =
0x409,SortId = 52,dwCompFlags = 0x30001
16:14:24 End Action DlgCollation
16:14:24 begin ShowDialogsUpdateMask
16:14:24 nFullMask = 0x1bffc037, nCurrent = 0x1000000, nDirection = 1
16:14:24 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
16:14:24 Dialog 0x1000000 returned: 1
16:14:24 End Action ShowDialogsHlpr
16:14:24 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
16:14:24 Begin Action ShowDialogsHlpr: 0x2000000
16:14:24 Begin Action: DlgNetwork
16:14:29 ShowDlgNetwork returned: 1
16:14:29 [DlgServerNetwork]
16:14:29 NetworkLibs = 255
16:14:29 TCPPort = 0
16:14:29 TCPPrxy = Default
16:14:29 NMPPipeName = \\.\pipe\MSSQL$INSTANCEC7\sql\query
16:14:29 Result = 1
16:14:29 End Action DlgNetwork
16:14:29 begin ShowDialogsUpdateMask
16:14:29 nFullMask = 0x1bffc037, nCurrent = 0x2000000, nDirection = 1
16:14:29 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
16:14:29 Dialog 0x2000000 returned: 1
16:14:29 End Action ShowDialogsHlpr
16:14:29 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
16:14:29 Begin Action ShowDialogsHlpr: 0x8000000
16:14:29 Begin Action: DialogShowSdStartCopy
16:14:30 End Action DialogShowSdStartCopy
16:14:30 begin ShowDialogsUpdateMask
16:14:30 nFullMask = 0x1bffc037, nCurrent = 0x8000000, nDirection = 1
16:14:30 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
16:14:30 Dialog 0x8000000 returned: 1
16:14:30 End Action ShowDialogsHlpr
16:14:30 ShowDialogsGetDialog returned: nCurrent=0x10000000,index=28
16:14:30 Begin Action ShowDialogsHlpr: 0x10000000
16:14:30 Begin Action: DialogShowSdLicenseMode
16:14:34 ShowDlgLicense returned: 1
16:14:34 ShowDlgLicense returned: LicenseMode = 0, LicenseLimit = 999
16:14:34 End Action DialogShowSdLicenseMode
16:14:34 Dialog 0x10000000 returned: 1
16:14:34 End Action ShowDialogsHlpr
16:14:34 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
16:14:34 End Action ShowDialogs
16:14:34 Setup is installing Microsoft Distributed Transaction Coordinator
(MSDTC) ...
16:14:34 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir
"C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg
"\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\Other\dtcsetup.exe" -LogFile
"C:\WINDOWS\sqlstp.log" -CtxAcct "<Removed>" -<Removed>
16:14:34 Process Exit Code: (0)
16:14:34 Begin Action : ClusterSetupHelper
16:14:34 Begin Action : CreateClustISSFiles
16:14:34 End Action : CreateClustISSFiles
16:14:34 Begin Action : ClusterWriteRemIni
16:14:34 End Action : ClusterWriteRemIni
16:14:34 Begin Action : Run setup on cluster nodes
[args]
NumRemoteServers=3
Server.1=NPBSQL6
Server.2=NPBSQL7
Server.3=NPBSQL8
[Server.1]
NumRemoteServices=1
1.app=\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
1.server=NPBSQL6
1.script=\\NPBSQL6\admin$\NPBSQL6_INSTANCEC7.iss
1.cmdlineformat=%s k=Nb k=Rm k=Cl -SMS -s -f
"\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1 %s -f2
"\\NPBSQL6\admin$\setup.log" -e "stpsilnt._ex" -b -x "C:\WINDOWS\TEMP\"
1.user=<Removed>
1.password=<Removed>
1.name=<Removed>
1.sqlsetup=Y
1.copyexe=cnvsvc1.exe
[Server.2]
NumRemoteServices=1
1.app=\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
1.server=NPBSQL7
1.script=\\NPBSQL6\admin$\NPBSQL7_INSTANCEC7.iss
1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f
"\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1 %s -f2
"\\NPBSQL7\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"
1.user=<Removed>
1.password=095b2c9b3941a75cd961
1.name=SQLSetup2
1.sqlsetup=Y
1.copyexe=cnvsvc2.exe
[Server.3]
NumRemoteServices=1
1.app=\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
1.server=NPBSQL8
1.script=\\NPBSQL6\admin$\NPBSQL8_INSTANCEC7.iss
1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f
"\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1 %s -f2
"\\NPBSQL8\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"
1.user=<Removed>
1.password=095b2c9b3941a75cd961
1.name=SQLSetup3
1.sqlsetup=Y
1.copyexe=cnvsvc3.exe
16:14:34 Setup is performing required operations on cluster nodes. This may
take a few minutes...
16:14:34 C:\WINDOWS\TEMP\SqlSetup\Bin\remsetup.exe C:\WINDOWS\remsetup.ini
16:16:41 Process Exit Code: (0)
16:16:41 Begin Action : GetRemsetupRetCode
16:16:41 Installation return status on NPBSQL6 : 0
16:16:41 Installation return status on NPBSQL7 : 0
16:16:41 Installation return status on NPBSQL8 : 0
16:16:41 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 05/18/05 16:14:34 ####
CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x78] created for execution.
CThread::Process [0x78]
CThreadPool::RunUntilCompleteHlpr create thread, index=1
Running '\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe k=Nb
k=Rm k=Cl -SMS -s -f
"\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1
\\NPBSQL6\admin$\NPBSQL6_INSTANCEC7.iss -f2 "\\NPBSQL6\admin$\setup.log" -e
"stpsilnt._ex" -b -x "C:\WINDOWS\TEMP\"' (NPBSQL6) ...
CThread::Run thread [0x80] created for execution.
CThread::Process [0x80]
CThreadPool::RunUntilCompleteHlpr create thread, index=2
CThread::Run thread [0x84] created for execution.
CThread::Process [0x84]
CThreadPool::RunUntilCompleteHlpr start thread [0x78],index=0
CThreadPool::RunUntilCompleteHlpr start thread [0x80],index=1
CThreadPool::RunUntilCompleteHlpr start thread [0x84],index=2
Script file copied to '\\NPBSQL8\ADMIN$\NPBSQL8_INSTANCEC7.iss' successfully.
Script file copied to '\\NPBSQL7\ADMIN$\NPBSQL7_INSTANCEC7.iss' successfully.
Installing remote service (NPBSQL8)...
Installing remote service (NPBSQL7)...
Running '\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
k=ClSec k=Rm k=Cl -SMS -s -f
"\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1
\\NPBSQL8\ADMIN$\NPBSQL8_INSTANCEC7.iss -f2 "\\NPBSQL8\admin$\setup.log" -e
"stpsilnt._ex" -x "C:\"' (NPBSQL8) ...
Running '\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
k=ClSec k=Rm k=Cl -SMS -s -f
"\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1
\\NPBSQL7\ADMIN$\NPBSQL7_INSTANCEC7.iss -f2 "\\NPBSQL7\admin$\setup.log" -e
"stpsilnt._ex" -x "C:\"' (NPBSQL7) ...
CRemoteProcess::RunUntilComplete [0x84] exit code: 0
Remote process exit code was '0' (NPBSQL8).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x84]
Thread [0x84] exit code: [0x0]
CRemoteProcess::RunUntilComplete [0x80] exit code: 0
Remote process exit code was '0' (NPBSQL7).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x80]
Thread [0x80] exit code: [0x0]
CProcess::RunUntilComplete [0x78] exit code: 0
Remote process exit code was '0' (NPBSQL6).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x78]
Thread [0x78] exit code: [0x0]
CThreadPool::RunUntilComplete returned 0
CThreadPool::RunUntilComplete execution level=1, need execution: 0
Disconnecting from remote machine (NPBSQL6)...
Service removed successfully.
Remote files could not be removed.
#### SQL Server Remote Setup - Stop Time 05/18/05 16:16:07 ####
Disconnecting from remote machine (NPBSQL7)...
Service removed successfully.
Remote files removed successfully.
#### SQL Server Remote Setup - Stop Time 05/18/05 16:16:24 ####
Disconnecting from remote machine (NPBSQL8)...
Service removed successfully.
Remote files removed successfully.
#### SQL Server Remote Setup - Stop Time 05/18/05 16:16:41 ####
16:16:41 End Action : Run setup on cluster nodes
16:16:41 SetClusterSecuritySQL (<Removed>) and (<Removed>) returned: 0
16:16:41 Begin Action : CreateVirtualServerResources
16:16:49 End Action : CreateVirtualServerResources
16:16:49 CreateVirtualServerResources returned: 2
SQL Clusters sometimes don't like installing from a network share. Burn a
CD and physically place it in the node you are running install on.
Geoff N. Hiten
Microsoft SQL Server MVP
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:22BF14DE-8ECE-48FD-BCF9-6D811C6F8277@.microsoft.com...
> Building an Active/Active/Passive SQL 2000 cluster on top of a 3 node 2003
> server cluster. As I go to install I end up getting a "An error occured
> while creating virtual server resources for clustering. The system cannot
> find the file specified."
> I've gone through KB 815431 and made sure the named piped alias is
> configured properly and it appears to be working correctly. Let me know
> if
> anyone has any ideas. Here's my sqlstp.log up to the point of the error.
> 16:12:58 Begin Setup
> 16:12:58 8.00.194
> 16:12:58 Mode = Normal
> 16:12:58 ModeType = NORMAL
> 16:12:58 GetDefinitionEx returned: 0, Extended: 0x0
> 16:12:58 ValueFTS returned: 1
> 16:12:58 ValuePID returned: 1
> 16:12:58 ValueLic returned: 1
> 16:12:58 System: Windows NT Enterprise Server
> 16:12:58 SQL Server ProductType: Enterprise Edition [0x3]
> 16:12:58 IsNTCluster returned: 1
> 16:12:58 Begin Action: SetupInitialize
> 16:12:58 End Action SetupInitialize
> 16:12:58 Begin Action: SetupInstall
> 16:12:58 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir
> ...
> 16:12:58 CommonFilesDir=C:\Program Files\Common Files
> 16:12:58 Windows Directory=C:\WINDOWS\
> 16:12:58 Program Files=C:\Program Files\
> 16:12:58 TEMPDIR=C:\WINDOWS\TEMP\
> 16:12:58 Begin Action: SetupInstall
> 16:12:58 digpid size : 256
> 16:12:58 digpid size : 164
> 16:12:58 Begin Action: CheckFixedRequirements
> 16:12:58 Platform ID: 0xf00000
> 16:12:58 Version: 5.2.3790
> 16:12:58 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.279
> 16:12:58 End Action: CheckFixedRequirements
> 16:12:58 Begin Action: ShowDialogs
> 16:12:58 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
> 16:12:58 Begin Action ShowDialogsHlpr: 0x1
> 16:12:58 Begin Action: DialogShowSdWelcome
> 16:13:01 End Action DialogShowSdWelcome
> 16:13:01 Dialog 0x1 returned: 1
> 16:13:01 End Action ShowDialogsHlpr
> 16:13:01 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 16:13:01 Begin Action ShowDialogsHlpr: 0x2
> 16:13:01 Begin Action: DialogShowSdMachineName
> 16:13:15 ShowDlgMachine returned: 1
> 16:13:15 Name = NPBSQLC7, Type = 0x10000008
> 16:13:15 Begin Action: CheckRequirements
> 16:13:15 Processor Architecture: x86 (Pentium)
> 16:13:15 ComputerName: NPBSQL6
> 16:13:15 User Name: <Removed>
> 16:13:15 IsAllAccessAllowed returned: 1
> 16:13:15 OS Language: 0x409
> 16:13:15 End Action CheckRequirements
> 16:13:15 This combination of Package and Operating System allows a full
> product install.
> 16:13:15 End Action DialogShowSdMachineName
> 16:13:15 begin ShowDialogsUpdateMask
> 16:13:15 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0
> 16:13:15 Updated Dialog Mask: 0xbf3c037, Disable Back = 0x1
> 16:13:15 Dialog 0x2 returned: 0
> 16:13:15 End Action ShowDialogsHlpr
> 16:13:15 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
> 16:13:15 Begin Action ShowDialogsHlpr: 0x4
> 16:13:15 Begin Action: DialogShowSdInstallMode
> 16:13:15 InstallMode : 0x1
> 16:13:15 End Action DialogShowSdInstallMode
> 16:13:15 begin ShowDialogsUpdateMask
> 16:13:15 nFullMask = 0xbf3c037, nCurrent = 0x4, nDirection = 1
> 16:13:15 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
> 16:13:15 Dialog 0x4 returned: 1
> 16:13:15 End Action ShowDialogsHlpr
> 16:13:15 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
> 16:13:15 Begin Action ShowDialogsHlpr: 0x10
> 16:13:15 Begin Action: DialogShowSdRegisterUserEx
> 16:13:17 End Action DialogShowSdRegisterUserEx
> 16:13:17 begin ShowDialogsUpdateMask
> 16:13:17 nFullMask = 0x1bf7c037, nCurrent = 0x10, nDirection = 1
> 16:13:17 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
> 16:13:17 Dialog 0x10 returned: 1
> 16:13:17 End Action ShowDialogsHlpr
> 16:13:17 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
> 16:13:17 Begin Action ShowDialogsHlpr: 0x20
> 16:13:17 Begin Action: DialogShowSdLicense
> 16:13:17 End Action DialogShowSdLicense
> 16:13:17 Dialog 0x20 returned: 1
> 16:13:17 End Action ShowDialogsHlpr
> 16:13:17 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14
> 16:13:17 Begin Action ShowDialogsHlpr: 0x4000
> 16:13:17 Begin Action: DialogShowSdVirtualServer
> 16:13:27 ShowDlgVirtualServer returned: 0
> 16:13:27 Ipaddress = 10.10.0.58,255.255.252.0,SQL2 Public Team
> 16:13:27 szNewList = 10.10.0.58,255.255.252.0,SQL2 Public Team
> 16:13:27 szModifiedList =
> 16:13:27 szRemovedList =
> 16:13:27 End Action DialogShowSdVirtualServer
> 16:13:27 begin ShowDialogsUpdateMask
> 16:13:27 nFullMask = 0x1bf7c037, nCurrent = 0x4000, nDirection = 1
> 16:13:27 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
> 16:13:27 Dialog 0x4000 returned: 1
> 16:13:27 End Action ShowDialogsHlpr
> 16:13:27 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15
> 16:13:27 Begin Action ShowDialogsHlpr: 0x8000
> 16:13:27 Begin Action : DialogShowSdDiskGroups
> 16:13:30 ShowDlgDiskGroups returned: 1
> 16:13:30 Disk Group = NPBSQLC7
> 16:13:30 End Action : DialogShowSdDiskGroups
> 16:13:30 begin ShowDialogsUpdateMask
> 16:13:30 nFullMask = 0x1bf7c037, nCurrent = 0x8000, nDirection = 1
> 16:13:30 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
> 16:13:30 Dialog 0x8000 returned: 1
> 16:13:30 End Action ShowDialogsHlpr
> 16:13:30 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16
> 16:13:30 Begin Action ShowDialogsHlpr: 0x10000
> 16:13:30 Begin Action: DialogShowSdClusterDef
> 16:13:31 ShowDlgClusterDef returned: 1
> 16:13:31 PrefOwners = NPBSQL6,NPBSQL7,NPBSQL8, NumIp = 3
> 16:13:31 Begin Action : ValidateNodeActions
> 16:13:31 Begin Action : ValidateNodeActions
> 16:13:31 End Action : ValidateNodeActions
> 16:13:31 End Action : ValidateNodeActions
> 16:13:31 End Action DialogShowSdClusterDef
> 16:13:31 begin ShowDialogsUpdateMask
> 16:13:31 nFullMask = 0x1bf7c037, nCurrent = 0x10000, nDirection = 1
> 16:13:31 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
> 16:13:31 Dialog 0x10000 returned: 1
> 16:13:31 End Action ShowDialogsHlpr
> 16:13:31 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17
> 16:13:31 Begin Action ShowDialogsHlpr: 0x20000
> 16:13:31 Begin Action : Cluster Security - DlgAcct
> 16:13:39 ShowDlgAcct returned: 1
> 16:13:39 [DlgAccount]
> 16:13:39 Domain = <Removed>
> 16:13:40 DomainAcct = <Removed>
> 16:13:40 DomainPwd
> 16:13:40 Result = 1
> 16:13:40 End Action : Cluster Security - DlgAcct
> 16:13:40 begin ShowDialogsUpdateMask
> 16:13:40 nFullMask = 0x1bf7c037, nCurrent = 0x20000, nDirection = 1
> 16:13:40 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
> 16:13:40 Dialog 0x20000 returned: 1
> 16:13:40 End Action ShowDialogsHlpr
> 16:13:40 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
> 16:13:40 Begin Action ShowDialogsHlpr: 0x40000
> 16:13:40 Begin Action: DialogShowSdCliSvr
> 16:13:40 DisplaySystemPreReq
> 16:13:40 ShowDlgClientServerSelect returned: 1
> 16:13:40 Type : 0x2
> 16:13:40 End Action DialogShowSdCliSvr
> 16:13:40 begin ShowDialogsUpdateMask
> 16:13:40 nFullMask = 0x1bf7c037, nCurrent = 0x40000, nDirection = 1
> 16:13:40 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
> 16:13:40 Dialog 0x40000 returned: 1
> 16:13:40 End Action ShowDialogsHlpr
> 16:13:40 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
> 16:13:40 Begin Action ShowDialogsHlpr: 0x80000
> 16:13:40 Begin Action: DialogShowSdInstanceName
> 16:13:40 Begin Action: ShowDlgInstanceName
> 16:13:46 End Action: ShowDlgInstanceName
> 16:13:46 ShowDlgInstanceName returned : 1
> 16:13:46 InstanceName : INSTANCEC7
> 16:13:46 End Action DialogShowSdInstanceName
> 16:13:46 begin ShowDialogsUpdateMask
> 16:13:46 nFullMask = 0x1bffc037, nCurrent = 0x80000, nDirection = 1
> 16:13:46 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
> 16:13:46 Dialog 0x80000 returned: 1
> 16:13:46 End Action ShowDialogsHlpr
> 16:13:46 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
> 16:13:46 Begin Action ShowDialogsHlpr: 0x100000
> 16:13:46 Begin Action: DialogShowSdSetupType
> 16:13:46 Begin Action: Setup Type
> 16:13:50 [SetupTypeSQL]
> 16:13:50 szDir = C:\Program Files\Microsoft SQL Server
> 16:13:50 szDir = C:\Program Files\Microsoft SQL Server
> 16:13:50 Result = 303
> 16:13:50 szDataDir = R:\Program Files\Microsoft SQL Server
> 16:13:50 szDataDir = R:\Program Files\Microsoft SQL Server
> 16:13:50 End Action: Setup Type
> 16:13:50 Setup Type: Custom (303)
> 16:13:50 End Action DialogShowSdSetupType
> 16:13:50 begin ShowDialogsUpdateMask
> 16:13:50 nFullMask = 0x1bffc037, nCurrent = 0x100000, nDirection = 303
> 16:13:50 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
> 16:13:50 Dialog 0x100000 returned: 303
> 16:13:50 End Action ShowDialogsHlpr
> 16:13:50 ShowDialogsGetDialog returned: nCurrent=0x200000,index=21
> 16:13:50 Begin Action ShowDialogsHlpr: 0x200000
> 16:13:50 Begin Action: DialogShowSdComponentMult
> 16:13:50 basesys = 0, baseinst = 0, basedata = 0
> 16:13:50 Begin Action: Component Handler
> 16:13:54 SQL program folder: C:\Program Files\Microsoft SQL
> Server\MSSQL$INSTANCEC7
> 16:13:54 SQL data folder: R:\Program Files\Microsoft SQL
> Server\MSSQL$INSTANCEC7
> 16:13:54 Windows system folder: C:\WINDOWS\system32\
> 16:13:54 Prog req: 22162, Data req: 34432, Sys req: 181286
> 16:13:54 Prog avail: 28555808, Data avail: 61083436, Sys avail: 28555808
> 16:13:54 Prog req vs. avail, 203448, 28555808
> 16:13:54 Data req vs. avail, 34432, 61083436
> 16:13:54 Sys req vs. avail, 181286, 28555808
> 16:13:54 DisplaySystemPreReq
> 16:13:54 [SQLComponentMult]
> 16:13:56 Component =
> 16:13:56 Result = 1
> 16:13:56 End Action: Component Handler
> 16:13:56 End Action DialogShowSdComponentMult
> 16:13:56 begin ShowDialogsUpdateMask
> 16:13:56 nFullMask = 0x1bffc037, nCurrent = 0x200000, nDirection = 1
> 16:13:56 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
> 16:13:56 Dialog 0x200000 returned: 1
> 16:13:56 End Action ShowDialogsHlpr
> 16:13:56 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
> 16:13:56 Begin Action ShowDialogsHlpr: 0x400000
> 16:13:56 Begin Action: DlgServices
> 16:14:15 ShowDlgServices returned: 1
> 16:14:15 [DlgServices]
> 16:14:15 Local-Domain = 61680
> 16:14:15 AutoStart = 0
> 16:14:15 SQLDomain = <Removed>
> 16:14:15 SQLDomainAcct = <Removed>
> 16:14:15 SQLDomainPwd
> 16:14:15 AgtDomain = <Removed>
> 16:14:15 AgtDomainAcct = <Removed>
> 16:14:15 AgtDomainPwd
> 16:14:15 Result = 1
> 16:14:15 End Action DlgServices
> 16:14:15 begin ShowDialogsUpdateMask
> 16:14:15 nFullMask = 0x1bffc037, nCurrent = 0x400000, nDirection = 1
> 16:14:15 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
> 16:14:15 Dialog 0x400000 returned: 1
> 16:14:15 End Action ShowDialogsHlpr
> 16:14:15 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
> 16:14:15 Begin Action ShowDialogsHlpr: 0x800000
> 16:14:15 Begin Action: DlgSQLSecurity
> 16:14:19 ShowDlgSQLSecurity returned: 1
> 16:14:19 LoginMode = 1,szPwd
> 16:14:19 End Action DlgSQLSecurity
> 16:14:19 begin ShowDialogsUpdateMask
> 16:14:19 nFullMask = 0x1bffc037, nCurrent = 0x800000, nDirection = 1
> 16:14:19 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
> 16:14:19 Dialog 0x800000 returned: 1
> 16:14:19 End Action ShowDialogsHlpr
> 16:14:19 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
> 16:14:19 Begin Action ShowDialogsHlpr: 0x1000000
> 16:14:19 Begin Action: DlgCollation
> 16:14:24 ShowDlgCollation returned: 1
> 16:14:24 collation_name = SQL_Latin1_General_CP1_CI_AS,locale_name = ,lcid
> =
> 0x409,SortId = 52,dwCompFlags = 0x30001
> 16:14:24 End Action DlgCollation
> 16:14:24 begin ShowDialogsUpdateMask
> 16:14:24 nFullMask = 0x1bffc037, nCurrent = 0x1000000, nDirection = 1
> 16:14:24 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
> 16:14:24 Dialog 0x1000000 returned: 1
> 16:14:24 End Action ShowDialogsHlpr
> 16:14:24 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
> 16:14:24 Begin Action ShowDialogsHlpr: 0x2000000
> 16:14:24 Begin Action: DlgNetwork
> 16:14:29 ShowDlgNetwork returned: 1
> 16:14:29 [DlgServerNetwork]
> 16:14:29 NetworkLibs = 255
> 16:14:29 TCPPort = 0
> 16:14:29 TCPPrxy = Default
> 16:14:29 NMPPipeName = \\.\pipe\MSSQL$INSTANCEC7\sql\query
> 16:14:29 Result = 1
> 16:14:29 End Action DlgNetwork
> 16:14:29 begin ShowDialogsUpdateMask
> 16:14:29 nFullMask = 0x1bffc037, nCurrent = 0x2000000, nDirection = 1
> 16:14:29 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
> 16:14:29 Dialog 0x2000000 returned: 1
> 16:14:29 End Action ShowDialogsHlpr
> 16:14:29 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
> 16:14:29 Begin Action ShowDialogsHlpr: 0x8000000
> 16:14:29 Begin Action: DialogShowSdStartCopy
> 16:14:30 End Action DialogShowSdStartCopy
> 16:14:30 begin ShowDialogsUpdateMask
> 16:14:30 nFullMask = 0x1bffc037, nCurrent = 0x8000000, nDirection = 1
> 16:14:30 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
> 16:14:30 Dialog 0x8000000 returned: 1
> 16:14:30 End Action ShowDialogsHlpr
> 16:14:30 ShowDialogsGetDialog returned: nCurrent=0x10000000,index=28
> 16:14:30 Begin Action ShowDialogsHlpr: 0x10000000
> 16:14:30 Begin Action: DialogShowSdLicenseMode
> 16:14:34 ShowDlgLicense returned: 1
> 16:14:34 ShowDlgLicense returned: LicenseMode = 0, LicenseLimit = 999
> 16:14:34 End Action DialogShowSdLicenseMode
> 16:14:34 Dialog 0x10000000 returned: 1
> 16:14:34 End Action ShowDialogsHlpr
> 16:14:34 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
> 16:14:34 End Action ShowDialogs
> 16:14:34 Setup is installing Microsoft Distributed Transaction Coordinator
> (MSDTC) ...
> 16:14:34 C:\WINDOWS\TEMP\SqlSetup\Bin\cldtcstp.exe -SupportDir
> "C:\WINDOWS\TEMP\SqlSetup\Bin" -DTCPkg
> "\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\Other\dtcsetup.exe" -LogFile
> "C:\WINDOWS\sqlstp.log" -CtxAcct "<Removed>" -<Removed>
> 16:14:34 Process Exit Code: (0)
> 16:14:34 Begin Action : ClusterSetupHelper
> 16:14:34 Begin Action : CreateClustISSFiles
> 16:14:34 End Action : CreateClustISSFiles
> 16:14:34 Begin Action : ClusterWriteRemIni
> 16:14:34 End Action : ClusterWriteRemIni
> 16:14:34 Begin Action : Run setup on cluster nodes
> [args]
> NumRemoteServers=3
> Server.1=NPBSQL6
> Server.2=NPBSQL7
> Server.3=NPBSQL8
> [Server.1]
> NumRemoteServices=1
> 1.app=\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
> 1.server=NPBSQL6
> 1.script=\\NPBSQL6\admin$\NPBSQL6_INSTANCEC7.iss
> 1.cmdlineformat=%s k=Nb k=Rm k=Cl -SMS -s -f
> "\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1 %s -f2
> "\\NPBSQL6\admin$\setup.log" -e "stpsilnt._ex" -b -x "C:\WINDOWS\TEMP\"
> 1.user=<Removed>
> 1.password=<Removed>
> 1.name=<Removed>
> 1.sqlsetup=Y
> 1.copyexe=cnvsvc1.exe
> [Server.2]
> NumRemoteServices=1
> 1.app=\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
> 1.server=NPBSQL7
> 1.script=\\NPBSQL6\admin$\NPBSQL7_INSTANCEC7.iss
> 1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f
> "\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1 %s -f2
> "\\NPBSQL7\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"
> 1.user=<Removed>
> 1.password=095b2c9b3941a75cd961
> 1.name=SQLSetup2
> 1.sqlsetup=Y
> 1.copyexe=cnvsvc2.exe
> [Server.3]
> NumRemoteServices=1
> 1.app=\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
> 1.server=NPBSQL8
> 1.script=\\NPBSQL6\admin$\NPBSQL8_INSTANCEC7.iss
> 1.cmdlineformat=%s k=ClSec k=Rm k=Cl -SMS -s -f
> "\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1 %s -f2
> "\\NPBSQL8\admin$\setup.log" -e "stpsilnt._ex" -x "C:\"
> 1.user=<Removed>
> 1.password=095b2c9b3941a75cd961
> 1.name=SQLSetup3
> 1.sqlsetup=Y
> 1.copyexe=cnvsvc3.exe
> 16:14:34 Setup is performing required operations on cluster nodes. This
> may
> take a few minutes...
> 16:14:34 C:\WINDOWS\TEMP\SqlSetup\Bin\remsetup.exe
> C:\WINDOWS\remsetup.ini
> 16:16:41 Process Exit Code: (0)
> 16:16:41 Begin Action : GetRemsetupRetCode
> 16:16:41 Installation return status on NPBSQL6 : 0
> 16:16:41 Installation return status on NPBSQL7 : 0
> 16:16:41 Installation return status on NPBSQL8 : 0
> 16:16:41 End Action : GetRemsetupRetCode
> #### SQL Server Remote Setup - Start Time 05/18/05 16:14:34 ####
> CThreadPool::RunUntilCompleteHlpr create thread, index=0
> CThread::Run thread [0x78] created for execution.
> CThread::Process [0x78]
> CThreadPool::RunUntilCompleteHlpr create thread, index=1
> Running '\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe k=Nb
> k=Rm k=Cl -SMS -s -f
> "\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1
> \\NPBSQL6\admin$\NPBSQL6_INSTANCEC7.iss -f2
> "\\NPBSQL6\admin$\setup.log" -e
> "stpsilnt._ex" -b -x "C:\WINDOWS\TEMP\"' (NPBSQL6) ...
> CThread::Run thread [0x80] created for execution.
> CThread::Process [0x80]
> CThreadPool::RunUntilCompleteHlpr create thread, index=2
> CThread::Run thread [0x84] created for execution.
> CThread::Process [0x84]
> CThreadPool::RunUntilCompleteHlpr start thread [0x78],index=0
> CThreadPool::RunUntilCompleteHlpr start thread [0x80],index=1
> CThreadPool::RunUntilCompleteHlpr start thread [0x84],index=2
> Script file copied to '\\NPBSQL8\ADMIN$\NPBSQL8_INSTANCEC7.iss'
> successfully.
> Script file copied to '\\NPBSQL7\ADMIN$\NPBSQL7_INSTANCEC7.iss'
> successfully.
> Installing remote service (NPBSQL8)...
> Installing remote service (NPBSQL7)...
> Running '\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
> k=ClSec k=Rm k=Cl -SMS -s -f
> "\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1
> \\NPBSQL8\ADMIN$\NPBSQL8_INSTANCEC7.iss -f2
> "\\NPBSQL8\admin$\setup.log" -e
> "stpsilnt._ex" -x "C:\"' (NPBSQL8) ...
> Running '\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setupsql.exe
> k=ClSec k=Rm k=Cl -SMS -s -f
> "\\NPB2KNAS1\APPS\APPS-IT\SQL\SQL2K_~1\x86\setup\setup.ins" -f1
> \\NPBSQL7\ADMIN$\NPBSQL7_INSTANCEC7.iss -f2
> "\\NPBSQL7\admin$\setup.log" -e
> "stpsilnt._ex" -x "C:\"' (NPBSQL7) ...
> CRemoteProcess::RunUntilComplete [0x84] exit code: 0
> Remote process exit code was '0' (NPBSQL8).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x84]
> Thread [0x84] exit code: [0x0]
> CRemoteProcess::RunUntilComplete [0x80] exit code: 0
> Remote process exit code was '0' (NPBSQL7).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x80]
> Thread [0x80] exit code: [0x0]
> CProcess::RunUntilComplete [0x78] exit code: 0
> Remote process exit code was '0' (NPBSQL6).
> CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
> CThreadPool::RunUntilCompleteHlpr signaled thread [0x78]
> Thread [0x78] exit code: [0x0]
> CThreadPool::RunUntilComplete returned 0
> CThreadPool::RunUntilComplete execution level=1, need execution: 0
> Disconnecting from remote machine (NPBSQL6)...
> Service removed successfully.
> Remote files could not be removed.
> #### SQL Server Remote Setup - Stop Time 05/18/05 16:16:07 ####
> Disconnecting from remote machine (NPBSQL7)...
> Service removed successfully.
> Remote files removed successfully.
> #### SQL Server Remote Setup - Stop Time 05/18/05 16:16:24 ####
> Disconnecting from remote machine (NPBSQL8)...
> Service removed successfully.
> Remote files removed successfully.
> #### SQL Server Remote Setup - Stop Time 05/18/05 16:16:41 ####
>
> 16:16:41 End Action : Run setup on cluster nodes
> 16:16:41 SetClusterSecuritySQL (<Removed>) and (<Removed>) returned: 0
> 16:16:41 Begin Action : CreateVirtualServerResources
> 16:16:49 End Action : CreateVirtualServerResources
> 16:16:49 CreateVirtualServerResources returned: 2
>
>
|||Thanks for the quick reply. I did try copying the install folder over
locally and ended up with the same error message.
"Geoff N. Hiten" wrote:

> SQL Clusters sometimes don't like installing from a network share. Burn a
> CD and physically place it in the node you are running install on.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:22BF14DE-8ECE-48FD-BCF9-6D811C6F8277@.microsoft.com...
>
>
|||Make sure both the SQL Service account and the install account are domain
accounts with administrators group membership on all nodes. Check the TMP
and TEMP system variable paths on all nodes. Log in to each server with
each account at least once before installing.
Geoff N. Hiten
Microsoft SQL Server MVP
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:D22ECFA7-0ECC-492E-98E9-60D3BBBF4A12@.microsoft.com...[vbcol=seagreen]
> Thanks for the quick reply. I did try copying the install folder over
> locally and ended up with the same error message.
> "Geoff N. Hiten" wrote:
|||Thansk again for the response!
I have logged onto each machine previous with the install account. As for
the accounts. The install account I'm using is the Domain Admin account, so
that should be alright. Also, the network accounts I'm using for both the
SQLService and the Cluster service are in the node's Local Admins group.
On all the nodes the TEMP and TMP variables for the Install account is
listed as %USERPROFILE%\Local Settings\Temp. For the system it's
%SystemRoot%\TEMP
I changed them all to %SystemRoot%\TEMP (Replaced %systemroot% with the
actual path name as well.)
Still got the error message right after it tries to create the cluster
resources.
Now previously I had an install of SQL installed on these nodes that were
SP'd up to 3a. Could that be causing any of the issues?
"Geoff N. Hiten" wrote:

> Make sure both the SQL Service account and the install account are domain
> accounts with administrators group membership on all nodes. Check the TMP
> and TEMP system variable paths on all nodes. Log in to each server with
> each account at least once before installing.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:D22ECFA7-0ECC-492E-98E9-60D3BBBF4A12@.microsoft.com...
>
>
|||Hmm, I'm wondering if it does have something to do with some SP3a files stuck
on that local machine. I attempted to install it to just a single node as
per http://support.microsoft.com/default...b;en-us;318672 and still
got the same error.
Not sure how I can dig out any files, at this point a full re-install may be
in order.
"Geoff N. Hiten" wrote:

> Make sure both the SQL Service account and the install account are domain
> accounts with administrators group membership on all nodes. Check the TMP
> and TEMP system variable paths on all nodes. Log in to each server with
> each account at least once before installing.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:D22ECFA7-0ECC-492E-98E9-60D3BBBF4A12@.microsoft.com...
>
>
|||An old install with incomplete removal might cause some issues.
This article will help remove any trace of the old SQL installation:
How to manually remove SQL Server 2000 default, named, or virtual instance
http://support.microsoft.com/default...b;en-us;290991
Geoff N. Hiten
Microsoft SQL Server MVP
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:E981A9F3-B54A-4D0A-AEEC-AA218EA2E717@.microsoft.com...[vbcol=seagreen]
> Thansk again for the response!
> I have logged onto each machine previous with the install account. As for
> the accounts. The install account I'm using is the Domain Admin account,
> so
> that should be alright. Also, the network accounts I'm using for both the
> SQLService and the Cluster service are in the node's Local Admins group.
> On all the nodes the TEMP and TMP variables for the Install account is
> listed as %USERPROFILE%\Local Settings\Temp. For the system it's
> %SystemRoot%\TEMP
> I changed them all to %SystemRoot%\TEMP (Replaced %systemroot% with the
> actual path name as well.)
> Still got the error message right after it tries to create the cluster
> resources.
> Now previously I had an install of SQL installed on these nodes that were
> SP'd up to 3a. Could that be causing any of the issues?
> "Geoff N. Hiten" wrote:
|||One other thing I once ran into:
Check C:\Documents and Settings
Maybe on one node you logged on locally before, and the other not. You might
have differences. e.g.:
Node A
Administrator
Administrator.domain
Node B
Administrator
The profile-directory for the account you are using has to be the same on
both nodes. It's kind of tricky ...
Chau chau,
Pascalos
"Chris" wrote:
[vbcol=seagreen]
> Hmm, I'm wondering if it does have something to do with some SP3a files stuck
> on that local machine. I attempted to install it to just a single node as
> per http://support.microsoft.com/default...b;en-us;318672 and still
> got the same error.
> Not sure how I can dig out any files, at this point a full re-install may be
> in order.
> "Geoff N. Hiten" wrote:

Error creating login - Incorrect syntax near 'LOGIN'.

Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
instance by the sounds of it. What's the version of the SQL instance
(run "SELECT SERVERPROPERTY('ProductVersion')")?
CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new logins
to a SQL 2000 instance, regardless of which SQL client tool you use, you
need to use sp_addlogin or sp_grantlogin (depending on whether it's a
standard SQL login or a trusted login we're talking about). I think the
GUI in Management Studio ought to take care of this automatically (ie.
use different commands depending on the server version) but if you want
to use T-SQL yourself then you need to write the correct statements for
the SQL version the server is running.
*mike hodgson*
http://sqlnerd.blogspot.com
eshhyasi@.gmail.com wrote:

>Hi,
>I am using Sql server 2005 and when I try to create a new login from
>the sql server mgmnt studio, I get this error.
>Msg 170, Level 15, State 1, Line 1
>Line 1: Incorrect syntax near 'LOGIN'.
>I have logged in as "sa" and the login statement that I am using is:
>CREATE LOGIN test WITH PASSWORD = 'beta'
>The product version is 8.00.2039.
>Anybody knows whats wrong'
>Thanks for helping out.
>Esha
>
>Even you are using Management Studio, you are connected to a SQL Server 2000
instance (according to your product version). You should connect to a SQL
Server 2005 instance to use create login.
Ben Nevarez, MCDBA, OCP
Database Administrator
"eshhyasi@.gmail.com" wrote:

> Hi,
> I am using Sql server 2005 and when I try to create a new login from
> the sql server mgmnt studio, I get this error.
> Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near 'LOGIN'.
> I have logged in as "sa" and the login statement that I am using is:
> CREATE LOGIN test WITH PASSWORD = 'beta'
> The product version is 8.00.2039.
> Anybody knows whats wrong'
> Thanks for helping out.
> Esha
>|||Thanks Mike,
I used sp_addlogin and it worked.
Thanks a lot,
Esha
Mike Hodgson wrote:
> Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
> instance by the sounds of it. What's the version of the SQL instance
> (run "SELECT SERVERPROPERTY('ProductVersion')")?
> CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new logins
> to a SQL 2000 instance, regardless of which SQL client tool you use, you
> need to use sp_addlogin or sp_grantlogin (depending on whether it's a
> standard SQL login or a trusted login we're talking about). I think the
> GUI in Management Studio ought to take care of this automatically (ie.
> use different commands depending on the server version) but if you want
> to use T-SQL yourself then you need to write the correct statements for
> the SQL version the server is running.
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> eshhyasi@.gmail.com wrote:
>
> --060001040307010407040902
> Content-Type: text/html; charset=ISO-8859-1
> X-Google-AttachSize: 2029
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>
> <head>
> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
> </head>
> <body bgcolor="#ffffff" text="#000000">
> <tt>Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
> instance by the sounds of it. What's the version of the SQL inst
ance
> (run "SELECT SERVERPROPERTY('ProductVersion')")?<br>
> <br>
> CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new
> logins to a SQL 2000 instance, regardless of which SQL client tool you
> use, you need to use sp_addlogin or sp_grantlogin (depending on whether
> it's a standard SQL login or a trusted login we're talking about).&nbs
p; I
> think the GUI in Management Studio ought to take care of this
> automatically (ie. use different commands depending on the server
> version) but if you want to use T-SQL yourself then you need to write
> the correct statements for the SQL version the server is running.<br>
> </tt>
> <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"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com">http://sqlner
d.blogspot.com</a></font></span>
> </p>
> </div>
> <br>
> <br>
> <a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:eshhyasi@.gmail.com">eshhy
asi@.gmail.com</a> wrote:
> <blockquote
> cite="mid1151465632.155321.236760@.m73g2000cwd.googlegroups.com"
> type="cite">
> <pre wrap="">Hi,
> I am using Sql server 2005 and when I try to create a new login from
> the sql server mgmnt studio, I get this error.
> Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near 'LOGIN'.
> I have logged in as "sa" and the login statement that I am using is:
> CREATE LOGIN test WITH PASSWORD = 'beta'
> The product version is 8.00.2039.
> Anybody knows whats wrong'
> Thanks for helping out.
> Esha
> </pre>
> </blockquote>
> </body>
> </html>
> --060001040307010407040902--|||Thanks Mike,
I used sp_addlogin and it worked.
Thanks a lot,
Esha
Mike Hodgson wrote:
> Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
> instance by the sounds of it. What's the version of the SQL instance
> (run "SELECT SERVERPROPERTY('ProductVersion')")?
> CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new logins
> to a SQL 2000 instance, regardless of which SQL client tool you use, you
> need to use sp_addlogin or sp_grantlogin (depending on whether it's a
> standard SQL login or a trusted login we're talking about). I think the
> GUI in Management Studio ought to take care of this automatically (ie.
> use different commands depending on the server version) but if you want
> to use T-SQL yourself then you need to write the correct statements for
> the SQL version the server is running.
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> eshhyasi@.gmail.com wrote:
>
> --060001040307010407040902
> Content-Type: text/html; charset=ISO-8859-1
> X-Google-AttachSize: 2029
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>
> <head>
> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
> </head>
> <body bgcolor="#ffffff" text="#000000">
> <tt>Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
> instance by the sounds of it. What's the version of the SQL inst
ance
> (run "SELECT SERVERPROPERTY('ProductVersion')")?<br>
> <br>
> CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new
> logins to a SQL 2000 instance, regardless of which SQL client tool you
> use, you need to use sp_addlogin or sp_grantlogin (depending on whether
> it's a standard SQL login or a trusted login we're talking about).&nbs
p; I
> think the GUI in Management Studio ought to take care of this
> automatically (ie. use different commands depending on the server
> version) but if you want to use T-SQL yourself then you need to write
> the correct statements for the SQL version the server is running.<br>
> </tt>
> <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"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com">http://sqlner
d.blogspot.com</a></font></span>
> </p>
> </div>
> <br>
> <br>
> <a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:eshhyasi@.gmail.com">eshhy
asi@.gmail.com</a> wrote:
> <blockquote
> cite="mid1151465632.155321.236760@.m73g2000cwd.googlegroups.com"
> type="cite">
> <pre wrap="">Hi,
> I am using Sql server 2005 and when I try to create a new login from
> the sql server mgmnt studio, I get this error.
> Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near 'LOGIN'.
> I have logged in as "sa" and the login statement that I am using is:
> CREATE LOGIN test WITH PASSWORD = 'beta'
> The product version is 8.00.2039.
> Anybody knows whats wrong'
> Thanks for helping out.
> Esha
> </pre>
> </blockquote>
> </body>
> </html>
> --060001040307010407040902--|||Hi,
I am using Sql server 2005 and when I try to create a new login from
the sql server mgmnt studio, I get this error.
Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near 'LOGIN'.
I have logged in as "sa" and the login statement that I am using is:
CREATE LOGIN test WITH PASSWORD = 'beta'
The product version is 8.00.2039.
Anybody knows whats wrong'
Thanks for helping out.
Esha|||Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
instance by the sounds of it. What's the version of the SQL instance
(run "SELECT SERVERPROPERTY('ProductVersion')")?
CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new logins
to a SQL 2000 instance, regardless of which SQL client tool you use, you
need to use sp_addlogin or sp_grantlogin (depending on whether it's a
standard SQL login or a trusted login we're talking about). I think the
GUI in Management Studio ought to take care of this automatically (ie.
use different commands depending on the server version) but if you want
to use T-SQL yourself then you need to write the correct statements for
the SQL version the server is running.
*mike hodgson*
http://sqlnerd.blogspot.com
eshhyasi@.gmail.com wrote:

>Hi,
>I am using Sql server 2005 and when I try to create a new login from
>the sql server mgmnt studio, I get this error.
>Msg 170, Level 15, State 1, Line 1
>Line 1: Incorrect syntax near 'LOGIN'.
>I have logged in as "sa" and the login statement that I am using is:
>CREATE LOGIN test WITH PASSWORD = 'beta'
>The product version is 8.00.2039.
>Anybody knows whats wrong'
>Thanks for helping out.
>Esha
>
>|||Even you are using Management Studio, you are connected to a SQL Server 2000
instance (according to your product version). You should connect to a SQL
Server 2005 instance to use create login.
Ben Nevarez, MCDBA, OCP
Database Administrator
"eshhyasi@.gmail.com" wrote:

> Hi,
> I am using Sql server 2005 and when I try to create a new login from
> the sql server mgmnt studio, I get this error.
> Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near 'LOGIN'.
> I have logged in as "sa" and the login statement that I am using is:
> CREATE LOGIN test WITH PASSWORD = 'beta'
> The product version is 8.00.2039.
> Anybody knows whats wrong'
> Thanks for helping out.
> Esha
>|||Thanks Mike,
I used sp_addlogin and it worked.
Thanks a lot,
Esha
Mike Hodgson wrote:
> Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
> instance by the sounds of it. What's the version of the SQL instance
> (run "SELECT SERVERPROPERTY('ProductVersion')")?
> CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new logins
> to a SQL 2000 instance, regardless of which SQL client tool you use, you
> need to use sp_addlogin or sp_grantlogin (depending on whether it's a
> standard SQL login or a trusted login we're talking about). I think the
> GUI in Management Studio ought to take care of this automatically (ie.
> use different commands depending on the server version) but if you want
> to use T-SQL yourself then you need to write the correct statements for
> the SQL version the server is running.
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> eshhyasi@.gmail.com wrote:
>
> --060001040307010407040902
> Content-Type: text/html; charset=ISO-8859-1
> X-Google-AttachSize: 2029
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>
> <head>
> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
> </head>
> <body bgcolor="#ffffff" text="#000000">
> <tt>Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
> instance by the sounds of it. What's the version of the SQL inst
ance
> (run "SELECT SERVERPROPERTY('ProductVersion')")?<br>
> <br>
> CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new
> logins to a SQL 2000 instance, regardless of which SQL client tool you
> use, you need to use sp_addlogin or sp_grantlogin (depending on whether
> it's a standard SQL login or a trusted login we're talking about).&nbs
p; I
> think the GUI in Management Studio ought to take care of this
> automatically (ie. use different commands depending on the server
> version) but if you want to use T-SQL yourself then you need to write
> the correct statements for the SQL version the server is running.<br>
> </tt>
> <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"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com">http://sqlner
d.blogspot.com</a></font></span>
> </p>
> </div>
> <br>
> <br>
> <a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:eshhyasi@.gmail.com">eshhy
asi@.gmail.com</a> wrote:
> <blockquote
> cite="mid1151465632.155321.236760@.m73g2000cwd.googlegroups.com"
> type="cite">
> <pre wrap="">Hi,
> I am using Sql server 2005 and when I try to create a new login from
> the sql server mgmnt studio, I get this error.
> Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near 'LOGIN'.
> I have logged in as "sa" and the login statement that I am using is:
> CREATE LOGIN test WITH PASSWORD = 'beta'
> The product version is 8.00.2039.
> Anybody knows whats wrong'
> Thanks for helping out.
> Esha
> </pre>
> </blockquote>
> </body>
> </html>
> --060001040307010407040902--|||Thanks Mike,
I used sp_addlogin and it worked.
Thanks a lot,
Esha
Mike Hodgson wrote:
> Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
> instance by the sounds of it. What's the version of the SQL instance
> (run "SELECT SERVERPROPERTY('ProductVersion')")?
> CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new logins
> to a SQL 2000 instance, regardless of which SQL client tool you use, you
> need to use sp_addlogin or sp_grantlogin (depending on whether it's a
> standard SQL login or a trusted login we're talking about). I think the
> GUI in Management Studio ought to take care of this automatically (ie.
> use different commands depending on the server version) but if you want
> to use T-SQL yourself then you need to write the correct statements for
> the SQL version the server is running.
> --
> *mike hodgson*
> http://sqlnerd.blogspot.com
>
> eshhyasi@.gmail.com wrote:
>
> --060001040307010407040902
> Content-Type: text/html; charset=ISO-8859-1
> X-Google-AttachSize: 2029
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>
> <head>
> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
> </head>
> <body bgcolor="#ffffff" text="#000000">
> <tt>Yeah, you're trying to run a "CREATE LOGIN" statement on a SQL 2000
> instance by the sounds of it. What's the version of the SQL inst
ance
> (run "SELECT SERVERPROPERTY('ProductVersion')")?<br>
> <br>
> CREATE LOGIN is new to the SQL 2005 dialect of T-SQL. To add new
> logins to a SQL 2000 instance, regardless of which SQL client tool you
> use, you need to use sp_addlogin or sp_grantlogin (depending on whether
> it's a standard SQL login or a trusted login we're talking about).&nbs
p; I
> think the GUI in Management Studio ought to take care of this
> automatically (ie. use different commands depending on the server
> version) but if you want to use T-SQL yourself then you need to write
> the correct statements for the SQL version the server is running.<br>
> </tt>
> <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"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com">http://sqlner
d.blogspot.com</a></font></span>
> </p>
> </div>
> <br>
> <br>
> <a class="moz-txt-link-abbreviated" href="http://links.10026.com/?link=mailto:eshhyasi@.gmail.com">eshhy
asi@.gmail.com</a> wrote:
> <blockquote
> cite="mid1151465632.155321.236760@.m73g2000cwd.googlegroups.com"
> type="cite">
> <pre wrap="">Hi,
> I am using Sql server 2005 and when I try to create a new login from
> the sql server mgmnt studio, I get this error.
> Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near 'LOGIN'.
> I have logged in as "sa" and the login statement that I am using is:
> CREATE LOGIN test WITH PASSWORD = 'beta'
> The product version is 8.00.2039.
> Anybody knows whats wrong'
> Thanks for helping out.
> Esha
> </pre>
> </blockquote>
> </body>
> </html>
> --060001040307010407040902--

Error copying databases in SQL Server 2005

How does one copy databases in SQLServer 2005?

I am trying to copy a database from one instance of SQLServer 2005 to another instance of SQLServer 2005 using the SQL Server Management Studio Copy Database Wizard. The source database is a continuously updatable database, while the destination database is used for reporting purposes.

When the wizard tries to create a SSIS package (as part of Copy Database), I get the following error:

While trying to find a folder on SQL an OLE DB error was encountered with error code 0x80004005 ([DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.)

The details have additional message:
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.FolderExistsOnSqlServer(String strFolderName, String strServerName, String strServerUserName, String strServerPassword)
at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.EnsurePackageFolderExist(String folderName, Application app, String serverName, String loginName, String password)
at Microsoft.SqlServer.Management.CopyDatabaseWizard.PackageCreator.SavePackage()

=============================================

While trying to find a folder on SQL an OLE DB error was encountered with error code 0x80004005 ([DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.)
-
Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.FolderExistsOnSQLServer(String bstrFolderName, String bstrServerName, String bstrServerUserName, String bstrServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.FolderExistsOnSqlServer(String strFolderName, String strServerName, String strServerUserName, String strServerPassword)

Hi

Copy database wizard is similar to EXPORT/IMPORT wizard of SQL Server 2000. There are new features in SQL Server 2005 for your scenario. You can use Database Mirroring, create a Snapshot on mirrored database for viewing data and can use for reporting services.|||Hi Jason,
This was a known problem in the past that should be working fine with the next CTP release. Right now, your best bet is to detach the database, copy to the destination, and then reattach it. You'll then need to copy recreate your logins at the destination to match with your users.
Thank you,
Bill Ramos

Error Connection with instance

How i can create the Instance into my sql server?
After create it , how to add into ODBC?have any different for the login
authentication between instance and local server?> How i can create the Instance into my sql server?
> After create it , how to add into ODBC?have any different for the login
> authentication between instance and local server?
It is hard to say what went wrong from your info. You can check how to
connect to SQL Server at
http://msdn2.microsoft.com/en-gb/library/ms190944.aspx. You can check
different connection string, including ODBS connection strings, at
http://www.connectionstrings.com/.
Dejan Sarka
http://www.solidqualitylearning.com/blogs/

Error Connection with instance

How i can create the Instance into my sql server?
After create it , how to add into ODBC?have any different for the login
authentication between instance and local server?> How i can create the Instance into my sql server?
> After create it , how to add into ODBC?have any different for the login
> authentication between instance and local server?
It is hard to say what went wrong from your info. You can check how to
connect to SQL Server at
http://msdn2.microsoft.com/en-gb/library/ms190944.aspx. You can check
different connection string, including ODBS connection strings, at
http://www.connectionstrings.com/.
--
Dejan Sarka
http://www.solidqualitylearning.com/blogs/

Error connection to MSDE

Hi all,
I have the Windows 2003 Server in my company and the MSDE SP3 install with
an instance for a program. But the program can't access the database, I have
tried to create a new data source to SQL Server in ODBC and it tells me SQL
Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
SQL server not found).
The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
protocols in SVRNETCN.
Does anyone know what to do?
Thanks
Hi,
From the SQL server MSDE installed machine can you try to connect to SQL
server using both authentication using OSQL.
OSQL -Sservername -Usa -Ppassword
The aove command is suppose to go to a SQL Prompt. If it does then your SQL
server is working fine.If it is not look into sql serevr logs and find the
rason why sql server is down.
If your first stpe passed then, From command prompt execute a PING from your
client PC to MSDE server.
If it fail "Request time out" then it is a network issue.
Thanks
Hari
MCDBA
"Pedro" <pedronazario@.timetech.pt> wrote in message
news:4065ce47$0$3527$a729d347@.news.telepac.pt...
> Hi all,
>
> I have the Windows 2003 Server in my company and the MSDE SP3 install with
> an instance for a program. But the program can't access the database, I
have
> tried to create a new data source to SQL Server in ODBC and it tells me
SQL
> Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
> SQL server not found).
>
> The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
> protocols in SVRNETCN.
>
> Does anyone know what to do?
>
> Thanks
>
|||By default only shared memory is enabled when you install MSDE. If the
connection is being made from a remote machine or uisng TCP/IP or named
pipes to connect locally the connection will fail. You can use svrnetcn.exe
(SQL Server Network Utiltiy) to enable TCP/IP and/or named pipes.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Error connection to MSDE

Hi all,
I have the Windows 2003 Server in my company and the MSDE SP3 install with
an instance for a program. But the program can't access the database, I have
tried to create a new data source to SQL Server in ODBC and it tells me SQL
Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
SQL server not found).
The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
protocols in SVRNETCN.
Does anyone know what to do?
ThanksHi,
From the SQL server MSDE installed machine can you try to connect to SQL
server using both authentication using OSQL.
OSQL -Sservername -Usa -Ppassword
The aove command is suppose to go to a SQL Prompt. If it does then your SQL
server is working fine.If it is not look into sql serevr logs and find the
rason why sql server is down.
If your first stpe passed then, From command prompt execute a PING from your
client PC to MSDE server.
If it fail "Request time out" then it is a network issue.
Thanks
Hari
MCDBA
"Pedro" <pedronazario@.timetech.pt> wrote in message
news:4065ce47$0$3527$a729d347@.news.telepac.pt...
> Hi all,
>
> I have the Windows 2003 Server in my company and the MSDE SP3 install with
> an instance for a program. But the program can't access the database, I
have
> tried to create a new data source to SQL Server in ODBC and it tells me
SQL
> Server Error: 11004 (Connection failed) and SQL Server Error: 6 (Specified
> SQL server not found).
>
> The MSDE is running with the name "SERVER\INSTANCE". I have enabled the
> protocols in SVRNETCN.
>
> Does anyone know what to do?
>
> Thanks
>|||By default only shared memory is enabled when you install MSDE. If the
connection is being made from a remote machine or uisng TCP/IP or named
pipes to connect locally the connection will fail. You can use svrnetcn.exe
(SQL Server Network Utiltiy) to enable TCP/IP and/or named pipes.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Error Connecting To SQL 2005 through Webservice using SQL Authentication

Running a SQL 2005 Database under a Default instance. i.e. (SERVERNAME) and not (SERVERNAME/SQL2005)

I have a SQL Login sa password.

When I connect to SQL 2005 from anywhere other then the webservice it works fine.

In my webservice i am using System.Data.SqlClient.

SqlConnection, SqlCommand, SqlDataAdapter are being used to called a stored procedure and return the data into a System.Data.DataSet.

I get the following error when calling DataAdapter.Fill(dataSet);

{"TCP Provider: An existing connection was forcibly closed by the remote host.\r\n\r\nLogin failed for user 'sa'."}

I have no resolutions as of yet. Any help would be greatly appreciated.

Did you mean you can connect to the SQL2005 from anywhere with 'sa' login, except webservice? You can check the status of 'sa' login in management studio under Security->Logins, also make sure the Authentication Mode is SQL Server and Windows.|||

I have checked the status of the login for user "sa" and it has access rights and grant levels to everything it needs to.

I have also created a new account specifically for that database which does not work either. Same error.

And yes my SQL 2005 Instance is configured to use both SQL Authentication and Windows Authentication. (Mixed Mode).

Any Ideas?

|||

If you encountered this issue when you're trying to establish encrypted connection , you may take a look at this article:

http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx

Error connecting to SQL 2000 remotely

We are trying to connect to a specific database on an instance of SQL 2000
(there are two instances on this server) running on W2K.
However when we try and login (the username and password are correct) we
receive the following error:
Server Error in '/SimplyWeb' Application.
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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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)
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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)]
BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
e) +517
Infragistics.WebUI.WebDataInput.WebImageButton.OnC lick(Int32 action) +91
Infragistics.WebUI.WebControls.Buttons.WebButtonBa se.System.Web.UI.IPostBackDataHandler.RaisePostDat aChangedEvent() +18
System.Web.UI.Page.RaiseChangedEvents() +137
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832
Any ideas or hints to allow remote connections to a SQL 2000 server?
The hint would be simple: a bit more study on SQL Server configuration. Look
into these:
1. Does the SQL Server instance allow remote connection (from other
computer?)
2. Does the SQL Server use SQL Server security - mixed security mode -
(using username/password in connectionString)?
If you can clearly answer these two questions, and still have problem, then
you have to show some code, especially the ConnectionString, and describe
more details.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> We are trying to connect to a specific database on an instance of SQL 2000
> (there are two instances on this server) running on W2K.
> However when we try and login (the username and password are correct) we
> receive the following error:
> Server Error in '/SimplyWeb' Application.
> ----
> 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)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: 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)
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [SqlException (0x80131904): 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)]
> BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> e) +517
> Infragistics.WebUI.WebDataInput.WebImageButton.OnC lick(Int32 action) +91
> Infragistics.WebUI.WebControls.Buttons.WebButtonBa se.System.Web.UI.IPostBackDataHandler.RaisePostDat aChangedEvent()
> +18
> System.Web.UI.Page.RaiseChangedEvents() +137
> System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
>
>
> ----
> Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> ASP.NET
> Version:2.0.50727.832
>
> Any ideas or hints to allow remote connections to a SQL 2000 server?
|||Found out I had brackets around the server name. Now getting a different
error, this time:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
SqlException (0x80131904): An error has occurred while establishing a
connection to the server.
I have checked that named pipes and TCP/IP are allowed. What should the
named pipes string look like for connecting to a local database?
"Norman Yuan" wrote:

> The hint would be simple: a bit more study on SQL Server configuration. Look
> into these:
> 1. Does the SQL Server instance allow remote connection (from other
> computer?)
> 2. Does the SQL Server use SQL Server security - mixed security mode -
> (using username/password in connectionString)?
> If you can clearly answer these two questions, and still have problem, then
> you have to show some code, especially the ConnectionString, and describe
> more details.
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
>

Error connecting to SQL 2000 remotely

We are trying to connect to a specific database on an instance of SQL 2000
(there are two instances on this server) running on W2K.
However when we try and login (the username and password are correct) we
receive the following error:
Server Error in '/SimplyWeb' Application.
----
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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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)
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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)]
BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
e) +517
Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent() +18
System.Web.UI.Page.RaiseChangedEvents() +137
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
----
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832
Any ideas or hints to allow remote connections to a SQL 2000 server?The hint would be simple: a bit more study on SQL Server configuration. Look
into these:
1. Does the SQL Server instance allow remote connection (from other
computer?)
2. Does the SQL Server use SQL Server security - mixed security mode -
(using username/password in connectionString)?
If you can clearly answer these two questions, and still have problem, then
you have to show some code, especially the ConnectionString, and describe
more details.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> We are trying to connect to a specific database on an instance of SQL 2000
> (there are two instances on this server) running on W2K.
> However when we try and login (the username and password are correct) we
> receive the following error:
> Server Error in '/SimplyWeb' Application.
> ----
> 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)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: 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)
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [SqlException (0x80131904): 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)]
> BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> e) +517
> Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
> Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent()
> +18
> System.Web.UI.Page.RaiseChangedEvents() +137
> System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
>
>
> ----
> Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> ASP.NET
> Version:2.0.50727.832
>
> Any ideas or hints to allow remote connections to a SQL 2000 server?|||Found out I had brackets around the server name. Now getting a different
error, this time:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
SqlException (0x80131904): An error has occurred while establishing a
connection to the server.
I have checked that named pipes and TCP/IP are allowed. What should the
named pipes string look like for connecting to a local database?
"Norman Yuan" wrote:
> The hint would be simple: a bit more study on SQL Server configuration. Look
> into these:
> 1. Does the SQL Server instance allow remote connection (from other
> computer?)
> 2. Does the SQL Server use SQL Server security - mixed security mode -
> (using username/password in connectionString)?
> If you can clearly answer these two questions, and still have problem, then
> you have to show some code, especially the ConnectionString, and describe
> more details.
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> > We are trying to connect to a specific database on an instance of SQL 2000
> > (there are two instances on this server) running on W2K.
> >
> > However when we try and login (the username and password are correct) we
> > receive the following error:
> >
> > Server Error in '/SimplyWeb' Application.
> > ----
> >
> > 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)
> > Description: An unhandled exception occurred during the execution of the
> > current web request. Please review the stack trace for more information
> > about
> > the error and where it originated in the code.
> >
> > Exception Details: System.Data.SqlClient.SqlException: 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)
> >
> > Source Error:
> >
> > An unhandled exception was generated during the execution of the current
> > web
> > request. Information regarding the origin and location of the exception
> > can
> > be identified using the exception stack trace below.
> >
> > Stack Trace:
> >
> >
> > [SqlException (0x80131904): 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)]
> > BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> > SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> > e) +517
> > Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
> >
> > Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent()
> > +18
> > System.Web.UI.Page.RaiseChangedEvents() +137
> > System.Web.UI.Page.ProcessRequestMain(Boolean
> > includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
> >
> >
> >
> >
> > ----
> > Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> > ASP.NET
> > Version:2.0.50727.832
> >
> >
> > Any ideas or hints to allow remote connections to a SQL 2000 server?
>

Error connecting to SQL 2000 remotely

We are trying to connect to a specific database on an instance of SQL 2000
(there are two instances on this server) running on W2K.
However when we try and login (the username and password are correct) we
receive the following error:
Server Error in '/SimplyWeb' Application.
----
--
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/Instanc
e
Specified)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information abou
t
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: An error has occurred
while establishing a connection to the server. When connecting to SQL Serve
r
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)
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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 no
t
allow remote connections. (provider: SQL Network Interfaces, error: 26 -
Error Locating Server/Instance Specified)]
BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
e) +517
Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBack
DataHandler.RaisePostDataChangedEvent() +18
System.Web.UI.Page.RaiseChangedEvents() +137
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
----
--
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET
Version:2.0.50727.832
Any ideas or hints to allow remote connections to a SQL 2000 server?The hint would be simple: a bit more study on SQL Server configuration. Look
into these:
1. Does the SQL Server instance allow remote connection (from other
computer?)
2. Does the SQL Server use SQL Server security - mixed security mode -
(using username/password in connectionString)?
If you can clearly answer these two questions, and still have problem, then
you have to show some code, especially the ConnectionString, and describe
more details.
"Simon" <Simon@.discussions.microsoft.com> wrote in message
news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
> We are trying to connect to a specific database on an instance of SQL 2000
> (there are two instances on this server) running on W2K.
> However when we try and login (the username and password are correct) we
> receive the following error:
> Server Error in '/SimplyWeb' Application.
> ----
--
> 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)
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: 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)
> Source Error:
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [SqlException (0x80131904): 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)]
> BusinessRules.IUsers.clsIUsers..ctor(String InUserName) +54
> SimplyWebPersonnel.Login.Login.LoginClick(Object sender, ButtonEventArgs
> e) +517
> Infragistics.WebUI.WebDataInput.WebImageButton.OnClick(Int32 action) +91
> Infragistics.WebUI.WebControls.Buttons.WebButtonBase.System.Web.UI.IPostBa
ckDataHandler.RaisePostDataChangedEvent()
> +18
> System.Web.UI.Page.RaiseChangedEvents() +137
> System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4778
>
>
> ----
--
> Version Information: Microsoft .NET Framework Version:2.0.50727.832;
> ASP.NET
> Version:2.0.50727.832
>
> Any ideas or hints to allow remote connections to a SQL 2000 server?|||Found out I had brackets around the server name. Now getting a different
error, this time:
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
SqlException (0x80131904): An error has occurred while establishing a
connection to the server.
I have checked that named pipes and TCP/IP are allowed. What should the
named pipes string look like for connecting to a local database?
"Norman Yuan" wrote:

> The hint would be simple: a bit more study on SQL Server configuration. Lo
ok
> into these:
> 1. Does the SQL Server instance allow remote connection (from other
> computer?)
> 2. Does the SQL Server use SQL Server security - mixed security mode -
> (using username/password in connectionString)?
> If you can clearly answer these two questions, and still have problem, the
n
> you have to show some code, especially the ConnectionString, and describe
> more details.
>
> "Simon" <Simon@.discussions.microsoft.com> wrote in message
> news:EFC3F694-126C-473B-AD0B-AA59ACCF0411@.microsoft.com...
>