On SQL 2005, I created a simple database and log file backup job using the Maintenance Plan wizard and scheduled it, but it does not work. When I run it, it generates an error:
"Unable to start execution of step 1 (reason: line(1): Syntax error). The step failed."
I can't believe MS would have this kind of bug. Something generated by a wizard needs to work. PERIOD.
Anyway, the fix for me was this:
1. Go to SQL Server Agents\Jobs. Select job and click Properties.
2. Go down to Steps
3. Highlight your SubPlan and click Edit
4. Add a Backslash to the beginning of the path listed in the "Package" box
And, like magic, no error and job runs.
Hope that helps!
Thursday, October 14, 2010
Wednesday, October 13, 2010
Event ID 4292 - The IPSec driver has entered Block mode.
Full event properties:
The IPSec driver has entered Block mode. IPSec will discard all inbound and outbound TCP/IP network traffic that is not permitted by boot-time IPSec Policy exemptions. User Action: To restore full unsecured TCP/IP connectivity, disable the IPSec services, and then restart the computer. For detailed troubleshooting information, review the events in the Security event log.
Possible Cause:
A corrupted file in the policy store causes this problem. An interruption that occurs when the policy is being written to the disk may cause the corruption.
Check:
When you try to open the Internet Protocol security (IPSec) Microsoft Management Console (MMC) policy on a Microsoft Windows Server 2003-based computer, you receive the following error message:
"The IPSec Policy storage container could not be opened. The following error occurred: The system cannot find the file specified. (80070002)."
Resolution:
References: http://support.microsoft.com/kb/870910
The IPSec driver has entered Block mode. IPSec will discard all inbound and outbound TCP/IP network traffic that is not permitted by boot-time IPSec Policy exemptions. User Action: To restore full unsecured TCP/IP connectivity, disable the IPSec services, and then restart the computer. For detailed troubleshooting information, review the events in the Security event log.
Possible Cause:
A corrupted file in the policy store causes this problem. An interruption that occurs when the policy is being written to the disk may cause the corruption.
Check:
When you try to open the Internet Protocol security (IPSec) Microsoft Management Console (MMC) policy on a Microsoft Windows Server 2003-based computer, you receive the following error message:
"The IPSec Policy storage container could not be opened. The following error occurred: The system cannot find the file specified. (80070002)."
Resolution:
- In Registry Editor, locate and then DELETE the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\IPSec\Policy\Local
- Close Registry Editor.
- Rebuild a new local policy store. To do this, Click Start, click Run, type regsvr32 polstore.dll, and then click OK.
References: http://support.microsoft.com/kb/870910
Subscribe to:
Comments (Atom)