Can''t configure Log Shipping on a workgroup network

I have a WORKGROUP network with 2 SQL Server 2005 servers. I want to configure for log shipping.

When I try and set up the 'Secondary Database Settings', and try and run the process, it gets an error saying it cannot access the backup file (the secondary cannot access the backup file on the primary). The file is there. It is shared. I have created local accounts on both machines called 'SyncAccount', and have given full control over the shared directory (on the primary) and local directory on the secondary. I have chaged the SQL Agent to use the local account.

TITLE: Microsoft SQL Server Management Studio

SQL Server Management Studio restore database 'ISC'

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (SqlManagerUI)

Cannot open backup device '\\FAtBOY\ISC\ISC.bak'. Operating system error 5(Access is denied.).
RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3201)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=3201&LinkId=20476

I have tested access for the created user by doing a "runas" from the command prompt.

I have invested hours in this. I have found several relevent artcles, but have not found the answer.

What is wrong with this thing?

Is this login part of sql sysadmin group? What account is used to start up sqlserver service? Does this account have permission to write to the shared folder? What's about the sqlagent service?

|||

It has been a while since I made this post, but I am still having the problem.

Is this login part of sql sysadmin group? I have given admin provlidges to thie user.

What account is used to start up sqlserver service? I created a new "syncaccount" as assiged it to the sql agent. It has admin rights.

Does this account have permission to write to the shared folder? Yes. I tested this by linking to the shared folder using "connect as".

What's about the sqlagent service? Explained above.

I think there is something wrong with the server. Perhaps my configuration is the issue. Two servers (not on a domain) in a workgroup.

|||

When you operate in a workgroup, network permission is nothing more than Windows impersonation. For things to work, the account must be created on both workgroup nodes and has the same password. Logshipping is nothing more than a whole bunch of sql jobs that get executed under a security context (i.e. sqlagent or the proxy). If your job is owned by a sysadmin, the job will get executed under sqlagent service account to access network resources. If it's a non-sysadmin, it will be under the proxy account.

Take a look at xp_cmdshell in book online. There is a link to how to setup/configure the proxy account.

To see if the NT accout is valid, try backup a database to the network share. Resolve this before you attempt to solve the logshipping issue.

Can't configure Log Shipping on a workgroup network

I have a WORKGROUP network with 2 SQL Server 2005 servers. I want to configure for log shipping.

When I try and set up the 'Secondary Database Settings', and try and run the process, it gets an error saying it cannot access the backup file (the secondary cannot access the backup file on the primary). The file is there. It is shared. I have created local accounts on both machines called 'SyncAccount', and have given full control over the shared directory (on the primary) and local directory on the secondary. I have chaged the SQL Agent to use the local account.

TITLE: Microsoft SQL Server Management Studio

SQL Server Management Studio restore database 'ISC'

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (SqlManagerUI)

Cannot open backup device '\\FAtBOY\ISC\ISC.bak'. Operating system error 5(Access is denied.).
RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3201)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=3201&LinkId=20476

I have tested access for the created user by doing a "runas" from the command prompt.

I have invested hours in this. I have found several relevent artcles, but have not found the answer.

What is wrong with this thing?

Is this login part of sql sysadmin group? What account is used to start up sqlserver service? Does this account have permission to write to the shared folder? What's about the sqlagent service?

|||

It has been a while since I made this post, but I am still having the problem.

Is this login part of sql sysadmin group? I have given admin provlidges to thie user.

What account is used to start up sqlserver service? I created a new "syncaccount" as assiged it to the sql agent. It has admin rights.

Does this account have permission to write to the shared folder? Yes. I tested this by linking to the shared folder using "connect as".

What's about the sqlagent service? Explained above.

I think there is something wrong with the server. Perhaps my configuration is the issue. Two servers (not on a domain) in a workgroup.

|||

When you operate in a workgroup, network permission is nothing more than Windows impersonation. For things to work, the account must be created on both workgroup nodes and has the same password. Logshipping is nothing more than a whole bunch of sql jobs that get executed under a security context (i.e. sqlagent or the proxy). If your job is owned by a sysadmin, the job will get executed under sqlagent service account to access network resources. If it's a non-sysadmin, it will be under the proxy account.

Take a look at xp_cmdshell in book online. There is a link to how to setup/configure the proxy account.

To see if the NT accout is valid, try backup a database to the network share. Resolve this before you attempt to solve the logshipping issue.

Can't configure Log Shipping on a workgroup network

I have a WORKGROUP network with 2 SQL Server 2005 servers. I want to configure for log shipping.

When I try and set up the 'Secondary Database Settings', and try and run the process, it gets an error saying it cannot access the backup file (the secondary cannot access the backup file on the primary). The file is there. It is shared. I have created local accounts on both machines called 'SyncAccount', and have given full control over the shared directory (on the primary) and local directory on the secondary. I have chaged the SQL Agent to use the local account.

TITLE: Microsoft SQL Server Management Studio

SQL Server Management Studio restore database 'ISC'

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (SqlManagerUI)

Cannot open backup device '\\FAtBOY\ISC\ISC.bak'. Operating system error 5(Access is denied.).
RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3201)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=3201&LinkId=20476

I have tested access for the created user by doing a "runas" from the command prompt.

I have invested hours in this. I have found several relevent artcles, but have not found the answer.

What is wrong with this thing?

Is this login part of sql sysadmin group? What account is used to start up sqlserver service? Does this account have permission to write to the shared folder? What's about the sqlagent service?

|||

It has been a while since I made this post, but I am still having the problem.

Is this login part of sql sysadmin group? I have given admin provlidges to thie user.

What account is used to start up sqlserver service? I created a new "syncaccount" as assiged it to the sql agent. It has admin rights.

Does this account have permission to write to the shared folder? Yes. I tested this by linking to the shared folder using "connect as".

What's about the sqlagent service? Explained above.

I think there is something wrong with the server. Perhaps my configuration is the issue. Two servers (not on a domain) in a workgroup.

|||

When you operate in a workgroup, network permission is nothing more than Windows impersonation. For things to work, the account must be created on both workgroup nodes and has the same password. Logshipping is nothing more than a whole bunch of sql jobs that get executed under a security context (i.e. sqlagent or the proxy). If your job is owned by a sysadmin, the job will get executed under sqlagent service account to access network resources. If it's a non-sysadmin, it will be under the proxy account.

Take a look at xp_cmdshell in book online. There is a link to how to setup/configure the proxy account.

To see if the NT accout is valid, try backup a database to the network share. Resolve this before you attempt to solve the logshipping issue.

Can't access Report Manager on another computer

I have Reporting Services for SQL Server 2005 (beta 2) installed on 2
Windows XP Pro boxes that are part of the same Windows workgroup. I
need to deploy reports from one box to the other, but I can't see the
Report Manager on the opposing machine, even though I can see it
locally on the respective machine.
I know we're talking beta here, but I need to give a coworker a way to
have access to all our reports on his laptop. Since Reporting
Services for SQL 2000 requires a server, the only way he and I can
have the reports locally on Win XP Pro is via Reporting Services 2005.
Any idea how I can get access to his Report Manager? When I go to
Report Manager on my machine, I go to
"http://MyComputerName/Reports$2005", which works fine. When I'm on
his machine and go to Report Manager, I go to
"http://HisComputerName/Reports$2005" and that works fine. When I try
the same path from my computer, I get a "page not found" error.
I am a local administrator on his machine and have full directory
access (e.g. //ComputerName/C$). I checked the IIS permissions for
his Reports$2005 virtual directory and the Directory Security
authentication method is set to Integrated Windows authentication. I
tried Anonymous access, but that didn't help. Any ideas?I figured it out. Service Pack 2 for Win XP Pro was installed on the
remote machine, so the firewall was preventing me from getting to the
Report Server. I simply disabled the firewall temporarily so I could
deploy my reports. I didn't know how to configure the firewall to
allow me to access the computer, so I found that disabling the
firewall was the best method.
Anyway, that solved my problem.
steve.pantazis@.gmail.com (Steve Pantazis) wrote in message news:<437b6286.0409250937.485cb6ac@.posting.google.com>...
> I have Reporting Services for SQL Server 2005 (beta 2) installed on 2
> Windows XP Pro boxes that are part of the same Windows workgroup. I
> need to deploy reports from one box to the other, but I can't see the
> Report Manager on the opposing machine, even though I can see it
> locally on the respective machine.
> I know we're talking beta here, but I need to give a coworker a way to
> have access to all our reports on his laptop. Since Reporting
> Services for SQL 2000 requires a server, the only way he and I can
> have the reports locally on Win XP Pro is via Reporting Services 2005.
> Any idea how I can get access to his Report Manager? When I go to
> Report Manager on my machine, I go to
> "http://MyComputerName/Reports$2005", which works fine. When I'm on
> his machine and go to Report Manager, I go to
> "http://HisComputerName/Reports$2005" and that works fine. When I try
> the same path from my computer, I get a "page not found" error.
> I am a local administrator on his machine and have full directory
> access (e.g. //ComputerName/C$). I checked the IIS permissions for
> his Reports$2005 virtual directory and the Directory Security
> authentication method is set to Integrated Windows authentication. I
> tried Anonymous access, but that didn't help. Any ideas?sql

Cannot stop or start SQL server from SQLEM

Hi,
Merry Christmas to Everyone.
We have a SQL2k server that is not in any domain (in a
workgroup). I registered it in the Enterprise Manager on
my workstation with the sa account. However, I can do
anything but stop or start the SQL server and server
agent. Here is the error message:
An error 5 - (Access is denied) occurred while performing
this service operation on the SQLServerAgent service.
Any suggestions?
Thanks.
David WangServices are an OS thing, not an SQL thing. Log in as
admin.
>--Original Message--
>Hi,
>Merry Christmas to Everyone.
>We have a SQL2k server that is not in any domain (in a
>workgroup). I registered it in the Enterprise Manager on
>my workstation with the sa account. However, I can do
>anything but stop or start the SQL server and server
>agent. Here is the error message:
>An error 5 - (Access is denied) occurred while performing
>this service operation on the SQLServerAgent service.
>Any suggestions?
>Thanks.
>David Wang
>.
>|||Yes, you are right. I have no problem to do this if I log
in from the local server. I am trying to do this from a
remote machine. I thought the sa account could impersonate
the local system admin role.
Thanks.
>--Original Message--
>Services are an OS thing, not an SQL thing. Log in as
>admin.
>>--Original Message--
>>Hi,
>>Merry Christmas to Everyone.
>>We have a SQL2k server that is not in any domain (in a
>>workgroup). I registered it in the Enterprise Manager on
>>my workstation with the sa account. However, I can do
>>anything but stop or start the SQL server and server
>>agent. Here is the error message:
>>An error 5 - (Access is denied) occurred while
performing
>>this service operation on the SQLServerAgent service.
>>Any suggestions?
>>Thanks.
>>David Wang
>>.
>.
>|||sa is not an administrator to the operating system.

Cannot start your application. The workgroup information file is missing or opened exclusively b

hye everyone,
when i browse my web application the eror as below display..
what should i do..
any suggestion or tips...

"Cannot start your application. The workgroup information file is missing or opened exclusively by another user.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.OleDb.OleDbException: Cannot start your application. The workgroup information file is missing or opened exclusively by another user. "

thanks in advance..
thank you very much..

That is not a SQL Server problem as you aure using obviously MS Access, you better post your question to one of the Access forums in the public newgroup network. But, as far as I can remember from my old Access days, you will have to delete the lock file which is located in the same folder as the workgroup file which contains the security informa′tion.

Jens K. Suessmeyer

http://www.sqlserver2005.de