![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Using this command, I get error C:\WINDOWS>c:\WINDOWS\Microsoft.NET\Framework\v2.0 .50727\aspnet_regsql.exe -A all -C "Data Source=np:\\VISTA64\pipe\sql\query; Application Name='\'; Initial Catalog=ASPNETMembershipDB; Integrated Security=SSPI; Password=SQLAgent; User ID=SQLAgent;" I've verified using PipeList that sql\query is on the VISTA64 machine. Using SQL Server 2008. on 64 bit vista. trying to hookup client. I've verified that the ports exist and are enabled on the client (XP sp3) machine by enabling logging on the the communication on these ports. (on both Client and Server). I've created the ASPNETMembershipDB database and SQLAgent has all the rights in the world. Is there a problem with the string? Minor jiggering of the string has produced errors 40 , 25, 26 , I just don't know where to turn next. TIA. -- Gak - Finecats |
#3
| |||
| |||
|
|
SQL server is a server itself, it should not need extras to connect that, can you try a normal connection string. www.connectionstrings.com Cor "usfinecats" <usfinecats (AT) nospam (DOT) nospam> wrote in message news:C98E33E2-C701-44F5-A4D5-1A597C5B1E1C (AT) microsoft (DOT) com... Using this command, I get error C:\WINDOWS>c:\WINDOWS\Microsoft.NET\Framework\v2.0 .50727\aspnet_regsql.exe -A all -C "Data Source=np:\\VISTA64\pipe\sql\query; Application Name='\'; Initial Catalog=ASPNETMembershipDB; Integrated Security=SSPI; Password=SQLAgent; User ID=SQLAgent;" I've verified using PipeList that sql\query is on the VISTA64 machine. Using SQL Server 2008. on 64 bit vista. trying to hookup client. I've verified that the ports exist and are enabled on the client (XP sp3) machine by enabling logging on the the communication on these ports. (on both Client and Server). I've created the ASPNETMembershipDB database and SQLAgent has all the rights in the world. Is there a problem with the string? Minor jiggering of the string has produced errors 40 , 25, 26 , I just don't know where to turn next. TIA. -- Gak - Finecats |
#4
| |||
| |||
|
|
And for the very dense among us all, prey tell what that command string for aspnet_regsql might be inorder to connect to SQL server on a differnet computer on my workstation group? -- Gak - Finecats "Cor Ligthert[MVP]" wrote: SQL server is a server itself, it should not need extras to connect that, can you try a normal connection string. www.connectionstrings.com Cor "usfinecats" <usfinecats (AT) nospam (DOT) nospam> wrote in message news:C98E33E2-C701-44F5-A4D5-1A597C5B1E1C (AT) microsoft (DOT) com... Using this command, I get error C:\WINDOWS>c:\WINDOWS\Microsoft.NET\Framework\v2.0 .50727\aspnet_regsql.exe -A all -C "Data Source=np:\\VISTA64\pipe\sql\query; Application Name='\'; Initial Catalog=ASPNETMembershipDB; Integrated Security=SSPI; Password=SQLAgent; User ID=SQLAgent;" I've verified using PipeList that sql\query is on the VISTA64 machine. Using SQL Server 2008. on 64 bit vista. trying to hookup client. I've verified that the ports exist and are enabled on the client (XP sp3) machine by enabling logging on the the communication on these ports. (on both Client and Server). I've created the ASPNETMembershipDB database and SQLAgent has all the rights in the world. Is there a problem with the string? Minor jiggering of the string has produced errors 40 , 25, 26 , I just don't know where to turn next. TIA. -- Gak - Finecats |
#5
| |||
| |||
|
|
From: =?Utf-8?B?dXNmaW5lY2F0cw==?= <usfinecats (AT) nospam (DOT) nospam Subject: SQL Server 2008/aspnet_regsql problem Date: Fri, 8 May 2009 18:46:00 -0700 Using this command, I get error C:\WINDOWS>c:\WINDOWS\Microsoft.NET\Framework\v2.0 .50727\aspnet_regsql.exe -A all -C "Data Source=np:\\VISTA64\pipe\sql\query; Application Name='\'; Initial Catalog=ASPNETMembershipDB; Integrated Security=SSPI; Password=SQLAgent; User ID=SQLAgent;" I've verified using PipeList that sql\query is on the VISTA64 machine. Using SQL Server 2008. on 64 bit vista. trying to hookup client. I've verified that the ports exist and are enabled on the client (XP sp3) machine by enabling logging on the the communication on these ports. (on both Client and Server). I've created the ASPNETMembershipDB database and SQLAgent has all the rights in the world. Is there a problem with the string? Minor jiggering of the string has produced errors 40 , 25, 26 , I just don't know where to turn next. TIA. -- Gak - Finecats |
#6
| |||
| |||
|
|
Using this command, I get error C:\WINDOWS>c:\WINDOWS\Microsoft.NET\Framework\v2.0 .50727\aspnet_regsql.exe -A all -C "Data Source=np:\\VISTA64\pipe\sql\query; Application Name='\'; Initial Catalog=ASPNETMembershipDB; Integrated Security=SSPI; Password=SQLAgent; User ID=SQLAgent;" I've verified using PipeList that sql\query is on the VISTA64 machine. Using SQL Server 2008. on 64 bit vista. trying to hookup client. I've verified that the ports exist and are enabled on the client (XP sp3) machine by enabling logging on the the communication on these ports. (on both Client and Server). I've created the ASPNETMembershipDB database and SQLAgent has all the rights in the world. Is there a problem with the string? Minor jiggering of the string has produced errors 40 , 25, 26 , I just don't know where to turn next. TIA. -- Gak - Finecats |
#7
| |||
| |||
|
|
Content-Transfer-Encoding: 7bit From: stcheng (AT) online (DOT) microsoft.com ("Steven Cheng") Organization: Microsoft Date: Mon, 11 May 2009 02:28:39 GMT Subject: RE: SQL Server 2008/aspnet_regsql problem Hi Gak, As for the aspnet_regsql.exe, you can simply use the "-S" option to specify the remote SQL Server instance name(instead of specify the entire connectionstring). The server instance name is just the normal "computername\instanceName" syntax. e.g. "myServer2k3\sql2008Inst" http://msdn.microsoft.com/en-us/library/x28wfk74.aspx Here is a walkthrough on using this tool: http://www.shiningstar.net/ASPNet_Articles/SqlMembershipProvider.aspx Btw, as other members mentioned, you need to make sure the remote SQL server instance has correctly configured to allow remote connection. You can also trying connecting the server via SQL management studio if available on the box. For configuring 2008 for remote connection, here is an article you can refer to http://www.linglom.com/2009/03/28/enable-remote-connection-on-sql-server-20 0 8-express/ Sincerely, Steven Cheng Microsoft MSDN Online Support Lead |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |