Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Monday, March 26, 2012

Moving a database SPID 51 error access error

Hi,
When I follow the instructions found here
http://support.microsoft.com/?id=224071 to move a (user) database I get an
error. This relates to unable to get exclusive access - there is only on
lock (spid 51) - can I just kill this?
sql 2000 - sp3 (so i am told) window 2000 sp4
Thanks
LeeOk, no worries - it was enterprise manager - rookie mistake
"Lee J" <ljackson_js@.hotmailREMOVESPAMMY.com> wrote in message
news:e9m0bs$7s1@.dispatch.concentric.net...
> Hi,
> When I follow the instructions found here
> http://support.microsoft.com/?id=224071 to move a (user) database I get an
> error. This relates to unable to get exclusive access - there is only on
> lock (spid 51) - can I just kill this?
> sql 2000 - sp3 (so i am told) window 2000 sp4
> Thanks
> Lee
>

Moving a database SPID 51 error access error

Hi,
When I follow the instructions found here
http://support.microsoft.com/?id=224071 to move a (user) database I get an
error. This relates to unable to get exclusive access - there is only on
lock (spid 51) - can I just kill this?
sql 2000 - sp3 (so i am told) window 2000 sp4
Thanks
LeeOk, no worries - it was enterprise manager - rookie mistake
"Lee J" <ljackson_js@.hotmailREMOVESPAMMY.com> wrote in message
news:e9m0bs$7s1@.dispatch.concentric.net...
> Hi,
> When I follow the instructions found here
> http://support.microsoft.com/?id=224071 to move a (user) database I get an
> error. This relates to unable to get exclusive access - there is only on
> lock (spid 51) - can I just kill this?
> sql 2000 - sp3 (so i am told) window 2000 sp4
> Thanks
> Lee
>

Friday, March 23, 2012

Moved master db and now cannot start SQL

After changing the startup parameters and moving the database we are unable
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.
HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.
|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/de...servr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:

> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.
|||Error 5 is access denied. Make sure that the SQL Server service account has permissions to the file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.
|||Moved it based on Microsoft articel changed startup parameters and only moved
the master.mdf so I only changed that parameter.
"doller" wrote:

> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
>
|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters back
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/de...servr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
[vbcol=seagreen]
> Used this article to move the database also tried to start it from a command
> prompt and would not start. Also tried to change the startup parameters back
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and tried
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved[vbcol=seagreen]
> the master.mdf so I only changed that parameter.
> "doller" wrote:
unable[vbcol=seagreen]
log is[vbcol=seagreen]
|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...[vbcol=seagreen]
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:

Moved master db and now cannot start SQL

After changing the startup parameters and moving the database we are unable
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/d...>
rvr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:

> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Error 5 is access denied. Make sure that the SQL Server service account has
permissions to the file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Moved it based on Microsoft articel changed startup parameters and only move
d
the master.mdf so I only changed that parameter.
"doller" wrote:

> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
>|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters bac
k
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/d...
servr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
>|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
[vbcol=seagreen]
> Used this article to move the database also tried to start it from a comma
nd
> prompt and would not start. Also tried to change the startup parameters b
ack
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and trie
d
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
>|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved[vbcol=seagreen]
> the master.mdf so I only changed that parameter.
> "doller" wrote:
>
unable[vbcol=seagreen]
log is[vbcol=seagreen]|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...[vbcol=seagreen]
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:
>

Moved master db and now cannot start SQL

After changing the startup parameters and moving the database we are unable
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Error 5 is access denied. Make sure that the SQL Server service account has permissions to the file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Moved it based on Microsoft articel changed startup parameters and only moved
the master.mdf so I only changed that parameter.
"doller" wrote:
> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
> > After changing the startup parameters and moving the database we are unable
> > to start SQL. The error message we are getting in the application log is
> > that the initconfig: (error 5) access denied to g:\sqldata.
>|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters back
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
> > After changing the startup parameters and moving the database we are unable
> > to start SQL. The error message we are getting in the application log is
> > that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
> Used this article to move the database also tried to start it from a command
> prompt and would not start. Also tried to change the startup parameters back
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and tried
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
> > Hi
> >
> > This article descibes how to move your master database
> > http://support.microsoft.com/kb/224071/EN-US/
> >
> > You may want to try starting SQL Server from the command prompt
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
> > with the correct parameters (possibly with -f also!) and also making sure
> > that the permissions for the directories being used are correct.
> >
> > You can not use a mapped network drive for your database files.
> >
> > John
> >
> > "Ray Skweres" wrote:
> >
> > > After changing the startup parameters and moving the database we are unable
> > > to start SQL. The error message we are getting in the application log is
> > > that the initconfig: (error 5) access denied to g:\sqldata.|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved
> the master.mdf so I only changed that parameter.
> "doller" wrote:
> > HI,
> > How u moved the database and what parameter u have changed.
> >
> > from
> > killer
> >
> >
> > Ray Skweres wrote:
> > > After changing the startup parameters and moving the database we are
unable
> > > to start SQL. The error message we are getting in the application
log is
> > > that the initconfig: (error 5) access denied to g:\sqldata.
> >
> >|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:
>> Used this article to move the database also tried to start it from a
>> command
>> prompt and would not start. Also tried to change the startup parameters
>> back
>> though command prompt and did not work. I am not using a mapped network
>> drive. Permissions are fine on the file. Even went into registry and
>> tried
>> to change and then start sql still did not start and then when I went
>> back
>> into the registry and it was back to the old setting.
>> "John Bell" wrote:
>> > Hi
>> >
>> > This article descibes how to move your master database
>> > http://support.microsoft.com/kb/224071/EN-US/
>> >
>> > You may want to try starting SQL Server from the command prompt
>> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
>> > with the correct parameters (possibly with -f also!) and also making
>> > sure
>> > that the permissions for the directories being used are correct.
>> >
>> > You can not use a mapped network drive for your database files.
>> >
>> > John
>> >
>> > "Ray Skweres" wrote:
>> >
>> > > After changing the startup parameters and moving the database we are
>> > > unable
>> > > to start SQL. The error message we are getting in the application
>> > > log is
>> > > that the initconfig: (error 5) access denied to g:\sqldata.

Wednesday, March 21, 2012

Move/copy Data base failed from sql 2000 to sql 2005

When I try to copy or move a DB from a sql server 2000 to a sql srvr 2005 using sql 2005 "copy database wizard", I get an error in the SQL Server Agent Job execution.

The two databases are on different PC, and same problem occurs if I try to copy/move a DB from sql 2005 to an other sql 2005 server.

Wizard does not fail if the copy is done on the same machine.

Following is the log generated:


- Add log for package (Success)

- Add task for transferring database objects (Success)

- Create package (Success)

- Start SQL Server Agent Job (Success)

- Execute SQL Server Agent Job (Error)
Messages
* The job failed. Check the event log on the destination server for details. (Copy Database Wizard)

Any Idea to help?

thanks

The easiest way to move a database from SQL Server 2000 to SQL Server 2005 is to detach the database files from SQL Server 2000 and attach them to your SQL Server 2005 instance. To do that:

1) In SQL Server 2000, make a complete backup of your database (better safe than sorry!)

2) Detach the database from SQL Server 2000. You can use SQL Server Management Studio 2005 to do this if you like. Start SSMS, connect to your SQL Server 2000 server, expand the databases folder, right click on your database and select "Tasks > Detach" from the context menu.

3) Copy all the .mdf, .ldf, and .ndf files for your database to a location accessible to your SQL Server 2005 instance. You can use Windows Explorer to do this.

4) Attach the copied files to your SQL Server 2005 instance. You can do this SSMS as well. Connect to your SQL Server 2005 instance, right click on the databases folder and select "Attach" in the context menu. In the Attach Database dialog, you just need to add the .mdf file - the dialog will find the other files if you have copied all of them to the same directory - and click OK.

You can also move your database by restoring a full backup of the SQL Server 2000 database on the SQL Server 2005 server.

Once your database has been attached (or restored), make sure it has a valid owner. If the SQL Server 2000 database was owned by a SQL Authentication login, the new server won't know about the owner on the old server. You can change the database owner to a login the SQL Server 2005 server knows about using the database properties dialog in SSMS - just right click on the new database and select properties. The owner is defined on the "Files" page of the dialog.

Hope this helps,
Steve

sql

Move/copy Data base failed from sql 2000 to sql 2005

When I try to copy or move a DB from a sql server 2000 to a sql srvr 2005 using sql 2005 "copy database wizard", I get an error in the SQL Server Agent Job execution.

The two databases are on different PC, and same problem occurs if I try to copy/move a DB from sql 2005 to an other sql 2005 server.

Wizard does not fail if the copy is done on the same machine.

Following is the log generated:


- Add log for package (Success)

- Add task for transferring database objects (Success)

- Create package (Success)

- Start SQL Server Agent Job (Success)

- Execute SQL Server Agent Job (Error)
Messages
* The job failed. Check the event log on the destination server for details. (Copy Database Wizard)

Any Idea to help?

thanks

The easiest way to move a database from SQL Server 2000 to SQL Server 2005 is to detach the database files from SQL Server 2000 and attach them to your SQL Server 2005 instance. To do that:

1) In SQL Server 2000, make a complete backup of your database (better safe than sorry!)

2) Detach the database from SQL Server 2000. You can use SQL Server Management Studio 2005 to do this if you like. Start SSMS, connect to your SQL Server 2000 server, expand the databases folder, right click on your database and select "Tasks > Detach" from the context menu.

3) Copy all the .mdf, .ldf, and .ndf files for your database to a location accessible to your SQL Server 2005 instance. You can use Windows Explorer to do this.

4) Attach the copied files to your SQL Server 2005 instance. You can do this SSMS as well. Connect to your SQL Server 2005 instance, right click on the databases folder and select "Attach" in the context menu. In the Attach Database dialog, you just need to add the .mdf file - the dialog will find the other files if you have copied all of them to the same directory - and click OK.

You can also move your database by restoring a full backup of the SQL Server 2000 database on the SQL Server 2005 server.

Once your database has been attached (or restored), make sure it has a valid owner. If the SQL Server 2000 database was owned by a SQL Authentication login, the new server won't know about the owner on the old server. You can change the database owner to a login the SQL Server 2005 server knows about using the database properties dialog in SSMS - just right click on the new database and select properties. The owner is defined on the "Files" page of the dialog.

Hope this helps,
Steve

Friday, March 9, 2012

move msdb

I am getting following error when moving msdb database to different drive.

“SQL SERVER is in SINGLE USER MODE and only one administrator can connect”

I followed steps menthioned in http://support.microsoft.com/kb/224071

Also, it was mentioned that even object browser is also one connection- http://deepakinsql.blogspot.com/2007/08/moving-system-databases-in-sql-2005.html , so I closed that but didn't work.

I am using SQL 2005 Enterprise non clustered with no service pack on windows 2003 server

Did anybody faced this problem and found any solution.

thanks,

Hi
This will help.
http://support.microsoft.com/kb/224071#
|||

I used the same KB article but still getting the error.

Thanks,

|||May be this help?
Stop the SQL Server Agent service before connecting to an instance of SQL Server in single-user mode; otherwise, the SQL Server Agent service uses the connection, thereby blocking it.
|||

After adding ;–c;-m;-T3608 at the end of starup, restart came with SQL Agent not running. So SQL Agent is not running . Moreover I stopped other services like sql browser , Integration service , Analysis service to make sure nobody is connecting. Can I see who is using administrator connection to figure out where it is getting used?

Thanks,

|||STOP SQL SERVICES.
START SQL FROM command prompt

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn>sqlservr.exe -m
Connect using SQL Management Studio.
|||I have tested above method and it is working on my SQL server 2005 developer edition.

Move Logs to another drive

Does anyone know how to move the SQL logs to another drive. I want to
seperate these from the database for redundancy and performance
I get an error stating the log cannot be moved after the database has been
create.
SQL 2000 STD
Thanks in advance for your helpSee sp_detach/ sp_attach in BOL.
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help|||"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
sp_attach_db and sp_detach_db can help you here.
Alternately, you could issue a RESTORE DATABASE command specify the new
location using the MOVE TO option.
Rick Sawtell
MCT, MCSD, MCDBA

Move Logs to another drive

Does anyone know how to move the SQL logs to another drive. I want to
seperate these from the database for redundancy and performance
I get an error stating the log cannot be moved after the database has been
create.
SQL 2000 STD
Thanks in advance for your help
See sp_detach/ sp_attach in BOL.
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
|||"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
sp_attach_db and sp_detach_db can help you here.
Alternately, you could issue a RESTORE DATABASE command specify the new
location using the MOVE TO option.
Rick Sawtell
MCT, MCSD, MCDBA

Move Logs to another drive

Does anyone know how to move the SQL logs to another drive. I want to
seperate these from the database for redundancy and performance
I get an error stating the log cannot be moved after the database has been
create.
SQL 2000 STD
Thanks in advance for your helpSee sp_detach/ sp_attach in BOL.
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help|||"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:D14C7D37-BCF5-4D79-ACCE-95C1F75C4783@.microsoft.com...
> Does anyone know how to move the SQL logs to another drive. I want to
> seperate these from the database for redundancy and performance
> I get an error stating the log cannot be moved after the database has been
> create.
> SQL 2000 STD
> Thanks in advance for your help
sp_attach_db and sp_detach_db can help you here.
Alternately, you could issue a RESTORE DATABASE command specify the new
location using the MOVE TO option.
Rick Sawtell
MCT, MCSD, MCDBA

move log file to diff location

Hi,
I got this error when I move the log file to a diff location in the cluster
environment.
Any ideas and solution?
Thanks
Msg 5184, Level 16, State 2, Line 1
Cannot use file 'T:\Logs\myrpdLog.ldf' for clustered server. Only
formatted files on which the cluster resource of the server has a dependency
can be used.
Please don't multi-post. See my answer in .clustering.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"mecn" <mecn2002@.yahoo.com> wrote in message
news:%23lg8C4luHHA.1768@.TK2MSFTNGP04.phx.gbl...
Hi,
I got this error when I move the log file to a diff location in the cluster
environment.
Any ideas and solution?
Thanks
Msg 5184, Level 16, State 2, Line 1
Cannot use file 'T:\Logs\myrpdLog.ldf' for clustered server. Only
formatted files on which the cluster resource of the server has a dependency
can be used.

move log file to diff location

Hi,
I got this error when I move the log file to a diff location in the cluster
environment.
Any ideas and solution?
Thanks
Msg 5184, Level 16, State 2, Line 1
Cannot use file 'T:\Logs\myrpdLog.ldf' for clustered server. Only
formatted files on which the cluster resource of the server has a dependency
can be used.Please don't multi-post. See my answer in .clustering.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"mecn" <mecn2002@.yahoo.com> wrote in message
news:%23lg8C4luHHA.1768@.TK2MSFTNGP04.phx.gbl...
Hi,
I got this error when I move the log file to a diff location in the cluster
environment.
Any ideas and solution?
Thanks
Msg 5184, Level 16, State 2, Line 1
Cannot use file 'T:\Logs\myrpdLog.ldf' for clustered server. Only
formatted files on which the cluster resource of the server has a dependency
can be used.

move log file to diff location

Hi,
I got this error when I move the log file to a diff location in the cluster
environment.
Any ideas and solution?
Thanks
Msg 5184, Level 16, State 2, Line 1
Cannot use file 'T:\Logs\myrpdLog.ldf' for clustered server. Only
formatted files on which the cluster resource of the server has a dependency
can be used.Please don't multi-post. See my answer in .clustering.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"mecn" <mecn2002@.yahoo.com> wrote in message
news:%23lg8C4luHHA.1768@.TK2MSFTNGP04.phx.gbl...
Hi,
I got this error when I move the log file to a diff location in the cluster
environment.
Any ideas and solution?
Thanks
Msg 5184, Level 16, State 2, Line 1
Cannot use file 'T:\Logs\myrpdLog.ldf' for clustered server. Only
formatted files on which the cluster resource of the server has a dependency
can be used.

Monday, February 20, 2012

MS Reporting Services Error

I have MS RS installed on the W2K3 EE member server, SQL 2000 SP4 and IIS 6
are also installed on the same machine.
For some reason when I connect to:
http://<servername>/reports
or
http://<IP>/reports
or
http://<Localhost>/reports
I'm showed the error message:
"The underlying connection was closed: Unable to connect to the remote
server."
From checking the web and this newsgroup it is clear that there is very
little information about this which leads me to believe this must be some
obvious setting that most people are aware of. Can anyone provide assistance?
Thanks in Advance,
CRHave you checked the event logs on the server?
One other things that come to mind is connection timeouts.
Check the newsgroup on how to change this.
I did have an issue installing RS on a domain controller basically it
didn't set up the ASPNet user properly but I was generally getting
permission denied problems with this one.
Chris
CR wrote:
> I have MS RS installed on the W2K3 EE member server, SQL 2000 SP4 and
> IIS 6 are also installed on the same machine.
> For some reason when I connect to:
> http://<servername>/reports
> or
> http://<IP>/reports
> or
> http://<Localhost>/reports
> I'm showed the error message:
> "The underlying connection was closed: Unable to connect to the
> remote server."
> From checking the web and this newsgroup it is clear that there is
> very little information about this which leads me to believe this
> must be some obvious setting that most people are aware of. Can
> anyone provide assistance?
> Thanks in Advance,
> CR

MS Reporting Services 2000 Error ?

hi

when i try to use Reporting Services to render a report from aspx page

(web app) (vb.net) by usingReportingServices.dll (by add referennces)

i am not using (web referennces)

i get this erorr :

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

System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\NETWORK SERVICE' are insufficient for performing this operation. > Microsoft.ReportingServices.Diagnostics.Utilities.RSException .

note:

=====

- i have windows 2003 server ent.

- sql 2000 sp3 .

- MS Reporting Services 2000 sp2 .

- i am login as administrator .

pls tell me what i can do ?

thank you all

Hi,

as you did not post any code, I can give you a common suggestion. If you use impersonation, you will have to use the credentials of the actual user and add it to the instantiated proxy of the webservice. This will make the call to the webservice under the credentials and the permissions of the impersonated user.

HTH, Jens K. Suessmeyer.


http://www.sqlserver2005.de

|||Correct me if I'm wrong, but if you don't do this then it uses the identity of the app pool under which the website runs which by default is network service for the default app pool|||yep.