Jump to content

Client backup fails with Error 540


Recommended Posts

Yesterday, from an old piece of advice found on this forum, I edited my RetroClient file in /Library/StartupItems/RetroClient so it would have the correct path to pitond and would hopefully stop turning off my client every time my laptop goes to sleep or gets restarted. I had previously moved the Retrospect Client from its default location in /Applications/Retrospect Client/ to where I wanted it in /Applications/Utilities.

 

 

 

I left my laptop here at the office last night to get backed up as usual. In the morning, I saw that the backup had failed on another volume for unrelated reasons and sat until the backup server script schedule was over.

 

 

 

No biggie, I thought, and set the schedule for my Pismo's backup server script to 'Always' and told it to backup ASAP. Retrospect Workgroup Backup 5.0.236 on my Xserve had no problem seeing, logging into, or configuring any of the clients, including my Pismo which is running Retrospect Client 5.0.540. Both machines are running Mac OS X 10.2.1.

 

 

 

After giving my Pismo the 20 second countdown, the backup server started scanning my files but stopped after about 1,900 files. Yesterday morning during a successful backup, I watched it count about 230,000 files. The remaining window on the server said "Execution Incomplete. See log for details." The log reported:

 

 

 

Scanning incomplete, error 540 (trouble creating service)

 

 

 

I initiated a backup of all the other clients in the office that didn't get backed up last night to see if the problem was universal or specific to my computer. The other clients backed up with no problems.

 

 

 

Searching the Dantz.com Support site for "540" came up with:

 

 

 

Error -540 (trouble creating service)This error means that Retrospect could not properly access a Windows client.

 

 

 

It went on to say that the error is specific to Windows 95. My error is "540" not "-540" but the description (trouble creating service) is the same.

 

 

 

Figuring that I had messed up my client yesterday, I erased every file relating to Retrospect from my computer, including killing and erasing the pitond process. I didn't look for invisible files. The files I erased were:

 

 

 

/Library/StartupItems/RetroClient/RetroClient

 

/Library/StartupItems/RetroClient/StartupParameters.plist

 

/Library/StartupItems/RetroRun/*

 

/Library/Preferences/Retrospect

 

/Library/Preferences/retroclient.state

 

 

 

There might have been some others, but I think they were related to the time I attempted to run Workgroup on my computer.

 

 

 

Once every trace was gone, I copied the known-good Retrospect Client 5.0.540 Installer from my server and ran it locally. The installation went smoothly and I left the files alone where they were installed. Then I rebooted the Pismo when requested by the installer. When it rebooted, I confirmed that the old files were gone, the new files were in place, and one instance of pitond was running.

 

 

 

In Retrospect's Configure -> Clients on the Xserve, I Forgot the old Pismo client, went into Network, and logged into the Pismo with the password I gave to the Client installer. Everything looked good when I went to Configure. I was able to synchronize the clocks, see the startup disk, and verify that the client had a password and was of version 5.0.540. I went back to edit my backup server script and told it to use my startup disk.

 

 

 

When I started the backup server, it connected to the client and started scanning my hard drive. This time it got only about 400 files into the scan before it stopped with the Error 540 in the log.

 

 

 

I told it to Forget the client again and when I logged back in, I told it to use the entire Desktop in the Configure window. In the backup server script window, I told it to use the entire client as the backup source.

 

 

 

This time when I started the backup server, it scanned about 20,000 files (out of 230,000) and stopped with the Error 540 in the log. (Just when I was getting my hopes up.)

 

 

 

Here is a sample of my Operations Log:

 

 

 

 

 

- 10/24/2002 11:42 AM: Backup Server stopped

 

* $[24]$[*!s13805,,14,+3]Pismo$[25]: forgotten from client database

 

Quit at 10/24/2002 11:42 AM

 

 

 

 

 

$[31]Retrospect$[32] version 5.0.236

 

launched at 10/24/2002 11:46 AM

 

+ Retrospect Driver Update, version 3.0.104

 

 

 

+ 10/24/2002 11:46 AM: Backup Server started

 

 

 

- 10/24/2002 11:47 AM: Backup Server stopped

 

* $[24]$[*!s13805,,14,+3]Pismo$[25]: logged into client database

 

 

 

+ 10/24/2002 11:50 AM: Backup Server started

 

 

 

+ Normal backup using $[24]Pismo$[25] at 10/24/2002 11:50 AM

 

To backup set $[*!s321,,14,+3]02/10/10 B…

 

 

 

- 10/24/2002 11:50:38 AM: Copying $[*!s314,,14,+3]Pismo on $[35]Pismo$[36]…

 

10/24/2002 11:50:38 AM: Connected to $[*!s13805,,14,+3]Pismo

 

$[40] Scanning incomplete, error 540 (trouble creating service)

Link to comment
Share on other sites

Any ideas? Please help.

 

 

 

Thanks,

 

 

 

Bryan

 

 

 

My posts are getting chopped off at the bottom . . .

 

 

 

 

 

 

 

- 10/24/2002 11:54 AM: Backup Server stopped

 

* $[24]$[*!s13805,,14,+3]Pismo$[25]: forgotten from client database

 

* $[24]$[*!s13805,,14,+3]Pismo$[25]: logged into client database

 

 

 

+ 10/24/2002 11:55 AM: Backup Server started

 

 

 

+ Normal backup using $[24]Pismo$[25] at 10/24/2002 11:56 AM

 

To backup set $[*!s321,,14,+3]02/10/10 B…

 

 

 

- 10/24/2002 11:56:23 AM: Copying $[*!s314,,14,+3]Pismo on $[35]Pismo$[36]…

 

10/24/2002 11:56:23 AM: Connected to $[*!s13805,,14,+3]Pismo

 

$[40] Scanning incomplete, error 540 (trouble creating service)

 

 

 

+ Normal backup using $[24]Pismo$[25] at 10/24/2002 11:57 AM

 

To backup set $[*!s321,,14,+3]02/10/10 B…

 

 

 

- 10/24/2002 11:57:09 AM: Copying $[*!s314,,14,+3]Pismo on $[35]Pismo$[36]…

 

10/24/2002 11:57:09 AM: Connected to $[*!s13805,,14,+3]Pismo

 

$[40] Scanning incomplete, error 540 (trouble creating service)

Link to comment
Share on other sites

Update (still talking to myself):

 

 

 

The next night, it scanned about 3% of my files before stopping with an "Error 540 (trouble creating service)" in the log.

 

 

 

I copied the Client Installer (5.0.540) from my server again and this time ran it in Unistall mode. After a few minutes of looking locked up (no progress bar movement), it took off and deleted most of the Retrospect files. It complained that either some files were in use or some folders had non-Retrospect files in them, so I rebooted and checked the hard drive for Retrospect Client files. It appeared to be clear of them, but I ran the de-installer again just in case. (I was running out of ideas at this point and Dantz has yet to provide any clues as to what the Error 540 means in Mac OS X.) I had the same experience with the de-installer, so I quit it and ran the Installer again.

 

 

 

The installer ran smoothly again, asked for the password, and dumped it's Client folder loose in the Applications folder, where it likes to be. Once again, I didn't move it. I then turned on the Client.

 

 

 

On the server, I ran throught the process again: Forget client, Login client, Configure client, update backup server script to use client.

 

 

 

From the Immediate pane of the Directory window, I initiated an Immediate Backup. It worked!

 

 

 

I was thinking I could now track down the problem on the server if the backup server script failed, but it didn't!

 

 

 

I'm very thankful that my computer has been backing up properly for the last two days, but the error is still an unsolved mystery. If anyone can tell me why I got the Error 540 on a Mac OS X network, please let me know!

 

 

 

Bryan

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...