I am trying to move my SharePoint db's from on drive on a SQL Server to
another. Apparently, This cannot be done with the Management Tool and must
be done with the sqlcmd.
The first comand needed is: >sqlcmd -S
\\.\pipe\mssql$microsoft##ssee\sql\query -E
This yields the follwoing error:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
TCP, Named Pipes and Shared Memory are enabled and configuration allows for
remote connection (even thought this local)
I have tried to modify the command with the specific instance and
server\instance all result in the same error.
I am at a loss as what to do to move these db's
Can anyone help with this issue.
Thanks,
Mike Altman
Hello Mike,
Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
using Management Studio, go to the operating system and move all your
database files to the new drive and then attach your databases using
Management Studio again.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"travldc" wrote:
> I am trying to move my SharePoint db's from on drive on a SQL Server to
> another. Apparently, This cannot be done with the Management Tool and must
> be done with the sqlcmd.
> The first comand needed is: >sqlcmd -S
> \\.\pipe\mssql$microsoft##ssee\sql\query -E
> This yields the follwoing error:
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server does
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> TCP, Named Pipes and Shared Memory are enabled and configuration allows for
> remote connection (even thought this local)
> I have tried to modify the command with the specific instance and
> server\instance all result in the same error.
> I am at a loss as what to do to move these db's
> Can anyone help with this issue.
> Thanks,
> Mike Altman
>
>
|||Hi Ben,
I had read that this was not best practice, but it worked just fine. Thanks
for the help.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hello Mike,
> Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
> using Management Studio, go to the operating system and move all your
> database files to the new drive and then attach your databases using
> Management Studio again.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "travldc" wrote:
Showing posts with label sharepoint. Show all posts
Showing posts with label sharepoint. Show all posts
Friday, March 9, 2012
Error connecting to SQL from within same machine
I am trying to move my SharePoint db's from on drive on a SQL Server to
another. Apparently, This cannot be done with the Management Tool and must
be done with the sqlcmd.
The first comand needed is: >sqlcmd -S
\\.\pipe\mssql$microsoft##ssee\sql\query -E
This yields the follwoing error:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
TCP, Named Pipes and Shared Memory are enabled and configuration allows for
remote connection (even thought this local)
I have tried to modify the command with the specific instance and
server\instance all result in the same error.
I am at a loss as what to do to move these db's
Can anyone help with this issue.
Thanks,
Mike AltmanHello Mike,
Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
using Management Studio, go to the operating system and move all your
database files to the new drive and then attach your databases using
Management Studio again.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"travldc" wrote:
> I am trying to move my SharePoint db's from on drive on a SQL Server to
> another. Apparently, This cannot be done with the Management Tool and must
> be done with the sqlcmd.
> The first comand needed is: >sqlcmd -S
> \\.\pipe\mssql$microsoft##ssee\sql\query -E
> This yields the follwoing error:
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server does
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> TCP, Named Pipes and Shared Memory are enabled and configuration allows for
> remote connection (even thought this local)
> I have tried to modify the command with the specific instance and
> server\instance all result in the same error.
> I am at a loss as what to do to move these db's
> Can anyone help with this issue.
> Thanks,
> Mike Altman
>
>|||Hi Ben,
I had read that this was not best practice, but it worked just fine. Thanks
for the help.
"Ben Nevarez" wrote:
> Hello Mike,
> Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
> using Management Studio, go to the operating system and move all your
> database files to the new drive and then attach your databases using
> Management Studio again.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "travldc" wrote:
> > I am trying to move my SharePoint db's from on drive on a SQL Server to
> > another. Apparently, This cannot be done with the Management Tool and must
> > be done with the sqlcmd.
> >
> > The first comand needed is: >sqlcmd -S
> > \\.\pipe\mssql$microsoft##ssee\sql\query -E
> >
> > This yields the follwoing error:
> >
> > HResult 0x2, Level 16, State 1
> > Named Pipes Provider: Could not open a connection to SQL Server [2].
> > Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> > establi
> > shing a connection to the server. When connecting to SQL Server 2005, this
> > failu
> > re may be caused by the fact that under the default settings SQL Server does
> > not
> > allow remote connections..
> > Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> >
> > TCP, Named Pipes and Shared Memory are enabled and configuration allows for
> > remote connection (even thought this local)
> >
> > I have tried to modify the command with the specific instance and
> > server\instance all result in the same error.
> >
> > I am at a loss as what to do to move these db's
> >
> > Can anyone help with this issue.
> >
> > Thanks,
> >
> > Mike Altman
> >
> >
> >
> >
another. Apparently, This cannot be done with the Management Tool and must
be done with the sqlcmd.
The first comand needed is: >sqlcmd -S
\\.\pipe\mssql$microsoft##ssee\sql\query -E
This yields the follwoing error:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
TCP, Named Pipes and Shared Memory are enabled and configuration allows for
remote connection (even thought this local)
I have tried to modify the command with the specific instance and
server\instance all result in the same error.
I am at a loss as what to do to move these db's
Can anyone help with this issue.
Thanks,
Mike AltmanHello Mike,
Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
using Management Studio, go to the operating system and move all your
database files to the new drive and then attach your databases using
Management Studio again.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"travldc" wrote:
> I am trying to move my SharePoint db's from on drive on a SQL Server to
> another. Apparently, This cannot be done with the Management Tool and must
> be done with the sqlcmd.
> The first comand needed is: >sqlcmd -S
> \\.\pipe\mssql$microsoft##ssee\sql\query -E
> This yields the follwoing error:
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server does
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> TCP, Named Pipes and Shared Memory are enabled and configuration allows for
> remote connection (even thought this local)
> I have tried to modify the command with the specific instance and
> server\instance all result in the same error.
> I am at a loss as what to do to move these db's
> Can anyone help with this issue.
> Thanks,
> Mike Altman
>
>|||Hi Ben,
I had read that this was not best practice, but it worked just fine. Thanks
for the help.
"Ben Nevarez" wrote:
> Hello Mike,
> Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
> using Management Studio, go to the operating system and move all your
> database files to the new drive and then attach your databases using
> Management Studio again.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "travldc" wrote:
> > I am trying to move my SharePoint db's from on drive on a SQL Server to
> > another. Apparently, This cannot be done with the Management Tool and must
> > be done with the sqlcmd.
> >
> > The first comand needed is: >sqlcmd -S
> > \\.\pipe\mssql$microsoft##ssee\sql\query -E
> >
> > This yields the follwoing error:
> >
> > HResult 0x2, Level 16, State 1
> > Named Pipes Provider: Could not open a connection to SQL Server [2].
> > Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> > establi
> > shing a connection to the server. When connecting to SQL Server 2005, this
> > failu
> > re may be caused by the fact that under the default settings SQL Server does
> > not
> > allow remote connections..
> > Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> >
> > TCP, Named Pipes and Shared Memory are enabled and configuration allows for
> > remote connection (even thought this local)
> >
> > I have tried to modify the command with the specific instance and
> > server\instance all result in the same error.
> >
> > I am at a loss as what to do to move these db's
> >
> > Can anyone help with this issue.
> >
> > Thanks,
> >
> > Mike Altman
> >
> >
> >
> >
Error connecting to SQL from within same machine
I am trying to move my SharePoint db's from on drive on a SQL Server to
another. Apparently, This cannot be done with the Management Tool and must
be done with the sqlcmd.
The first comand needed is: >sqlcmd -S
\\.\pipe\mssql$microsoft##ssee\sql\query -E
This yields the follwoing error:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
TCP, Named Pipes and Shared Memory are enabled and configuration allows for
remote connection (even thought this local)
I have tried to modify the command with the specific instance and
server\instance all result in the same error.
I am at a loss as what to do to move these db's
Can anyone help with this issue.
Thanks,
Mike AltmanHello Mike,
Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
using Management Studio, go to the operating system and move all your
database files to the new drive and then attach your databases using
Management Studio again.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"travldc" wrote:
> I am trying to move my SharePoint db's from on drive on a SQL Server to
> another. Apparently, This cannot be done with the Management Tool and mus
t
> be done with the sqlcmd.
> The first comand needed is: >sqlcmd -S
> \\.\pipe\mssql$microsoft##ssee\sql\query -E
> This yields the follwoing error:
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server do
es
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> TCP, Named Pipes and Shared Memory are enabled and configuration allows fo
r
> remote connection (even thought this local)
> I have tried to modify the command with the specific instance and
> server\instance all result in the same error.
> I am at a loss as what to do to move these db's
> Can anyone help with this issue.
> Thanks,
> Mike Altman
>
>|||Hi Ben,
I had read that this was not best practice, but it worked just fine. Thanks
for the help.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hello Mike,
> Do not use sqlcmd. Just stop your SharePoint services. Detach your databas
es
> using Management Studio, go to the operating system and move all your
> database files to the new drive and then attach your databases using
> Management Studio again.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "travldc" wrote:
>
another. Apparently, This cannot be done with the Management Tool and must
be done with the sqlcmd.
The first comand needed is: >sqlcmd -S
\\.\pipe\mssql$microsoft##ssee\sql\query -E
This yields the follwoing error:
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
TCP, Named Pipes and Shared Memory are enabled and configuration allows for
remote connection (even thought this local)
I have tried to modify the command with the specific instance and
server\instance all result in the same error.
I am at a loss as what to do to move these db's
Can anyone help with this issue.
Thanks,
Mike AltmanHello Mike,
Do not use sqlcmd. Just stop your SharePoint services. Detach your databases
using Management Studio, go to the operating system and move all your
database files to the new drive and then attach your databases using
Management Studio again.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"travldc" wrote:
> I am trying to move my SharePoint db's from on drive on a SQL Server to
> another. Apparently, This cannot be done with the Management Tool and mus
t
> be done with the sqlcmd.
> The first comand needed is: >sqlcmd -S
> \\.\pipe\mssql$microsoft##ssee\sql\query -E
> This yields the follwoing error:
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server do
es
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> TCP, Named Pipes and Shared Memory are enabled and configuration allows fo
r
> remote connection (even thought this local)
> I have tried to modify the command with the specific instance and
> server\instance all result in the same error.
> I am at a loss as what to do to move these db's
> Can anyone help with this issue.
> Thanks,
> Mike Altman
>
>|||Hi Ben,
I had read that this was not best practice, but it worked just fine. Thanks
for the help.
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hello Mike,
> Do not use sqlcmd. Just stop your SharePoint services. Detach your databas
es
> using Management Studio, go to the operating system and move all your
> database files to the new drive and then attach your databases using
> Management Studio again.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "travldc" wrote:
>
Wednesday, February 15, 2012
Error accessing report from anywhere but local server
I am trying to view a report that i created and I get an error everywhere but on the server, where it runs fine. the report uses the sharepoint lists.asmx web service as a datasource, and I'm using Windows Authentication on the datasource. I'm logged on to my desktop with the same account i use on the server, but on the server it runs and on the desktop i get the following error:
|||I added my account specifically with full permissions. i just remembered that the list web service i'm accessing is actually not on the same server as reporting services. is this related to the "double-hop" issue? is there some workaround?|||Try this, I had problems connecting on my PC also until I ensured that my data source was shared. I thought I had done so when I specified it to be a shared data source when creating it in VS 2005 but I also had to do this:
"An error has occurred during report processing. (rsProcessingAborted) Get Online Help Query execution failed for data set 'SiteTripList'. (rsErrorExecutingCommand) Get Online Help Failed to execute web request for the specified URL. (rsXmlDataProviderError) Get Online Help For more information about this error navigate to the report server on the local server machine, or enable remote errors "
After checking the event log I found a System.FormatException being thrown with the message "Input String was not in a correct format."
Any help would be greatly appreciated!!
josh meyer
What does the Properties -> Security look like?|||I added my account specifically with full permissions. i just remembered that the list web service i'm accessing is actually not on the same server as reporting services. is this related to the "double-hop" issue? is there some workaround?|||Try this, I had problems connecting on my PC also until I ensured that my data source was shared. I thought I had done so when I specified it to be a shared data source when creating it in VS 2005 but I also had to do this:
In Report Manager
1) Click on Properties
2) Click on Data Sources
3) Make your Data Source Shared|||
Hi
It does not allow making it share as it throws error.Also even in my case muy reporting services is on other machine and sharepoint on other machine.Hence unable to get access to datasource(maybe).
Will certainly like to get soln to this problem
Error accessing report from anywhere but local server
I am trying to view a report that i created and I get an error everywhere but on the server, where it runs fine. the report uses the sharepoint lists.asmx web service as a datasource, and I'm using Windows Authentication on the datasource. I'm logged on to my desktop with the same account i use on the server, but on the server it runs and on the desktop i get the following error:
|||I added my account specifically with full permissions. i just remembered that the list web service i'm accessing is actually not on the same server as reporting services. is this related to the "double-hop" issue? is there some workaround?|||Try this, I had problems connecting on my PC also until I ensured that my data source was shared. I thought I had done so when I specified it to be a shared data source when creating it in VS 2005 but I also had to do this:
"An error has occurred during report processing. (rsProcessingAborted) Get Online Help Query execution failed for data set 'SiteTripList'. (rsErrorExecutingCommand) Get Online Help Failed to execute web request for the specified URL. (rsXmlDataProviderError) Get Online Help For more information about this error navigate to the report server on the local server machine, or enable remote errors "
After checking the event log I found a System.FormatException being thrown with the message "Input String was not in a correct format."
Any help would be greatly appreciated!!
josh meyer
What does the Properties -> Security look like?|||I added my account specifically with full permissions. i just remembered that the list web service i'm accessing is actually not on the same server as reporting services. is this related to the "double-hop" issue? is there some workaround?|||Try this, I had problems connecting on my PC also until I ensured that my data source was shared. I thought I had done so when I specified it to be a shared data source when creating it in VS 2005 but I also had to do this:
In Report Manager
1) Click on Properties
2) Click on Data Sources
3) Make your Data Source Shared|||
Hi
It does not allow making it share as it throws error.Also even in my case muy reporting services is on other machine and sharepoint on other machine.Hence unable to get access to datasource(maybe).
Will certainly like to get soln to this problem
Error accessing report from anywhere but local server
I am trying to view a report that i created and I get an error everywhere but on the server, where it runs fine. the report uses the sharepoint lists.asmx web service as a datasource, and I'm using Windows Authentication on the datasource. I'm logged on to my desktop with the same account i use on the server, but on the server it runs and on the desktop i get the following error:
|||I added my account specifically with full permissions. i just remembered that the list web service i'm accessing is actually not on the same server as reporting services. is this related to the "double-hop" issue? is there some workaround?|||Try this, I had problems connecting on my PC also until I ensured that my data source was shared. I thought I had done so when I specified it to be a shared data source when creating it in VS 2005 but I also had to do this:
"An error has occurred during report processing. (rsProcessingAborted) Get Online Help Query execution failed for data set 'SiteTripList'. (rsErrorExecutingCommand) Get Online Help Failed to execute web request for the specified URL. (rsXmlDataProviderError) Get Online Help For more information about this error navigate to the report server on the local server machine, or enable remote errors "
After checking the event log I found a System.FormatException being thrown with the message "Input String was not in a correct format."
Any help would be greatly appreciated!!
josh meyer
What does the Properties -> Security look like?|||I added my account specifically with full permissions. i just remembered that the list web service i'm accessing is actually not on the same server as reporting services. is this related to the "double-hop" issue? is there some workaround?|||Try this, I had problems connecting on my PC also until I ensured that my data source was shared. I thought I had done so when I specified it to be a shared data source when creating it in VS 2005 but I also had to do this:
In Report Manager
1) Click on Properties
2) Click on Data Sources
3) Make your Data Source Shared|||
Hi
It does not allow making it share as it throws error.Also even in my case muy reporting services is on other machine and sharepoint on other machine.Hence unable to get access to datasource(maybe).
Will certainly like to get soln to this problem
Subscribe to:
Posts (Atom)