Tuesday, March 27, 2012
Basic question
Service is working, but i can't connect my project with serwer. ASP configuration tool(security) can't connect. Error message doesn't show any reason.
Server menager can connect normally.
Please help
what is the error message?sql
Basic question
Service is working, but i can't connect my project with serwer. ASP configuration tool(security) can't connect. Error message doesn't show any reason.
Server menager can connect normally.
Please help
what is the error message?
Sunday, March 25, 2012
Basic DTS service problems, i guess...
Server1 has a working DTS-service running
Server2 cannot start the DTS due to the following error:
"An error 1060 - (the specified service does not exist as an installes service) occured while performing this service operation on the MSDTC service".
Ok, I got it, the service isn't running (since I get this mess. when I'm tryin to start the service).
Can't find any service in the opsys services. Tried to reinstall the MSSQL but the MSDTC was/is allready installed.
Please help!
By the way, I'm running MSSQL 2000.
thanksIs the dtc service started ?|||Originally posted by rnealejr
Is the dtc service started ?
Nope, and that's the problem. I get the errormessage when I try to start the service in enterprise manager.
I can't find any corresponding service in the opsys services. It seems like the service isn't installed...but it is??!!
Sunday, March 11, 2012
Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005
Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?
05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181
Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?
Thanks,
Samuel Lester (MSFT)
From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
Please reboot and try again. May be SNAC reboot has halted the installation until reboot.
|||did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error
'failed because a higher version already exists on the machine'
Is it safe to uninstall backward compatability and reinstall it?
Thanks,
Kerry
|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005
Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?
05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181
Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?
Thanks,
Samuel Lester (MSFT)
From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
Please reboot and try again. May be SNAC reboot has halted the installation until reboot.
|||did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error
'failed because a higher version already exists on the machine'
Is it safe to uninstall backward compatability and reinstall it?
Thanks,
Kerry
|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005
Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?
05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181
Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?
Thanks,
Samuel Lester (MSFT)
From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
Please reboot and try again. May be SNAC reboot has halted the installation until reboot.
|||did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error
'failed because a higher version already exists on the machine'
Is it safe to uninstall backward compatability and reinstall it?
Thanks,
Kerry
|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.Wednesday, March 7, 2012
Backups Not Deleting
Plan that backs up all user databases, each to its own subfolder, every
night. The plan is supposed to delete old copies as well which it is not
doing. If I change the plan to backup only 1 database it works (old copies
deleted). When I switch it to all user databases, no more deletes. And the
sqlmaint log file does not even show that any deletes were attempted. Note
that we do have some databases offline, so those are skipped, of course, and
the job does fail.
Please help! What's the secret to get the older files to delete?
Here's the Step on the SQL Agent job:
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
21EA0A98-9812-4AEA-8BC0-08AEAEAB24EC -Rpt "c:\temp\DB Maintenance
Plan14.txt" -DelTxtRpt 1WEEKS -WriteHistory -VrfyBackup -BkUpMedia
DISK -BkUpDB "D:\Backup" -DelBkUps 1DAYS -CrBkSubDir -BkExt "BAK"'
Thanks,
Krip
>I believe that deletion is done *at the end* of the job, so if anything
>fails, it bails out and no deletion is performed. You can try by first
>including only database so the whole job succeeds.
Tibor,
Thanks for the tip! I detached all our offline databases, and job finishes
without error, and deletes the old backups. Beautiful.
-Krip
|||I have also seen this behavior when the plan includes both Full and Simple
Recovery model databases.
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"Krip" <amk@.kynetix.com> wrote in message
news:7A2C4350-5AED-4F70-A22A-47E64ED68DFD@.microsoft.com...
> Tibor,
> Thanks for the tip! I detached all our offline databases, and job
> finishes without error, and deletes the old backups. Beautiful.
> -Krip
>
Friday, February 24, 2012
BackupIoRequest::WaitForIoCompletion failure when restoring database
I have MS SQL 200 Server Developer Edition Installed from MSDN collection. (New installation with service pack 2). When I try to restore 7GB or bigger database, following error occurs in eventlog:
Source: MSSQLSERVER
Category: (6)
ID: 18210
Date: 11.9.2007
Time: 14:50:09
Description:
BackupIoRequest::WaitForIoCompletion: write failure on backup device ''. Operating system error 1450(here is message in local language like "here is no resources to complete requested service").
But I am not writting to backup device, I am restoring. Thank for any helpful answer.
Not sure about the cause of the error.. Check if its related to this KB : http://support.microsoft.com/default.aspx?scid=kb;en-us;304101
|||Thank you, dinakar.
KB howto i tried, but with no success.
Backup/Restore SP2 to SP3?
2000 (Service Pack 2) and Restore it on a server running
SQL Server 2000 (Service Pack 3)? (Without problems, of
course).
I want to not only restore User DBs, but also System DBs
sush as Master, Model, and msdb.
ThanksSystem databases, no. YOu cannot restore a previous
version (i.e. SP2) under SP3.
For user dbs, sure.
>--Original Message--
>Can I take a Backup created on a server running SQL
Server
>2000 (Service Pack 2) and Restore it on a server running
>SQL Server 2000 (Service Pack 3)? (Without problems, of
>course).
>I want to not only restore User DBs, but also System DBs
>sush as Master, Model, and msdb.
>Thanks
>.
>|||Allan
Does this mean that I can restore a user database saved on SP2 into SP3?
Ron Lounsbury
"Allan Hirt" <allanh@.NOSPAMavanade.com> wrote in message
news:561601c3b2c4$5b6ed470$a601280a@.phx.gbl...
> System databases, no. YOu cannot restore a previous
> version (i.e. SP2) under SP3.
> For user dbs, sure.
> >--Original Message--
> >Can I take a Backup created on a server running SQL
> Server
> >2000 (Service Pack 2) and Restore it on a server running
> >SQL Server 2000 (Service Pack 3)? (Without problems, of
> >course).
> >
> >I want to not only restore User DBs, but also System DBs
> >sush as Master, Model, and msdb.
> >
> >Thanks
> >
> >.
> >|||Yes, of course, you can. I do that all the time. Imagine
if you couldn't restore an SP2 user database to an SP3
instance, you would have to upgrade your Dev and prod
environments at the same time if you want to copy any
databases from the prod to the Dev for whatever purposes.
Linchi
>--Original Message--
>Allan
> Does this mean that I can restore a user database
saved on SP2 into SP3?
>Ron Lounsbury
>
>"Allan Hirt" <allanh@.NOSPAMavanade.com> wrote in message
>news:561601c3b2c4$5b6ed470$a601280a@.phx.gbl...
>> System databases, no. YOu cannot restore a previous
>> version (i.e. SP2) under SP3.
>> For user dbs, sure.
>> >--Original Message--
>> >Can I take a Backup created on a server running SQL
>> Server
>> >2000 (Service Pack 2) and Restore it on a server
running
>> >SQL Server 2000 (Service Pack 3)? (Without problems, of
>> >course).
>> >
>> >I want to not only restore User DBs, but also System
DBs
>> >sush as Master, Model, and msdb.
>> >
>> >Thanks
>> >
>> >.
>> >
>
>.
>
Friday, February 10, 2012
Backup to Network Resource from a Server Machine Service Account
Trying to backup to a network resource when SQL uses the machine service
account. Obviously something like EXEC sp_addumpdevice 'disk', 'device_name',
'\\filer_name\share_name\path\file_name.ext' would be used but this doesn't
work because of permissions.
Fairly new to DBA stuff so please have patience with me.
How can you do this?
Regards,
Richard.
You would need to have SQL Server using a service account that has permissions on that share.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> SQL Server 2000 SP4
> Trying to backup to a network resource when SQL uses the machine service
> account. Obviously something like EXEC sp_addumpdevice 'disk', 'device_name',
> '\\filer_name\share_name\path\file_name.ext' would be used but this doesn't
> work because of permissions.
> Fairly new to DBA stuff so please have patience with me.
> How can you do this?
> Regards,
> Richard.
|||I don't think Windows security works like that:
Services Using The System Account
Services that use the system account start in the system context (without
credentials). In Windows NT 3.5 and later, Windows NT services with no
credentials (no domain name, user name, or password) that attempt to connect
to network resources are denied access because they have no credentials and
they are using a null session. For additional information, click the article
number below to view the article in the Microsoft Knowledge Base:
from: http://support.microsoft.com/kb/132679
Essentially the local system account has no credentials so cannot
athenticate to anything on the network.
Is there anyway round this?
"Tibor Karaszi" wrote:
> You would need to have SQL Server using a service account that has permissions on that share.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
> news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
>
>
|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> SQL Server 2000 SP4
> Trying to backup to a network resource when SQL uses the machine service
> account. Obviously something like EXEC sp_addumpdevice 'disk',
> 'device_name',
> '\\filer_name\share_name\path\file_name.ext' would be used but this
> doesn't
> work because of permissions.
> Fairly new to DBA stuff so please have patience with me.
> How can you do this?
> Regards,
> Richard.
|||>I don't think Windows security works like that:
I don't see in what way what I said differs from the text you quoted.
> Is there anyway round this?
Not AFAIK...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:C2D36167-F2BE-464E-9404-3A689C9A0A22@.microsoft.com...[vbcol=seagreen]
>I don't think Windows security works like that:
> Services Using The System Account
> Services that use the system account start in the system context (without
> credentials). In Windows NT 3.5 and later, Windows NT services with no
> credentials (no domain name, user name, or password) that attempt to connect
> to network resources are denied access because they have no credentials and
> they are using a null session. For additional information, click the article
> number below to view the article in the Microsoft Knowledge Base:
> from: http://support.microsoft.com/kb/132679
> Essentially the local system account has no credentials so cannot
> athenticate to anything on the network.
>
> Is there anyway round this?
> "Tibor Karaszi" wrote:
|||As Tibor pointed out you need an account to run SQL Server Service under
that has the appropriate permissions to that share. A LOCAL account has no
permissions outside that box. So change it to a Domain account with the
appropriate permissions.
Andrew J. Kelly SQL MVP
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:C2D36167-F2BE-464E-9404-3A689C9A0A22@.microsoft.com...[vbcol=seagreen]
>I don't think Windows security works like that:
> Services Using The System Account
> Services that use the system account start in the system context (without
> credentials). In Windows NT 3.5 and later, Windows NT services with no
> credentials (no domain name, user name, or password) that attempt to
> connect
> to network resources are denied access because they have no credentials
> and
> they are using a null session. For additional information, click the
> article
> number below to view the article in the Microsoft Knowledge Base:
> from: http://support.microsoft.com/kb/132679
> Essentially the local system account has no credentials so cannot
> athenticate to anything on the network.
>
> Is there anyway round this?
> "Tibor Karaszi" wrote:
|||Hello,
To solve the issue you have start the SQL Server service using an Domain OS
user which got write
access to the remote share.
So go to Control Panel -- Admin Tools -- Services -- MSSQL Server sercice--
Double click and select the "Log on" option.
There you give a Valid Domain OS user and password to start the service. Now
stop and start the MSSQL Serevr service.
Note: That domain user should have previlages in the remote share to write
the file as well as prev. to start the SQL server.
After this you try to execute the Backup database command in Query
Analyzer:-
Backup database <dbname> to Disk='\\backup\tmp\networkdatabase.dat' with
init ( With init will overwrite the backup file every time)
Thanks
Hari
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> SQL Server 2000 SP4
> Trying to backup to a network resource when SQL uses the machine service
> account. Obviously something like EXEC sp_addumpdevice 'disk',
> 'device_name',
> '\\filer_name\share_name\path\file_name.ext' would be used but this
> doesn't
> work because of permissions.
> Fairly new to DBA stuff so please have patience with me.
> How can you do this?
> Regards,
> Richard.
Backup to Network Resource from a Server Machine Service Account
Trying to backup to a network resource when SQL uses the machine service
account. Obviously something like EXEC sp_addumpdevice 'disk', 'device_name',
'\\filer_name\share_name\path\file_name.ext' would be used but this doesn't
work because of permissions.
Fairly new to DBA stuff so please have patience with me.
How can you do this?
Regards,
Richard.You would need to have SQL Server using a service account that has permissions on that share.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> SQL Server 2000 SP4
> Trying to backup to a network resource when SQL uses the machine service
> account. Obviously something like EXEC sp_addumpdevice 'disk', 'device_name',
> '\\filer_name\share_name\path\file_name.ext' would be used but this doesn't
> work because of permissions.
> Fairly new to DBA stuff so please have patience with me.
> How can you do this?
> Regards,
> Richard.|||I don't think Windows security works like that:
Services Using The System Account
Services that use the system account start in the system context (without
credentials). In Windows NT 3.5 and later, Windows NT services with no
credentials (no domain name, user name, or password) that attempt to connect
to network resources are denied access because they have no credentials and
they are using a null session. For additional information, click the article
number below to view the article in the Microsoft Knowledge Base:
from: http://support.microsoft.com/kb/132679
Essentially the local system account has no credentials so cannot
athenticate to anything on the network.
Is there anyway round this?
"Tibor Karaszi" wrote:
> You would need to have SQL Server using a service account that has permissions on that share.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
> news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> > SQL Server 2000 SP4
> >
> > Trying to backup to a network resource when SQL uses the machine service
> > account. Obviously something like EXEC sp_addumpdevice 'disk', 'device_name',
> > '\\filer_name\share_name\path\file_name.ext' would be used but this doesn't
> > work because of permissions.
> >
> > Fairly new to DBA stuff so please have patience with me.
> >
> > How can you do this?
> >
> > Regards,
> > Richard.
>
>|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> SQL Server 2000 SP4
> Trying to backup to a network resource when SQL uses the machine service
> account. Obviously something like EXEC sp_addumpdevice 'disk',
> 'device_name',
> '\\filer_name\share_name\path\file_name.ext' would be used but this
> doesn't
> work because of permissions.
> Fairly new to DBA stuff so please have patience with me.
> How can you do this?
> Regards,
> Richard.|||>I don't think Windows security works like that:
I don't see in what way what I said differs from the text you quoted.
> Is there anyway round this?
Not AFAIK...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:C2D36167-F2BE-464E-9404-3A689C9A0A22@.microsoft.com...
>I don't think Windows security works like that:
> Services Using The System Account
> Services that use the system account start in the system context (without
> credentials). In Windows NT 3.5 and later, Windows NT services with no
> credentials (no domain name, user name, or password) that attempt to connect
> to network resources are denied access because they have no credentials and
> they are using a null session. For additional information, click the article
> number below to view the article in the Microsoft Knowledge Base:
> from: http://support.microsoft.com/kb/132679
> Essentially the local system account has no credentials so cannot
> athenticate to anything on the network.
>
> Is there anyway round this?
> "Tibor Karaszi" wrote:
>> You would need to have SQL Server using a service account that has permissions on that share.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
>> news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
>> > SQL Server 2000 SP4
>> >
>> > Trying to backup to a network resource when SQL uses the machine service
>> > account. Obviously something like EXEC sp_addumpdevice 'disk', 'device_name',
>> > '\\filer_name\share_name\path\file_name.ext' would be used but this doesn't
>> > work because of permissions.
>> >
>> > Fairly new to DBA stuff so please have patience with me.
>> >
>> > How can you do this?
>> >
>> > Regards,
>> > Richard.
>>|||As Tibor pointed out you need an account to run SQL Server Service under
that has the appropriate permissions to that share. A LOCAL account has no
permissions outside that box. So change it to a Domain account with the
appropriate permissions.
--
Andrew J. Kelly SQL MVP
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:C2D36167-F2BE-464E-9404-3A689C9A0A22@.microsoft.com...
>I don't think Windows security works like that:
> Services Using The System Account
> Services that use the system account start in the system context (without
> credentials). In Windows NT 3.5 and later, Windows NT services with no
> credentials (no domain name, user name, or password) that attempt to
> connect
> to network resources are denied access because they have no credentials
> and
> they are using a null session. For additional information, click the
> article
> number below to view the article in the Microsoft Knowledge Base:
> from: http://support.microsoft.com/kb/132679
> Essentially the local system account has no credentials so cannot
> athenticate to anything on the network.
>
> Is there anyway round this?
> "Tibor Karaszi" wrote:
>> You would need to have SQL Server using a service account that has
>> permissions on that share.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
>> news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
>> > SQL Server 2000 SP4
>> >
>> > Trying to backup to a network resource when SQL uses the machine
>> > service
>> > account. Obviously something like EXEC sp_addumpdevice 'disk',
>> > 'device_name',
>> > '\\filer_name\share_name\path\file_name.ext' would be used but this
>> > doesn't
>> > work because of permissions.
>> >
>> > Fairly new to DBA stuff so please have patience with me.
>> >
>> > How can you do this?
>> >
>> > Regards,
>> > Richard.
>>|||Hello,
To solve the issue you have start the SQL Server service using an Domain OS
user which got write
access to the remote share.
So go to Control Panel -- Admin Tools -- Services -- MSSQL Server sercice--
Double click and select the "Log on" option.
There you give a Valid Domain OS user and password to start the service. Now
stop and start the MSSQL Serevr service.
Note: That domain user should have previlages in the remote share to write
the file as well as prev. to start the SQL server.
After this you try to execute the Backup database command in Query
Analyzer:-
Backup database <dbname> to Disk='\\backup\tmp\networkdatabase.dat' with
init ( With init will overwrite the backup file every time)
Thanks
Hari
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> SQL Server 2000 SP4
> Trying to backup to a network resource when SQL uses the machine service
> account. Obviously something like EXEC sp_addumpdevice 'disk',
> 'device_name',
> '\\filer_name\share_name\path\file_name.ext' would be used but this
> doesn't
> work because of permissions.
> Fairly new to DBA stuff so please have patience with me.
> How can you do this?
> Regards,
> Richard.
Backup to Network Resource from a Server Machine Service Account
Trying to backup to a network resource when SQL uses the machine service
account. Obviously something like EXEC sp_addumpdevice 'disk', 'device_name'
,
'\\filer_name\share_name\path\file_name.ext' would be used but this doesn't
work because of permissions.
Fairly new to DBA stuff so please have patience with me.
How can you do this?
Regards,
Richard.You would need to have SQL Server using a service account that has permissio
ns on that share.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> SQL Server 2000 SP4
> Trying to backup to a network resource when SQL uses the machine service
> account. Obviously something like EXEC sp_addumpdevice 'disk', 'device_nam
e',
> '\\filer_name\share_name\path\file_name.ext' would be used but this doesn'
t
> work because of permissions.
> Fairly new to DBA stuff so please have patience with me.
> How can you do this?
> Regards,
> Richard.|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> SQL Server 2000 SP4
> Trying to backup to a network resource when SQL uses the machine service
> account. Obviously something like EXEC sp_addumpdevice 'disk',
> 'device_name',
> '\\filer_name\share_name\path\file_name.ext' would be used but this
> doesn't
> work because of permissions.
> Fairly new to DBA stuff so please have patience with me.
> How can you do this?
> Regards,
> Richard.|||Hello,
To solve the issue you have start the SQL Server service using an Domain OS
user which got write
access to the remote share.
So go to Control Panel -- Admin Tools -- Services -- MSSQL Server sercice--
Double click and select the "Log on" option.
There you give a Valid Domain OS user and password to start the service. Now
stop and start the MSSQL Serevr service.
Note: That domain user should have previlages in the remote share to write
the file as well as prev. to start the SQL server.
After this you try to execute the Backup database command in Query
Analyzer:-
Backup database <dbname> to Disk='\\backup\tmp\networkdatabase.dat' with
init ( With init will overwrite the backup file every time)
Thanks
Hari
"BQ_rmsterling" <richard.sterling@.bluesq.com> wrote in message
news:77F10996-5141-4C32-BE8B-6CF9A973FC0C@.microsoft.com...
> SQL Server 2000 SP4
> Trying to backup to a network resource when SQL uses the machine service
> account. Obviously something like EXEC sp_addumpdevice 'disk',
> 'device_name',
> '\\filer_name\share_name\path\file_name.ext' would be used but this
> doesn't
> work because of permissions.
> Fairly new to DBA stuff so please have patience with me.
> How can you do this?
> Regards,
> Richard.
Backup to Network Drive
drive. We have created a domain user and set the SQL Server Service and SQL
Server Agent to use this account. We have also set this account as a member
of the Administrators group on the SQL Server itself and added it to the sys
admin group within SQL Server. On the destination server, the service account
has full control on the share that we'd like to write to. Unfortunately, our
backups are failing. The SQL Server Log provides the following message
"BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
create. Operating system error = 5(Access is denied.)."
What are we missing here?Marcia,
Did you restart the SQL Server once the drive was mounted on your
server? Have you verified that as the user which SQL Server starts
under on the box you can read and write data to that location? These
are some of the gotcha's. I wish SQL Server allowed you to see network
mount points when you go to Backup Database options through Enterprise
Manager.
Shahryar
MarciaN wrote:
>We are attempting to set our SQL Server 2000 backups to point to a network
>drive. We have created a domain user and set the SQL Server Service and SQL
>Server Agent to use this account. We have also set this account as a member
>of the Administrators group on the SQL Server itself and added it to the sys
>admin group within SQL Server. On the destination server, the service account
>has full control on the share that we'd like to write to. Unfortunately, our
>backups are failing. The SQL Server Log provides the following message
>"BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
>create. Operating system error = 5(Access is denied.)."
>What are we missing here?
>
Shahryar G. Hashemi | Sr. DBA Consultant
InfoSpace, Inc.
601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 USA
Mobile +1 206.459.6203 | Office +1 425.201.8853 | Fax +1 425.201.6150
shashem@.infospace.com | www.infospaceinc.com
This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s); any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. Thank you.|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
> We are attempting to set our SQL Server 2000 backups to point to a network
> drive. We have created a domain user and set the SQL Server Service and
> SQL
> Server Agent to use this account. We have also set this account as a
> member
> of the Administrators group on the SQL Server itself and added it to the
> sys
> admin group within SQL Server. On the destination server, the service
> account
> has full control on the share that we'd like to write to. Unfortunately,
> our
> backups are failing. The SQL Server Log provides the following message
> "BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
> create. Operating system error = 5(Access is denied.)."
> What are we missing here?|||We have followed these procedures and still no luck. Can you give some
specifics related to the access levels that the WIndows Service account
should have?
"Geoff N. Hiten" wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?kbid=555128
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
> > We are attempting to set our SQL Server 2000 backups to point to a network
> > drive. We have created a domain user and set the SQL Server Service and
> > SQL
> > Server Agent to use this account. We have also set this account as a
> > member
> > of the Administrators group on the SQL Server itself and added it to the
> > sys
> > admin group within SQL Server. On the destination server, the service
> > account
> > has full control on the share that we'd like to write to. Unfortunately,
> > our
> > backups are failing. The SQL Server Log provides the following message
> > "BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
> > create. Operating system error = 5(Access is denied.)."
> >
> > What are we missing here?
>
>|||The SQL Server service account requires FULL CONTROL over the share and the
underlying NTFS directory structure.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:12B2D6D3-3FFF-4356-9857-700A5E2CF2F0@.microsoft.com...
> We have followed these procedures and still no luck. Can you give some
> specifics related to the access levels that the WIndows Service account
> should have?
>
> "Geoff N. Hiten" wrote:
>> HowTo: Backup to UNC name using Database Maintenance Wizard
>> http://support.microsoft.com/?kbid=555128
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
>> news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
>> > We are attempting to set our SQL Server 2000 backups to point to a
>> > network
>> > drive. We have created a domain user and set the SQL Server Service and
>> > SQL
>> > Server Agent to use this account. We have also set this account as a
>> > member
>> > of the Administrators group on the SQL Server itself and added it to
>> > the
>> > sys
>> > admin group within SQL Server. On the destination server, the service
>> > account
>> > has full control on the share that we'd like to write to.
>> > Unfortunately,
>> > our
>> > backups are failing. The SQL Server Log provides the following message
>> > "BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed
>> > to
>> > create. Operating system error = 5(Access is denied.)."
>> >
>> > What are we missing here?
>>|||We gave the service account FULL CONTROL over the share. After an
unsuccessful test of that, we added the service account to the local admins
group on the destination server and still no luck. It seems like we have
covered all the bases but still can not make this work. Can you think of
anything else?
"Geoff N. Hiten" wrote:
> The SQL Server service account requires FULL CONTROL over the share and the
> underlying NTFS directory structure.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> news:12B2D6D3-3FFF-4356-9857-700A5E2CF2F0@.microsoft.com...
> > We have followed these procedures and still no luck. Can you give some
> > specifics related to the access levels that the WIndows Service account
> > should have?
> >
> >
> > "Geoff N. Hiten" wrote:
> >
> >> HowTo: Backup to UNC name using Database Maintenance Wizard
> >> http://support.microsoft.com/?kbid=555128
> >>
> >> --
> >> Geoff N. Hiten
> >> Senior Database Administrator
> >> Microsoft SQL Server MVP
> >> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> >> news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
> >> > We are attempting to set our SQL Server 2000 backups to point to a
> >> > network
> >> > drive. We have created a domain user and set the SQL Server Service and
> >> > SQL
> >> > Server Agent to use this account. We have also set this account as a
> >> > member
> >> > of the Administrators group on the SQL Server itself and added it to
> >> > the
> >> > sys
> >> > admin group within SQL Server. On the destination server, the service
> >> > account
> >> > has full control on the share that we'd like to write to.
> >> > Unfortunately,
> >> > our
> >> > backups are failing. The SQL Server Log provides the following message
> >> > "BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed
> >> > to
> >> > create. Operating system error = 5(Access is denied.)."
> >> >
> >> > What are we missing here?
> >>
> >>
> >>
>
>|||Verify NTFS file permissions on the destination directory. This is
different from the share security permissions.
Log in to the console of the SQL Server as the service account and try to
access the network share directly. Create, rename, and delete a file.
Run a backup via Query Analyzer (BACKUP DATABASE command) to the share
location.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:3469833A-EC8A-4755-828B-D309A0A2F72E@.microsoft.com...
> We gave the service account FULL CONTROL over the share. After an
> unsuccessful test of that, we added the service account to the local
> admins
> group on the destination server and still no luck. It seems like we have
> covered all the bases but still can not make this work. Can you think of
> anything else?
> "Geoff N. Hiten" wrote:
>> The SQL Server service account requires FULL CONTROL over the share and
>> the
>> underlying NTFS directory structure.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
>> news:12B2D6D3-3FFF-4356-9857-700A5E2CF2F0@.microsoft.com...
>> > We have followed these procedures and still no luck. Can you give some
>> > specifics related to the access levels that the WIndows Service account
>> > should have?
>> >
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> HowTo: Backup to UNC name using Database Maintenance Wizard
>> >> http://support.microsoft.com/?kbid=555128
>> >>
>> >> --
>> >> Geoff N. Hiten
>> >> Senior Database Administrator
>> >> Microsoft SQL Server MVP
>> >> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
>> >> news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
>> >> > We are attempting to set our SQL Server 2000 backups to point to a
>> >> > network
>> >> > drive. We have created a domain user and set the SQL Server Service
>> >> > and
>> >> > SQL
>> >> > Server Agent to use this account. We have also set this account as a
>> >> > member
>> >> > of the Administrators group on the SQL Server itself and added it to
>> >> > the
>> >> > sys
>> >> > admin group within SQL Server. On the destination server, the
>> >> > service
>> >> > account
>> >> > has full control on the share that we'd like to write to.
>> >> > Unfortunately,
>> >> > our
>> >> > backups are failing. The SQL Server Log provides the following
>> >> > message
>> >> > "BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup'
>> >> > failed
>> >> > to
>> >> > create. Operating system error = 5(Access is denied.)."
>> >> >
>> >> > What are we missing here?
>> >>
>> >>
>> >>
>>|||I'd start by logging in on the SQL Server machine using the service account and see if I can access
and create files. If so, use xp_cmdshell to see if you can do the same.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:3469833A-EC8A-4755-828B-D309A0A2F72E@.microsoft.com...
> We gave the service account FULL CONTROL over the share. After an
> unsuccessful test of that, we added the service account to the local admins
> group on the destination server and still no luck. It seems like we have
> covered all the bases but still can not make this work. Can you think of
> anything else?
> "Geoff N. Hiten" wrote:
>> The SQL Server service account requires FULL CONTROL over the share and the
>> underlying NTFS directory structure.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
>> news:12B2D6D3-3FFF-4356-9857-700A5E2CF2F0@.microsoft.com...
>> > We have followed these procedures and still no luck. Can you give some
>> > specifics related to the access levels that the WIndows Service account
>> > should have?
>> >
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> HowTo: Backup to UNC name using Database Maintenance Wizard
>> >> http://support.microsoft.com/?kbid=555128
>> >>
>> >> --
>> >> Geoff N. Hiten
>> >> Senior Database Administrator
>> >> Microsoft SQL Server MVP
>> >> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
>> >> news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
>> >> > We are attempting to set our SQL Server 2000 backups to point to a
>> >> > network
>> >> > drive. We have created a domain user and set the SQL Server Service and
>> >> > SQL
>> >> > Server Agent to use this account. We have also set this account as a
>> >> > member
>> >> > of the Administrators group on the SQL Server itself and added it to
>> >> > the
>> >> > sys
>> >> > admin group within SQL Server. On the destination server, the service
>> >> > account
>> >> > has full control on the share that we'd like to write to.
>> >> > Unfortunately,
>> >> > our
>> >> > backups are failing. The SQL Server Log provides the following message
>> >> > "BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed
>> >> > to
>> >> > create. Operating system error = 5(Access is denied.)."
>> >> >
>> >> > What are we missing here?
>> >>
>> >>
>> >>
>>|||It's working! We deleted the shared folder and recreated it. Now it works.
Thanks to all for your suggestions.
"Tibor Karaszi" wrote:
> I'd start by logging in on the SQL Server machine using the service account and see if I can access
> and create files. If so, use xp_cmdshell to see if you can do the same.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> news:3469833A-EC8A-4755-828B-D309A0A2F72E@.microsoft.com...
> > We gave the service account FULL CONTROL over the share. After an
> > unsuccessful test of that, we added the service account to the local admins
> > group on the destination server and still no luck. It seems like we have
> > covered all the bases but still can not make this work. Can you think of
> > anything else?
> >
> > "Geoff N. Hiten" wrote:
> >
> >> The SQL Server service account requires FULL CONTROL over the share and the
> >> underlying NTFS directory structure.
> >>
> >> --
> >> Geoff N. Hiten
> >> Senior Database Administrator
> >> Microsoft SQL Server MVP
> >>
> >> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> >> news:12B2D6D3-3FFF-4356-9857-700A5E2CF2F0@.microsoft.com...
> >> > We have followed these procedures and still no luck. Can you give some
> >> > specifics related to the access levels that the WIndows Service account
> >> > should have?
> >> >
> >> >
> >> > "Geoff N. Hiten" wrote:
> >> >
> >> >> HowTo: Backup to UNC name using Database Maintenance Wizard
> >> >> http://support.microsoft.com/?kbid=555128
> >> >>
> >> >> --
> >> >> Geoff N. Hiten
> >> >> Senior Database Administrator
> >> >> Microsoft SQL Server MVP
> >> >> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> >> >> news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
> >> >> > We are attempting to set our SQL Server 2000 backups to point to a
> >> >> > network
> >> >> > drive. We have created a domain user and set the SQL Server Service and
> >> >> > SQL
> >> >> > Server Agent to use this account. We have also set this account as a
> >> >> > member
> >> >> > of the Administrators group on the SQL Server itself and added it to
> >> >> > the
> >> >> > sys
> >> >> > admin group within SQL Server. On the destination server, the service
> >> >> > account
> >> >> > has full control on the share that we'd like to write to.
> >> >> > Unfortunately,
> >> >> > our
> >> >> > backups are failing. The SQL Server Log provides the following message
> >> >> > "BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed
> >> >> > to
> >> >> > create. Operating system error = 5(Access is denied.)."
> >> >> >
> >> >> > What are we missing here?
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>|||Windows has two level access control.
You need to give the sql account first the access to the shared
drive/directory and then you need to give access to the
files
1. Access to the SHARE
2. Access to files on that share
1. On the shared directory right click-> sharing->permissions. Check the
SQL account has access rights.
2. same right click->security->permissions. check the SQL account has
rights.
That should do it
rgrds Matti
Backup to Network Drive
drive. We have created a domain user and set the SQL Server Service and SQL
Server Agent to use this account. We have also set this account as a member
of the Administrators group on the SQL Server itself and added it to the sys
admin group within SQL Server. On the destination server, the service account
has full control on the share that we'd like to write to. Unfortunately, our
backups are failing. The SQL Server Log provides the following message
"BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
create. Operating system error = 5(Access is denied.)."
What are we missing here?
Marcia,
Did you restart the SQL Server once the drive was mounted on your
server? Have you verified that as the user which SQL Server starts
under on the box you can read and write data to that location? These
are some of the gotcha's. I wish SQL Server allowed you to see network
mount points when you go to Backup Database options through Enterprise
Manager.
Shahryar
MarciaN wrote:
>We are attempting to set our SQL Server 2000 backups to point to a network
>drive. We have created a domain user and set the SQL Server Service and SQL
>Server Agent to use this account. We have also set this account as a member
>of the Administrators group on the SQL Server itself and added it to the sys
>admin group within SQL Server. On the destination server, the service account
>has full control on the share that we'd like to write to. Unfortunately, our
>backups are failing. The SQL Server Log provides the following message
>"BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
>create. Operating system error = 5(Access is denied.)."
>What are we missing here?
>
Shahryar G. Hashemi | Sr. DBA Consultant
InfoSpace, Inc.
601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 USA
Mobile +1 206.459.6203 | Office +1 425.201.8853 | Fax +1 425.201.6150
shashem@.infospace.com | www.infospaceinc.com
This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s); any disclosure, copying, distribution, or other use of this information is strictly prohi
bited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. Thank you.
|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
> We are attempting to set our SQL Server 2000 backups to point to a network
> drive. We have created a domain user and set the SQL Server Service and
> SQL
> Server Agent to use this account. We have also set this account as a
> member
> of the Administrators group on the SQL Server itself and added it to the
> sys
> admin group within SQL Server. On the destination server, the service
> account
> has full control on the share that we'd like to write to. Unfortunately,
> our
> backups are failing. The SQL Server Log provides the following message
> "BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
> create. Operating system error = 5(Access is denied.)."
> What are we missing here?
|||We have followed these procedures and still no luck. Can you give some
specifics related to the access levels that the WIndows Service account
should have?
"Geoff N. Hiten" wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?kbid=555128
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
>
>
|||The SQL Server service account requires FULL CONTROL over the share and the
underlying NTFS directory structure.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:12B2D6D3-3FFF-4356-9857-700A5E2CF2F0@.microsoft.com...[vbcol=seagreen]
> We have followed these procedures and still no luck. Can you give some
> specifics related to the access levels that the WIndows Service account
> should have?
>
> "Geoff N. Hiten" wrote:
|||We gave the service account FULL CONTROL over the share. After an
unsuccessful test of that, we added the service account to the local admins
group on the destination server and still no luck. It seems like we have
covered all the bases but still can not make this work. Can you think of
anything else?
"Geoff N. Hiten" wrote:
> The SQL Server service account requires FULL CONTROL over the share and the
> underlying NTFS directory structure.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> news:12B2D6D3-3FFF-4356-9857-700A5E2CF2F0@.microsoft.com...
>
>
|||Verify NTFS file permissions on the destination directory. This is
different from the share security permissions.
Log in to the console of the SQL Server as the service account and try to
access the network share directly. Create, rename, and delete a file.
Run a backup via Query Analyzer (BACKUP DATABASE command) to the share
location.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:3469833A-EC8A-4755-828B-D309A0A2F72E@.microsoft.com...[vbcol=seagreen]
> We gave the service account FULL CONTROL over the share. After an
> unsuccessful test of that, we added the service account to the local
> admins
> group on the destination server and still no luck. It seems like we have
> covered all the bases but still can not make this work. Can you think of
> anything else?
> "Geoff N. Hiten" wrote:
|||I'd start by logging in on the SQL Server machine using the service account and see if I can access
and create files. If so, use xp_cmdshell to see if you can do the same.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:3469833A-EC8A-4755-828B-D309A0A2F72E@.microsoft.com...[vbcol=seagreen]
> We gave the service account FULL CONTROL over the share. After an
> unsuccessful test of that, we added the service account to the local admins
> group on the destination server and still no luck. It seems like we have
> covered all the bases but still can not make this work. Can you think of
> anything else?
> "Geoff N. Hiten" wrote:
|||It's working! We deleted the shared folder and recreated it. Now it works.
Thanks to all for your suggestions.
"Tibor Karaszi" wrote:
> I'd start by logging in on the SQL Server machine using the service account and see if I can access
> and create files. If so, use xp_cmdshell to see if you can do the same.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> news:3469833A-EC8A-4755-828B-D309A0A2F72E@.microsoft.com...
>
|||Windows has two level access control.
You need to give the sql account first the access to the shared
drive/directory and then you need to give access to the
files
1. Access to the SHARE
2. Access to files on that share
1. On the shared directory right click-> sharing->permissions. Check the
SQL account has access rights.
2. same right click->security->permissions. check the SQL account has
rights.
That should do it
rgrds Matti
Backup to Network Drive
drive. We have created a domain user and set the SQL Server Service and SQL
Server Agent to use this account. We have also set this account as a member
of the Administrators group on the SQL Server itself and added it to the sys
admin group within SQL Server. On the destination server, the service accoun
t
has full control on the share that we'd like to write to. Unfortunately, our
backups are failing. The SQL Server Log provides the following message
"BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
create. Operating system error = 5(Access is denied.)."
What are we missing here?Marcia,
Did you restart the SQL Server once the drive was mounted on your
server? Have you verified that as the user which SQL Server starts
under on the box you can read and write data to that location? These
are some of the gotcha's. I wish SQL Server allowed you to see network
mount points when you go to Backup Database options through Enterprise
Manager.
Shahryar
MarciaN wrote:
>We are attempting to set our SQL Server 2000 backups to point to a network
>drive. We have created a domain user and set the SQL Server Service and SQL
>Server Agent to use this account. We have also set this account as a member
>of the Administrators group on the SQL Server itself and added it to the sy
s
>admin group within SQL Server. On the destination server, the service accou
nt
>has full control on the share that we'd like to write to. Unfortunately, ou
r
>backups are failing. The SQL Server Log provides the following message
>"BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
>create. Operating system error = 5(Access is denied.)."
>What are we missing here?
>
Shahryar G. Hashemi | Sr. DBA Consultant
InfoSpace, Inc.
601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 USA
Mobile +1 206.459.6203 | Office +1 425.201.8853 | Fax +1 425.201.6150
shashem@.infospace.com | www.infospaceinc.com
This e-mail and any attachments may contain confidential information that is
legally privileged. The information is solely for the use of the intended
recipient(s); any disclosure, copying, distribution, or other use of this in
formation is strictly prohi
bited. If you have received this e-mail in error, please notify the sender
by return e-mail and delete this message. Thank you.|||HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/?kbid=555128
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
> We are attempting to set our SQL Server 2000 backups to point to a network
> drive. We have created a domain user and set the SQL Server Service and
> SQL
> Server Agent to use this account. We have also set this account as a
> member
> of the Administrators group on the SQL Server itself and added it to the
> sys
> admin group within SQL Server. On the destination server, the service
> account
> has full control on the share that we'd like to write to. Unfortunately,
> our
> backups are failing. The SQL Server Log provides the following message
> "BackupDiskFile::CreateMedia: Backup device '\\Server\SQLBackup' failed to
> create. Operating system error = 5(Access is denied.)."
> What are we missing here?|||We have followed these procedures and still no luck. Can you give some
specifics related to the access levels that the WIndows Service account
should have?
"Geoff N. Hiten" wrote:
> HowTo: Backup to UNC name using Database Maintenance Wizard
> http://support.microsoft.com/?kbid=555128
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> news:B8AAEF33-2B4B-445A-ADBF-F2D74A78F0D2@.microsoft.com...
>
>|||The SQL Server service account requires FULL CONTROL over the share and the
underlying NTFS directory structure.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:12B2D6D3-3FFF-4356-9857-700A5E2CF2F0@.microsoft.com...[vbcol=seagreen]
> We have followed these procedures and still no luck. Can you give some
> specifics related to the access levels that the WIndows Service account
> should have?
>
> "Geoff N. Hiten" wrote:
>|||We gave the service account FULL CONTROL over the share. After an
unsuccessful test of that, we added the service account to the local admins
group on the destination server and still no luck. It seems like we have
covered all the bases but still can not make this work. Can you think of
anything else?
"Geoff N. Hiten" wrote:
> The SQL Server service account requires FULL CONTROL over the share and th
e
> underlying NTFS directory structure.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> news:12B2D6D3-3FFF-4356-9857-700A5E2CF2F0@.microsoft.com...
>
>|||Verify NTFS file permissions on the destination directory. This is
different from the share security permissions.
Log in to the console of the SQL Server as the service account and try to
access the network share directly. Create, rename, and delete a file.
Run a backup via Query Analyzer (BACKUP DATABASE command) to the share
location.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:3469833A-EC8A-4755-828B-D309A0A2F72E@.microsoft.com...[vbcol=seagreen]
> We gave the service account FULL CONTROL over the share. After an
> unsuccessful test of that, we added the service account to the local
> admins
> group on the destination server and still no luck. It seems like we have
> covered all the bases but still can not make this work. Can you think of
> anything else?
> "Geoff N. Hiten" wrote:
>|||I'd start by logging in on the SQL Server machine using the service account
and see if I can access
and create files. If so, use xp_cmdshell to see if you can do the same.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
news:3469833A-EC8A-4755-828B-D309A0A2F72E@.microsoft.com...[vbcol=seagreen]
> We gave the service account FULL CONTROL over the share. After an
> unsuccessful test of that, we added the service account to the local admin
s
> group on the destination server and still no luck. It seems like we have
> covered all the bases but still can not make this work. Can you think of
> anything else?
> "Geoff N. Hiten" wrote:
>|||It's working! We deleted the shared folder and recreated it. Now it works.
Thanks to all for your suggestions.
"Tibor Karaszi" wrote:
> I'd start by logging in on the SQL Server machine using the service accoun
t and see if I can access
> and create files. If so, use xp_cmdshell to see if you can do the same.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "MarciaN" <MarciaN@.discussions.microsoft.com> wrote in message
> news:3469833A-EC8A-4755-828B-D309A0A2F72E@.microsoft.com...
>|||Windows has two level access control.
You need to give the sql account first the access to the shared
drive/directory and then you need to give access to the
files
1. Access to the SHARE
2. Access to files on that share
1. On the shared directory right click-> sharing->permissions. Check the
SQL account has access rights.
2. same right click->security->permissions. check the SQL account has
rights.
That should do it
rgrds Matti