| Author |
Topic |
|
rhofing
Starting Member
15 Posts |
 Posted - 2004-03-25 : 09:24:47
|
| Hello, I am trying to install log shipping on one of our older SQL 7 boxes. I have run the scripts to create the various tables and stored procedures and run them. I now have two jobs: a Load and a Copy job. The Load is failing with the following error:sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.I have verified the source and destination server names are correct, as well as the UNC paths for the log file source and destination. Both servers can see each other in SQL.I have never setup log shipping in SQL 7 and I would appreciate any help.Ric |
|
|
Sitka
Aged Yak Warrior
571 Posts |
Posted - 2004-03-25 : 10:00:42
|
| I just did this a little while ago. I used this article mainlyhttp://www.sql-server-performance.com/sql_server_log_shipping.aspAre you using the set of tools that came with the resource kit.Or totally by hand. How are you driving the physical file namesof the log backups from a maintenance plan?One key to get mine running was to create a domain user thatwas dedicated as the "run/startup" service account for both the live serverand standby server MSSQLSERVER and SQLSERVERAGENT.It is a rich creamy color with a high fat content of 5-7 percent. Being so high in fat, it is usually processed into butter, cheese, or yogurt. An average cow will produce 110 kg. Milk in a lactation period of an average of 149 days |
 |
|
|
MuadDBA
628 Posts |
Posted - 2004-03-25 : 11:21:36
|
| Try running the statement in query analyzer, it will give you more info abotu why the task failed. then post it here. |
|
|
|
rhofing
Starting Member
15 Posts |
Posted - 2004-03-25 : 11:35:20
|
| Here is the command being run:EXECUTE master.dbo.xp_sqlmaint '-CopyPlanName "Log ship P0121010 to P028965" ' Here is the output: (I replaced the username with *)Logged on to SQL Server 'P0028965' as 'MTL01\********' (trusted)SQLMAINT.EXE Process Exit Code: 1 (Failed)Server: Msg 22029, Level 16, State 1, Line 0sqlmaint.exe failed. |
|
|
|
rhofing
Starting Member
15 Posts |
Posted - 2004-03-25 : 11:47:52
|
| One additional note: To verify the SLQAgent account had the appropriate permissions I created a scheduled job that used xp_cmdshell to copy the transaction log files from the backup server to the source server (using UNC naming conventions for the paths), ran the job and it worked fine. |
|
|
|
Sitka
Aged Yak Warrior
571 Posts |
Posted - 2004-03-26 : 11:44:28
|
| Good note, might not be enough, depending on your environment.(especially legacy cause the SQL7 maybe started in an NT4 DOMAIN then moved to Win2000)xp_cmdshell lets you run scripts locally to impact (ie xcopy) across a network (DOMAIN/NTFS jusrisdiction) but RESTORE on the standy server defaults to members of the sysadmin role.It is interesting that you are using maintenence plans for SQL7 log shipping.That approach didn't seem obvious to me.It is a rich creamy color with a high fat content of 5-7 percent. Being so high in fat, it is usually processed into butter, cheese, or yogurt. An average cow will produce 110 kg. Milk in a lactation period of an average of 149 days |
|
|
|
MuadDBA
628 Posts |
Posted - 2004-03-26 : 15:16:19
|
| using SQLMaint.EXE is the way that the log shipping that comes with the resource kit works. I got the CD in a class and used it in a couple implementations, and now I wish I hadn't, simply because of how hard it is to debug the jobs....the only failure message you ever get from the job is "SQLMAINT.EXE failed". |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-26 : 15:18:51
|
| Well, although the job says SQLMAINT.exe failed, you can get the actual error by looking at the SQL Server Error Log. Just find the entry in there that corresponds to the time that the job failed.Tara |
|
|
|
MuadDBA
628 Posts |
Posted - 2004-03-29 : 10:53:25
|
| ooh, I have never tried that (silly me). Of course, my standby server does log restores every 5 minutes, so the error log gets kinda big :) |
|
|
|
|
SQL 7 Log shipping