Error encountered while starting the SSIS service

I installed SQL Server 2005 Integration services on Windows XP machine. Then I went to the SQL Server Configuration Manager and tried to Start the SSIS service. The "Log On As" value is "NT AUTHORITY\NetworkService". But I get the follwoing error:

The request failed or the service did not respond in a timely fashion. COnsult the event log or other applicable error logs for details.

Event Log details:
The SQL Server Integration Services service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I tried running the service using the "Local Service" and the "Local System" accounts also, but am still encountering the same error. What do I do...

Are you using SP1? There was a bug in SP1 that stopped the SSIS service from starting under certain conditions.

-Jamie

|||

I dont have any SP installed.

I installed SSIS on another machine and here the service runs successfully under NT AUTHORITY\Network Service. As for the first machine, as of now, I am only able to run it under the current domain account- Is this fine or will it lead to some problems/threats in future.

Error during restore operation

Hi all,
I installed SQL server 2000 on my machine first.
Then i just installed SQL server 2005 tools on above it to get
management studio access.
Now i am trying to restore a database on my machine from backup which
i took from server running SQL server 2005.
i am getting the error-
Too many backup devices specified for backup or restore; only 64 are
allowed. RESTORE HEADER ONLY is terminating abnormally.(Microsoft SQL
Server, Error:3205)
Does anybody know how do i go about to resolve it.
Thanks a lot.
I did some Google which suggests you get this error if you try to restore a 2005 backup to 2000.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<nitinluthra@.gmail.com> wrote in message
news:c1f4f806-807c-4f03-9757-43b9401d89b8@.a5g2000prg.googlegroups.com...
> Hi all,
> I installed SQL server 2000 on my machine first.
> Then i just installed SQL server 2005 tools on above it to get
> management studio access.
> Now i am trying to restore a database on my machine from backup which
> i took from server running SQL server 2005.
> i am getting the error-
> Too many backup devices specified for backup or restore; only 64 are
> allowed. RESTORE HEADER ONLY is terminating abnormally.(Microsoft SQL
> Server, Error:3205)
> Does anybody know how do i go about to resolve it.
> Thanks a lot.
|||I reproduced the error, that's exactly an error message you get when you try
to restore a backup that is taken from a SQL Server 2005 instance.
Ekrem nsoy
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OzMom43nIHA.3652@.TK2MSFTNGP03.phx.gbl...
>I did some Google which suggests you get this error if you try to restore a
>2005 backup to 2000.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> <nitinluthra@.gmail.com> wrote in message
> news:c1f4f806-807c-4f03-9757-43b9401d89b8@.a5g2000prg.googlegroups.com...
>
sql

Error during restore operation

Hi all,
I installed SQL server 2000 on my machine first.
Then i just installed SQL server 2005 tools on above it to get
management studio access.
Now i am trying to restore a database on my machine from backup which
i took from server running SQL server 2005.
i am getting the error-
Too many backup devices specified for backup or restore; only 64 are
allowed. RESTORE HEADER ONLY is terminating abnormally.(Microsoft SQL
Server, Error:3205)
Does anybody know how do i go about to resolve it.
Thanks a lot.I did some Google which suggests you get this error if you try to restore a 2005 backup to 2000.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<nitinluthra@.gmail.com> wrote in message
news:c1f4f806-807c-4f03-9757-43b9401d89b8@.a5g2000prg.googlegroups.com...
> Hi all,
> I installed SQL server 2000 on my machine first.
> Then i just installed SQL server 2005 tools on above it to get
> management studio access.
> Now i am trying to restore a database on my machine from backup which
> i took from server running SQL server 2005.
> i am getting the error-
> Too many backup devices specified for backup or restore; only 64 are
> allowed. RESTORE HEADER ONLY is terminating abnormally.(Microsoft SQL
> Server, Error:3205)
> Does anybody know how do i go about to resolve it.
> Thanks a lot.|||I reproduced the error, that's exactly an error message you get when you try
to restore a backup that is taken from a SQL Server 2005 instance.
--
Ekrem Önsoy
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OzMom43nIHA.3652@.TK2MSFTNGP03.phx.gbl...
>I did some Google which suggests you get this error if you try to restore a
>2005 backup to 2000.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> <nitinluthra@.gmail.com> wrote in message
> news:c1f4f806-807c-4f03-9757-43b9401d89b8@.a5g2000prg.googlegroups.com...
>> Hi all,
>> I installed SQL server 2000 on my machine first.
>> Then i just installed SQL server 2005 tools on above it to get
>> management studio access.
>> Now i am trying to restore a database on my machine from backup which
>> i took from server running SQL server 2005.
>> i am getting the error-
>> Too many backup devices specified for backup or restore; only 64 are
>> allowed. RESTORE HEADER ONLY is terminating abnormally.(Microsoft SQL
>> Server, Error:3205)
>> Does anybody know how do i go about to resolve it.
>> Thanks a lot.
>

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 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:

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
> >
> >
> >
> >

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:
>

Error connecting to sql db on another computer

When I try to connect to an sql express db on another machine, I get this
message
TITLE: Connect to Server
--
Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: -1)
For help, click:
http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
BUTTONS:
OK
The connection between the 2 machines are OK, I can connect to a SQL2000 db,
but not an sql express db
reidarTAnd do you allow "remote connections" as the error message said, don't you?
"reidarT" <reidar@.eivon.no> wrote in message
news:O%23iA%230tuGHA.4888@.TK2MSFTNGP05.phx.gbl...
> When I try to connect to an sql express db on another machine, I get this
> message
> TITLE: Connect to Server
> --
> Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> 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) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
> --
> BUTTONS:
> OK
> The connection between the 2 machines are OK, I can connect to a SQL2000
> db,
> but not an sql express db
> reidarT
>|||reidarT wrote:
> When I try to connect to an sql express db on another machine, I get this
> message
> TITLE: Connect to Server
> --
> Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> 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) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...-1&LinkId=20476
> --
> BUTTONS:
> OK
> The connection between the 2 machines are OK, I can connect to a SQL2000 d
b,
> but not an sql express db
> reidarT
>
Use the Surface Area Configuration Tool to allow remote connections.
They are disabled by default.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Error connecting to sql db on another computer

When I try to connect to an sql express db on another machine, I get this
message
TITLE: Connect to Server
--
Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
--
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: -1)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
--
BUTTONS:
OK
The connection between the 2 machines are OK, I can connect to a SQL2000 db,
but not an sql express db
reidarTAnd do you allow "remote connections" as the error message said, don't you?
"reidarT" <reidar@.eivon.no> wrote in message
news:O%23iA%230tuGHA.4888@.TK2MSFTNGP05.phx.gbl...
> When I try to connect to an sql express db on another machine, I get this
> message
> TITLE: Connect to Server
> --
> Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> 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) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
> --
> BUTTONS:
> OK
> The connection between the 2 machines are OK, I can connect to a SQL2000
> db,
> but not an sql express db
> reidarT
>|||reidarT wrote:
> When I try to connect to an sql express db on another machine, I get this
> message
> TITLE: Connect to Server
> --
> Cannot connect to REIDARNOTEBOOK\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> 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) (Microsoft SQL Server, Error: -1)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
> --
> BUTTONS:
> OK
> The connection between the 2 machines are OK, I can connect to a SQL2000 db,
> but not an sql express db
> reidarT
>
Use the Surface Area Configuration Tool to allow remote connections.
They are disabled by default.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

error connecting to sql db

I have an asp.net project on my laptop 'supposed to be' connecting to a SQL DB on the same machine. But I keep getting this error:

System.Data.SqlClient.SqlException: Cannot open database requested in login 'ASPState'. Login fails. Login failed for user 'xyz'.

It's driving me nuts. Any help would be appreciated.

txs
sonnersYou have to go to Sql Server Manager, go to the database, click Add New User and add the user that needs permission, then give that user owner permission|||I did all this. My SQL knowledge isn't so bad. I've been using the main SQL login account as it's my local machine. This account works for other ASP sites but not for .Net ASP site.|||What does your connection string look like? You may need to add <identity impersonate="true"/> to your web.config file.

Terri

Error connecting to remote SQL Server Analysis Services

Hi All,

I am trying to connect to the SQL Server Analysis Services on a remote server from my local machine, using SQL Server Management Studio.

I am able to connect to the SQL Server Database engine, but while connecting to the SQL Server Analysis services I get the following error :-

"Cannot connect to <IP Address>

A Connection cannot be made. Ensure that the server is running.

(Microsoft.AnalysisServices.AdomdClient)

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond(System)"

Things I have tried:-

- Ensured that the remote connection is enabled.

- Have SQL Server 2005 SP1 installed on the remote server.

- Tried installined SQL Server 2005 SP2 on my local machine, but same error.

I think some issue with the ports might exists, Dont have an exact idea of how to check on with the port settings.

Any kind of help will be appreciated on this.

Regards,

Sumeet:-)

We had similar problems when deploying cubes (although running Vanilla - not SP1)

We could replicate this problem by doing the following

1) Ensure all of the SQL Server Services (inc Analysis Services) are running

2) Browse a cube on your local machine

3) Rebuild this cube on your local machine

4) Check back on the remote server to see if AS is still running

If your issue is the same as ours, AS will no longer be running and there will be errors in the Application event log which read the following

"

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File system error: Error opening file; \\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\CubeTest.0.db\Data Warehouse.8.cub.xml is not a disk file or file is not accessible..

"

We found upgrading to SP2 stopped this issue

|||

Hi,

Nice to see your reply.

The issue that I am actually facing is not related to the cube, since I am not able connect to the Analysis services from my local machine, so their's no chance for me to browse a cube.

Are you able to connect to the remote Analysis services using SQL Server management studio on your lcoal machine? I am not able to achieve this and getting the error here itself...

Regards,

Sumeet

|||

hi

did you check the security settings of the analysis server? (right click -> properties-> security)

add 'everyone' to it and try again for testing. i believe you should put your active directory user in it

for http connectivity, the default port number of analysis services is 2383

hope this helps

|||

Hi Christina,

I have checked with the security settings, and I have the active directory user added into it, also I tried adding 'everyone' to the list, but still I am getting the same error.

Regarding the port no, Can you please let me know where exactly we need to check with the port nos., since I havent made any changes to the port no of Analysis services.

Regards,

Sumeet

|||hi, i had the same problem on my local machine, where i was running sql server 2000 and sql2k service pack 3 installed. noone could browse my cubes. I read somewhere that when installing sp 3, it changes some user roles. i can give you a clue, i am not sure that it will work for you, but it worked for me:

i have reinstalled Analysis services once again on another computer which was running win xp sp2. After that i installed sql2k sp 4, before, and not sql2k sp 3. This made it work

good luck
|||

Hi Vali,

I am using SQL Server 2005 on both my remote and local server, Also I have SP1 installed on both of my machines and it doesnt works.

Later on I installed SP2 on my local machine and still I am getting the same error.

Regards,

Sumeet.

|||

In the SQL Server Surface Area Configuration tool the instance of Analysis Services might be set to Local Connections Only.

Can you even ping the remote machine from your local machine? Are you specifying a named instance when connecting?

|||

Hi John,

I have Local and Remote Connections selected in the SQL Server Surface Area Configuration,

Also I am able to connect to the Database engine from my local machine to the Remote server using a SQL Server Authentication, but in Analysis services, theirs no option to login using SQL Server Authentication, and using Windows Authentication I am getting the above mentioned error.

Regards,

Sumeet

|||

Have you resolved this issue? We are experiencing the same problem. We can connect to the Database Engine but are no longer able to connect remotely to the Analysis Services.

Thanks in advance.

Sarah Cameron - Incycle Software

|||

The port setting for Analysis Service is configured in the 'msmdredir.ini' file that should be located in your '\Program Files\Microsoft SQL Server\90\Shared\ASConfig' directory. You should see a section at the bottom of the configuration settings for your specific instance with the name and the port number:

<Instances>
<Instance>
<Name>SQL2005</Name>
<Port>2194</Port>
</Instance>
</Instances>

|||

Hi Sarah,

We actually are not yet able to find a fool proof solution for this, but found that it makes connection using the full doamin name. again this behavior is not consistent for each and every machine.

So still waiting for help..

Regards,

Sumeet

|||

Thanks for the response. We were able to get our connection back yesterday evening. I think it had to do with some domain name resolution and active directory account authentication issues. The weird thing was that it was only affecting the Analysis Services and we were still able to connect to the Database Services. Sorry I can't be of more help in detailing why it is working again.

__

Sarah Cameron - Incycle Software

Error connecting to remote SQL Server Analysis Services

Hi All,

I am trying to connect to the SQL Server Analysis Services on a remote server from my local machine, using SQL Server Management Studio.

I am able to connect to the SQL Server Database engine, but while connecting to the SQL Server Analysis services I get the following error :-

"Cannot connect to <IP Address>

A Connection cannot be made. Ensure that the server is running.

(Microsoft.AnalysisServices.AdomdClient)

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond(System)"

Things I have tried:-

- Ensured that the remote connection is enabled.

- Have SQL Server 2005 SP1 installed on the remote server.

- Tried installined SQL Server 2005 SP2 on my local machine, but same error.

I think some issue with the ports might exists, Dont have an exact idea of how to check on with the port settings.

Any kind of help will be appreciated on this.

Regards,

Sumeet:-)

We had similar problems when deploying cubes (although running Vanilla - not SP1)

We could replicate this problem by doing the following

1) Ensure all of the SQL Server Services (inc Analysis Services) are running

2) Browse a cube on your local machine

3) Rebuild this cube on your local machine

4) Check back on the remote server to see if AS is still running

If your issue is the same as ours, AS will no longer be running and there will be errors in the Application event log which read the following

"

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File system error: Error opening file; \\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\CubeTest.0.db\Data Warehouse.8.cub.xml is not a disk file or file is not accessible..

"

We found upgrading to SP2 stopped this issue

|||

Hi,

Nice to see your reply.

The issue that I am actually facing is not related to the cube, since I am not able connect to the Analysis services from my local machine, so their's no chance for me to browse a cube.

Are you able to connect to the remote Analysis services using SQL Server management studio on your lcoal machine? I am not able to achieve this and getting the error here itself...

Regards,

Sumeet

|||

hi

did you check the security settings of the analysis server? (right click -> properties-> security)

add 'everyone' to it and try again for testing. i believe you should put your active directory user in it

for http connectivity, the default port number of analysis services is 2383

hope this helps

|||

Hi Christina,

I have checked with the security settings, and I have the active directory user added into it, also I tried adding 'everyone' to the list, but still I am getting the same error.

Regarding the port no, Can you please let me know where exactly we need to check with the port nos., since I havent made any changes to the port no of Analysis services.

Regards,

Sumeet

|||hi, i had the same problem on my local machine, where i was running sql server 2000 and sql2k service pack 3 installed. noone could browse my cubes. I read somewhere that when installing sp 3, it changes some user roles. i can give you a clue, i am not sure that it will work for you, but it worked for me:

i have reinstalled Analysis services once again on another computer which was running win xp sp2. After that i installed sql2k sp 4, before, and not sql2k sp 3. This made it work

good luck
|||

Hi Vali,

I am using SQL Server 2005 on both my remote and local server, Also I have SP1 installed on both of my machines and it doesnt works.

Later on I installed SP2 on my local machine and still I am getting the same error.

Regards,

Sumeet.

|||

In the SQL Server Surface Area Configuration tool the instance of Analysis Services might be set to Local Connections Only.

Can you even ping the remote machine from your local machine? Are you specifying a named instance when connecting?

|||

Hi John,

I have Local and Remote Connections selected in the SQL Server Surface Area Configuration,

Also I am able to connect to the Database engine from my local machine to the Remote server using a SQL Server Authentication, but in Analysis services, theirs no option to login using SQL Server Authentication, and using Windows Authentication I am getting the above mentioned error.

Regards,

Sumeet

|||

Have you resolved this issue? We are experiencing the same problem. We can connect to the Database Engine but are no longer able to connect remotely to the Analysis Services.

Thanks in advance.

Sarah Cameron - Incycle Software

|||

The port setting for Analysis Service is configured in the 'msmdredir.ini' file that should be located in your '\Program Files\Microsoft SQL Server\90\Shared\ASConfig' directory. You should see a section at the bottom of the configuration settings for your specific instance with the name and the port number:

<Instances>
<Instance>
<Name>SQL2005</Name>
<Port>2194</Port>
</Instance>
</Instances>

|||

Hi Sarah,

We actually are not yet able to find a fool proof solution for this, but found that it makes connection using the full doamin name. again this behavior is not consistent for each and every machine.

So still waiting for help..

Regards,

Sumeet

|||

Thanks for the response. We were able to get our connection back yesterday evening. I think it had to do with some domain name resolution and active directory account authentication issues. The weird thing was that it was only affecting the Analysis Services and we were still able to connect to the Database Services. Sorry I can't be of more help in detailing why it is working again.

__

Sarah Cameron - Incycle Software

Error connecting to remote SQL Server Analysis Services

Hi All,

I am trying to connect to the SQL Server Analysis Services on a remote server from my local machine, using SQL Server Management Studio.

I am able to connect to the SQL Server Database engine, but while connecting to the SQL Server Analysis services I get the following error :-

"Cannot connect to <IP Address>

A Connection cannot be made. Ensure that the server is running.

(Microsoft.AnalysisServices.AdomdClient)

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond(System)"

Things I have tried:-

- Ensured that the remote connection is enabled.

- Have SQL Server 2005 SP1 installed on the remote server.

- Tried installined SQL Server 2005 SP2 on my local machine, but same error.

I think some issue with the ports might exists, Dont have an exact idea of how to check on with the port settings.

Any kind of help will be appreciated on this.

Regards,

Sumeet:-)

We had similar problems when deploying cubes (although running Vanilla - not SP1)

We could replicate this problem by doing the following

1) Ensure all of the SQL Server Services (inc Analysis Services) are running

2) Browse a cube on your local machine

3) Rebuild this cube on your local machine

4) Check back on the remote server to see if AS is still running

If your issue is the same as ours, AS will no longer be running and there will be errors in the Application event log which read the following

"

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File system error: Error opening file; \\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\CubeTest.0.db\Data Warehouse.8.cub.xml is not a disk file or file is not accessible..

"

We found upgrading to SP2 stopped this issue

|||

Hi,

Nice to see your reply.

The issue that I am actually facing is not related to the cube, since I am not able connect to the Analysis services from my local machine, so their's no chance for me to browse a cube.

Are you able to connect to the remote Analysis services using SQL Server management studio on your lcoal machine? I am not able to achieve this and getting the error here itself...

Regards,

Sumeet

|||

hi

did you check the security settings of the analysis server? (right click -> properties-> security)

add 'everyone' to it and try again for testing. i believe you should put your active directory user in it

for http connectivity, the default port number of analysis services is 2383

hope this helps

|||

Hi Christina,

I have checked with the security settings, and I have the active directory user added into it, also I tried adding 'everyone' to the list, but still I am getting the same error.

Regarding the port no, Can you please let me know where exactly we need to check with the port nos., since I havent made any changes to the port no of Analysis services.

Regards,

Sumeet

|||hi, i had the same problem on my local machine, where i was running sql server 2000 and sql2k service pack 3 installed. noone could browse my cubes. I read somewhere that when installing sp 3, it changes some user roles. i can give you a clue, i am not sure that it will work for you, but it worked for me:

i have reinstalled Analysis services once again on another computer which was running win xp sp2. After that i installed sql2k sp 4, before, and not sql2k sp 3. This made it work

good luck
|||

Hi Vali,

I am using SQL Server 2005 on both my remote and local server, Also I have SP1 installed on both of my machines and it doesnt works.

Later on I installed SP2 on my local machine and still I am getting the same error.

Regards,

Sumeet.

|||

In the SQL Server Surface Area Configuration tool the instance of Analysis Services might be set to Local Connections Only.

Can you even ping the remote machine from your local machine? Are you specifying a named instance when connecting?

|||

Hi John,

I have Local and Remote Connections selected in the SQL Server Surface Area Configuration,

Also I am able to connect to the Database engine from my local machine to the Remote server using a SQL Server Authentication, but in Analysis services, theirs no option to login using SQL Server Authentication, and using Windows Authentication I am getting the above mentioned error.

Regards,

Sumeet

|||

Have you resolved this issue? We are experiencing the same problem. We can connect to the Database Engine but are no longer able to connect remotely to the Analysis Services.

Thanks in advance.

Sarah Cameron - Incycle Software

|||

The port setting for Analysis Service is configured in the 'msmdredir.ini' file that should be located in your '\Program Files\Microsoft SQL Server\90\Shared\ASConfig' directory. You should see a section at the bottom of the configuration settings for your specific instance with the name and the port number:

<Instances>
<Instance>
<Name>SQL2005</Name>
<Port>2194</Port>
</Instance>
</Instances>

|||

Hi Sarah,

We actually are not yet able to find a fool proof solution for this, but found that it makes connection using the full doamin name. again this behavior is not consistent for each and every machine.

So still waiting for help..

Regards,

Sumeet

|||

Thanks for the response. We were able to get our connection back yesterday evening. I think it had to do with some domain name resolution and active directory account authentication issues. The weird thing was that it was only affecting the Analysis Services and we were still able to connect to the Database Services. Sorry I can't be of more help in detailing why it is working again.

__

Sarah Cameron - Incycle Software

error connecting to msde

Hi everybody this is my problem:
I've just installed MSDE2000 on my machine an it all works fine.
I'm able to create tables, storedprocedures whithin an access project, but i
cant' connect any client, i tried to use the ip address and also the
computer name but it doesnt' connect.
I receive a strange error:
(it's a free traslation from italian)
not supported interface
[dbbetlib][connectionOpen]Connect())] Sql server not exist o denied access
the parameters used for the installations were:
setup SAPWD="mypwd"
SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0
hi,
ciroteo wrote:
> Hi everybody this is my problem:
> I've just installed MSDE2000 on my machine an it all works fine.
> I'm able to create tables, storedprocedures whithin an access
> project, but i cant' connect any client, i tried to use the ip
> address and also the computer name but it doesnt' connect.
> I receive a strange error:
> (it's a free traslation from italian)
> not supported interface
> [dbbetlib][connectionOpen]Connect())] Sql server not exist o denied
> access
> the parameters used for the installations were:
> setup SAPWD="mypwd"
> SECURITYMODE=SQL
> DISABLENETWORKPROTOCOLS=0
please have a look at
http://support.microsoft.com/default...06&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
news:36bjn6F4vqnh0U1@.individual.net...
> hi,
> ciroteo wrote:
> please have a look at
> http://support.microsoft.com/default...06&Product=sql
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Ciao andrea grazie per la risposta, credo sia un problema di windows
firewall, perch avendo fatto un'altra installazione su un pc dove
disabilitato funziona tutto correttamente ...
bah!
ciao
|||hi,
ciroteo wrote:
> Ciao andrea grazie per la risposta, credo sia un problema di windows
> firewall, perch avendo fatto un'altra installazione su un pc dove
> disabilitato funziona tutto correttamente ...
> bah!
> ciao
as we are on an english NG, it's better to continue in english language (or
the better sort of... :D)
if it may depends on Windows Firewall, you can have a look
http://support.microsoft.com/default.aspx?kbid=841249
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
news:36bp7qF4v61k0U1@.individual.net...
> hi,
> ciroteo wrote:
> as we are on an english NG, it's better to continue in english language
> (or
> the better sort of... :D)
> if it may depends on Windows Firewall, you can have a look
> http://support.microsoft.com/default.aspx?kbid=841249
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Ok sorry! You are right.
I'll check it out, thank you so much.
|||"ciroteo" <ciroteo_chiocciola@.libero.it> ha scritto nel messaggio
news:ev03tTRCFHA.392@.TK2MSFTNGP14.phx.gbl...
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
> news:36bp7qF4v61k0U1@.individual.net...
>
> Ok sorry! You are right.
> I'll check it out, thank you so much.
>
>
If the pc isn't in the same domain as server, or it has a different
operative system (i.e. win98) is it possbile to receive a connection error?
|||hi,
ciroteo wrote:

> If the pc isn't in the same domain as server, or it has a different
> operative system (i.e. win98) is it possbile to receive a connection
> error?
as regard different OSs, this is not a problem at all, as all the related
traffic is handled by the MDAC stack and the network protocols subsystem...
as regard the domain... it depends... you can connect to web hosted servers,
which for sure are not on the same domain of the remote client, but the
connecting pc has to be recognized some way by the server... as trusted
authenticated connections are not available in this scenario, SQL Server
authenticated connection are usually used...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Error connecting to local SQL Server Express with SQL Server management Studio Express

I have SQL Server 2005 Express Edition installed on a Windows Server 2003 SP1 machine. I am trying to connect to the server on the local machine via shared memory with SQL Server Management Studio Express but I get the following error message:

TITLE: Connect to Server

Cannot connect to SERVER\SQLEXPRESS.

ADDITIONAL INFORMATION:

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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)

I have already enabled remote connections, TCP Ports, etc., and disabled the firewall, but since I am connecting from a local machine, that should not matter. I have uninstalled and reinstalled SQL Server Express with same issue occuring. SQLServer service Browser service is running.

Can anyone share some ideas on how to troubleshoot this connection issue? Could this be caused by some scurity settings or services not running in Windows Server 2003? Any help would be greatly appreciated.

Seems to be a strange issue.

Please check whether the Engine Services are running by using the Configuration Manager. Also check whether the account with which the service is running has a valid login in the Server.

Regards,

Rajesh

|||

After a good night sleep, I tried to connect to the database via Management Studio Express with the following Connection: .\SQLEXPRESS. This allowed me to connect to the database. Previously I had always connected with Server\SQLEXPRESS which produced the above error. After connecting to the datagase, the Registered Database window of Management Studio Express showed the database engine as server\sqlexpress, even though I could not connect to it using Server\SQLEXPRESS.

I felt happier I could connect, but I still couldn't understand why I can't connect using SERVER\SQLEXPRESS but have to use .\SQLEXPRESS. My real purpose of using SQL Server Express is to upgrade the back-end of an existing networked MS Access database application. When I went to SQL Server Configuration Manager to set up remote connections so I could connect from a client using a form of .\SQLEXPRESS or maybe IP ADDRESS/SQLEXPRESS, I noticed under SQL Native Client Configuration => Aliases, there was an alias configured for "SERVER\SQLEXPRESS". I don't know why this was there since I removed (via add/remove programs deleting the remaining Program Files => SQL SERVER directories) and reinstalled the application. I deleted this alias. After doing this I was able to connect to the Sever from Server Management Studio Express using SERVER\SQLEXPRESS. Finally I am able to progress to the task at hand of connecting to the database via Access Client, which leads to other problem I hope someone can help me with below.

In upsizing our Access application, we have decided only to upgrade the back-end but keep the front-end using Access and Jet connection to SQL Server via ODBC. We are currently using the "SQL Sever" ODBC driver that comes standard on Windows XP machine, configured at Administrative Tools => Data Sources (ODBC). I know this is not the best, but budget dictates (minimal to no changes in front-end Access) and it is a small application (~100MB size with one year of data). I am able to connect to the SQLEXPRESS database from ACCESS front-end at the client workstations, so I know the SQL SERVER Firewall settings are O.K. The problem I am having is that the connection drops out after 15 -30 minutes. I then can not reconnect to the database for some time. However, after additional amount of time, I am able to connect without changing anything in the configuration. We are using Windows Server 2003 R2 SP1 with Windows XP Pro clients. I don't think it is a network cabling problem because at the times when I can not connect to SQL SERVER, file and print sharing still work.

Does anybody have any hints on the easiest way to troubleshoot and fix this intermittant issue? Should I try to use the "SQL Native Client" ODBC Driver? Any suggestions are greatly appreciated.

|||Check any error or warning from SQL error logs & event viewer logs for the intermittent disconnection, also you can run a netmon trace to find where it is having problem. I guess as the clients can connect to SQL server now after your setup, its only on the network you should chekc.

Error attaching a database

Hello:
When attaching a database that was detached from another SQL Server instance
and copied over to this machine, I got the error message below:
Error 602: Could not find row in sysindexes for database ID 7, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can somebody guide me on the steps I have to follow to resolve this issue?
Thanks.
VenkiHi
On the original server, run DBCC CHECKDB as during the attach, SQL Server is
finding possible corruption in the DB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
> Hello:
> When attaching a database that was detached from another SQL Server
> instance
> and copied over to this machine, I got the error message below:
> Error 602: Could not find row in sysindexes for database ID 7, object ID
> 1,
> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> Can somebody guide me on the steps I have to follow to resolve this issue?
> Thanks.
> Venki|||Mike:
The source DB Server has been retired and not available.
Is there any other option available to get the database back online?
Please say yes!
venki
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> On the original server, run DBCC CHECKDB as during the attach, SQL Server
is
> finding possible corruption in the DB.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
>
>|||
>
What are the results of DBCC CHECKTABLE sysindexes?
Regards
JTC ^..^|||As I said, I don't have access to the source DB instance anymore. Since my
understanding was that DBCC should be run on the source DB instance, I have
not done it.
"JTC ^..^" wrote:

>
> What are the results of DBCC CHECKTABLE sysindexes?
> --
> Regards
> JTC ^..^
>|||Hi,
Try the below steps. If it fails restore from a good database backup.
Steps:
1. Create a new database with the same name and same MDF and LDF files
2. Stop sql server and rename the existing MDF to a new one and copy the
original MDF to this location and delete the LDF files.
3. Start SQL Server
4. Now your database will be marked suspect
5. Update the sysdatabases to update to Emergency mode. This will not use
LOG files in start up
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = "BadDbName"
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
6. Restart sql server. now the database will be in emergency mode
7. Create a new database and use DTS to copy the objects and data to new
database. You can use this new database.
Note:
If you have the backup file, it is always recommended to use the backup file
to restore the database. SO that data integrity will be maintained.
.
Thanks
Hari
SQL Server MVP
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...[vbcol=seagreen]
> As I said, I don't have access to the source DB instance anymore. Since my
> understanding was that DBCC should be run on the source DB instance, I
> have
> not done it.
> "JTC ^..^" wrote:
>|||Hari:
Thank you. When following the steps, when I tried to execute the statement,
Update sysdatabases set status = 32768 where name = "BadDbName"
I got an error, "Invalid column nam". However, I found what the dbid was for
that particular row and updated the row with that column in the Where clause
.
I will now try to see if the data is accessible.
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup fi
le
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>|||Hari:
Also, I executed the statements after I was logged into master database; I
could not log onto the badDBName.
I hope that was fine.
Venki
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup fi
le
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>|||Hari:
Yes, the database is in emergency mode.
When I tried to create a DTS job to import, it does not show up in the list
of databases available as a source.
Any ideas?
venki
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup fi
le
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>

Error attaching a database

Hello:
When attaching a database that was detached from another SQL Server instance
and copied over to this machine, I got the error message below:
Error 602: Could not find row in sysindexes for database ID 7, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can somebody guide me on the steps I have to follow to resolve this issue?
Thanks.
VenkiHi
On the original server, run DBCC CHECKDB as during the attach, SQL Server is
finding possible corruption in the DB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
> Hello:
> When attaching a database that was detached from another SQL Server
> instance
> and copied over to this machine, I got the error message below:
> Error 602: Could not find row in sysindexes for database ID 7, object ID
> 1,
> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> Can somebody guide me on the steps I have to follow to resolve this issue?
> Thanks.
> Venki|||Mike:
The source DB Server has been retired and not available.
Is there any other option available to get the database back online?
Please say yes!
venki
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> On the original server, run DBCC CHECKDB as during the attach, SQL Server is
> finding possible corruption in the DB.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
> > Hello:
> >
> > When attaching a database that was detached from another SQL Server
> > instance
> > and copied over to this machine, I got the error message below:
> >
> > Error 602: Could not find row in sysindexes for database ID 7, object ID
> > 1,
> > index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >
> > Can somebody guide me on the steps I have to follow to resolve this issue?
> >
> > Thanks.
> >
> > Venki
>
>|||>> Error 602: Could not find row in sysindexes for database ID 7, object
>> ID 1,
>> index ID 1. Run DBCC CHECKTABLE on sysindexes.
>> Can somebody guide me on the steps I have to follow to resolve this
>> issue?
>> Thanks.
>> Venki
>
What are the results of DBCC CHECKTABLE sysindexes?
--
Regards
JTC ^..^|||As I said, I don't have access to the source DB instance anymore. Since my
understanding was that DBCC should be run on the source DB instance, I have
not done it.
"JTC ^..^" wrote:
> >> Error 602: Could not find row in sysindexes for database ID 7, object
> >> ID 1,
> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >>
> >> Can somebody guide me on the steps I have to follow to resolve this
> >> issue?
> >>
> >> Thanks.
> >>
> >> Venki
> >
> >
> What are the results of DBCC CHECKTABLE sysindexes?
> --
> Regards
> JTC ^..^
>|||Hi,
Try the below steps. If it fails restore from a good database backup.
Steps:
1. Create a new database with the same name and same MDF and LDF files
2. Stop sql server and rename the existing MDF to a new one and copy the
original MDF to this location and delete the LDF files.
3. Start SQL Server
4. Now your database will be marked suspect
5. Update the sysdatabases to update to Emergency mode. This will not use
LOG files in start up
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = "BadDbName"
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
6. Restart sql server. now the database will be in emergency mode
7. Create a new database and use DTS to copy the objects and data to new
database. You can use this new database.
Note:
If you have the backup file, it is always recommended to use the backup file
to restore the database. SO that data integrity will be maintained.
.
Thanks
Hari
SQL Server MVP
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
> As I said, I don't have access to the source DB instance anymore. Since my
> understanding was that DBCC should be run on the source DB instance, I
> have
> not done it.
> "JTC ^..^" wrote:
>> >> Error 602: Could not find row in sysindexes for database ID 7, object
>> >> ID 1,
>> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
>> >>
>> >> Can somebody guide me on the steps I have to follow to resolve this
>> >> issue?
>> >>
>> >> Thanks.
>> >>
>> >> Venki
>> >
>> >
>> What are the results of DBCC CHECKTABLE sysindexes?
>> --
>> Regards
>> JTC ^..^|||Hari:
Thank you. When following the steps, when I tried to execute the statement,
Update sysdatabases set status = 32768 where name = "BadDbName"
I got an error, "Invalid column nam". However, I found what the dbid was for
that particular row and updated the row with that column in the Where clause.
I will now try to see if the data is accessible.
"Hari Prasad" wrote:
> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
> > As I said, I don't have access to the source DB instance anymore. Since my
> > understanding was that DBCC should be run on the source DB instance, I
> > have
> > not done it.
> >
> > "JTC ^..^" wrote:
> >
> >>
> >> >> Error 602: Could not find row in sysindexes for database ID 7, object
> >> >> ID 1,
> >> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >> >>
> >> >> Can somebody guide me on the steps I have to follow to resolve this
> >> >> issue?
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Venki
> >> >
> >> >
> >>
> >> What are the results of DBCC CHECKTABLE sysindexes?
> >>
> >> --
> >> Regards
> >> JTC ^..^
> >>
>
>|||Hari:
Also, I executed the statements after I was logged into master database; I
could not log onto the badDBName.
I hope that was fine.
Venki
"Hari Prasad" wrote:
> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
> > As I said, I don't have access to the source DB instance anymore. Since my
> > understanding was that DBCC should be run on the source DB instance, I
> > have
> > not done it.
> >
> > "JTC ^..^" wrote:
> >
> >>
> >> >> Error 602: Could not find row in sysindexes for database ID 7, object
> >> >> ID 1,
> >> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >> >>
> >> >> Can somebody guide me on the steps I have to follow to resolve this
> >> >> issue?
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Venki
> >> >
> >> >
> >>
> >> What are the results of DBCC CHECKTABLE sysindexes?
> >>
> >> --
> >> Regards
> >> JTC ^..^
> >>
>
>|||Hari:
Yes, the database is in emergency mode.
When I tried to create a DTS job to import, it does not show up in the list
of databases available as a source.
Any ideas?
venki
"Hari Prasad" wrote:
> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
> > As I said, I don't have access to the source DB instance anymore. Since my
> > understanding was that DBCC should be run on the source DB instance, I
> > have
> > not done it.
> >
> > "JTC ^..^" wrote:
> >
> >>
> >> >> Error 602: Could not find row in sysindexes for database ID 7, object
> >> >> ID 1,
> >> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >> >>
> >> >> Can somebody guide me on the steps I have to follow to resolve this
> >> >> issue?
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Venki
> >> >
> >> >
> >>
> >> What are the results of DBCC CHECKTABLE sysindexes?
> >>
> >> --
> >> Regards
> >> JTC ^..^
> >>
>
>

Error attaching a database

Hello:
When attaching a database that was detached from another SQL Server instance
and copied over to this machine, I got the error message below:
Error 602: Could not find row in sysindexes for database ID 7, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can somebody guide me on the steps I have to follow to resolve this issue?
Thanks.
Venki
Hi
On the original server, run DBCC CHECKDB as during the attach, SQL Server is
finding possible corruption in the DB.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
> Hello:
> When attaching a database that was detached from another SQL Server
> instance
> and copied over to this machine, I got the error message below:
> Error 602: Could not find row in sysindexes for database ID 7, object ID
> 1,
> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> Can somebody guide me on the steps I have to follow to resolve this issue?
> Thanks.
> Venki
|||Mike:
The source DB Server has been retired and not available.
Is there any other option available to get the database back online?
Please say yes!
venki
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> On the original server, run DBCC CHECKDB as during the attach, SQL Server is
> finding possible corruption in the DB.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
>
>
|||
>
What are the results of DBCC CHECKTABLE sysindexes?
Regards
JTC ^..^
|||As I said, I don't have access to the source DB instance anymore. Since my
understanding was that DBCC should be run on the source DB instance, I have
not done it.
"JTC ^..^" wrote:

>
> What are the results of DBCC CHECKTABLE sysindexes?
> --
> Regards
> JTC ^..^
>
|||Hi,
Try the below steps. If it fails restore from a good database backup.
Steps:
1. Create a new database with the same name and same MDF and LDF files
2. Stop sql server and rename the existing MDF to a new one and copy the
original MDF to this location and delete the LDF files.
3. Start SQL Server
4. Now your database will be marked suspect
5. Update the sysdatabases to update to Emergency mode. This will not use
LOG files in start up
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = "BadDbName"
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
6. Restart sql server. now the database will be in emergency mode
7. Create a new database and use DTS to copy the objects and data to new
database. You can use this new database.
Note:
If you have the backup file, it is always recommended to use the backup file
to restore the database. SO that data integrity will be maintained.
..
Thanks
Hari
SQL Server MVP
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...[vbcol=seagreen]
> As I said, I don't have access to the source DB instance anymore. Since my
> understanding was that DBCC should be run on the source DB instance, I
> have
> not done it.
> "JTC ^..^" wrote:
|||Hari:
Thank you. When following the steps, when I tried to execute the statement,
Update sysdatabases set status = 32768 where name = "BadDbName"
I got an error, "Invalid column nam". However, I found what the dbid was for
that particular row and updated the row with that column in the Where clause.
I will now try to see if the data is accessible.
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>
|||Hari:
Also, I executed the statements after I was logged into master database; I
could not log onto the badDBName.
I hope that was fine.
Venki
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>
|||Hari:
Yes, the database is in emergency mode.
When I tried to create a DTS job to import, it does not show up in the list
of databases available as a source.
Any ideas?
venki
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>

Error after Windows Update

Hi to all,
i have a win2k machine with sql server 7 on it, that is beeing fed with
data by another one, using replication.
The other machine is an sql server 2k and is the Publisher of the
replication
The machine with sql server 7, needed a windows update and so i did it this
morning.
After the reboot, the Publisher machine cannot push data to sql 7,and it
displays the
following error :
"Unable to find the remote agent on the remote server. Upgrade SQL server on
the Subscriber if version is <= 7.0 or rerun SQL Server setup on the remote
server. The step failed."
Agent is of cource running on the sql 7 machine.
Does anyone else has encountered this ?
Thanks a lot for any help,
anthony
what is the db compatibility mode on the subscriber in the subscription
database?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"objectref" <objectref@.mediatrel.com> wrote in message
news:uR4tgdV%23EHA.1260@.TK2MSFTNGP12.phx.gbl...
> Hi to all,
> i have a win2k machine with sql server 7 on it, that is beeing fed with
> data by another one, using replication.
> The other machine is an sql server 2k and is the Publisher of the
> replication
> The machine with sql server 7, needed a windows update and so i did it
this
> morning.
> After the reboot, the Publisher machine cannot push data to sql 7,and it
> displays the
> following error :
> "Unable to find the remote agent on the remote server. Upgrade SQL server
on
> the Subscriber if version is <= 7.0 or rerun SQL Server setup on the
remote
> server. The step failed."
> Agent is of cource running on the sql 7 machine.
>
> Does anyone else has encountered this ?
> Thanks a lot for any help,
> anthony
>