July 24, 2004 at 8:42 pm
Hi
I have a WORKGROUP setup with two machines, machine A and Machine B. In machine A I have adatbase which I would like to backup such that the backup file with the .bak extension be created in machine B. When I try to create new backup media device and point to a folder in another machine I am prompted ONLY with GUI corresponfing to the directory of machine A, whereas I'm interested in the directory of machine B, just as is evident when browsing through 'my network places' from windows explorer will do so. I did some research, and I undrestand that I need to change the user name in the logon tabe of the mssqlserver service in the control panel|administartion|services window. I went ahead and changed the seettings from localsystem to administartor plus the password of machine B (the external machine where I want the backup file to reside), but when I press OK to confirm the change, I get the following error message: "the account name is invalid or does not exist, or the passowrd is invalid for the account name specified." I tried to place only the word administrator and leaving the password field blank, so as to match perhaps the passowrd for machine A, but that did not work either.
Note: when I log through the workgroup setup to machine A from any other machine, I just need to put the word administrator without the password inorder to browse the directory of machine A. To do the same with respect to machine B, I type the word administartor as well as the password in the password field.
Where did I gow wrong? Do i have to create some other account and type it in the logon tabe of the mssqlserver services form? any help will be much appreciated
thabk you in advance
avi
July 25, 2004 at 12:10 am
The SQL Server Service on machine 'A' must run as a user account on machine 'A' - this would be administrator + no password. BUT, it then cannot connect to machine B to do your backup as it would be connecting with "administrator"/no password. The easiest solution is to make a user on each machine called SQL with THE SAME PASSWORD on both machines. You can then give this user the required permissions (if you don't care for security then make it an administrator and be done with it). Thus SQL Server will run as the user "SQL" and can successfully connect to the other machine as "SQL".
Note that you should probably use Enterprise Manager to change the startup account rather than the Services applet (the service user requires a SQL Server account - that's why if you leave BUILTIN\ADMINISTRATORS as a group in SQL Server and make "SQL" an administrator you will have no issues at all and can use the services applet).
That should do the trick for you
July 25, 2004 at 12:55 am
hello ianyates,
thank you for your prompt reply. I understood the idea behind your helpful suggestion, but I'm pretty mixed up when it comes to implementing the modification of accounts. I have to windows server 2000, which, as far as i can tell, do not have the active directory installed/enabled. From the little that I understand, I need to create identical account+password in bpth machines with respect to the operating system, and in order to do this I need to get into the all complicated idea of active directory and all the accompanied terminilogy which is rather foreign to me. Once I create the account in both machines, I need to associate the account with the priviliges of administartor. When it comes to being practical I am lost, so if you can please give me a little guidance and tell me if indeed active directory plays a role in the process, and if so, how do I go about adding the account.
once again, thank you for your help
avi
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply