JFulford Posted December 18, 2006 Report Share Posted December 18, 2006 I am receving the error Trouble reading files, error -540 (trouble creating service). It is occurring during the backup of three of my raid drives. Other raids on the same machine do not give this error and it occurs after a certain number of files have already been backed up. I am using Retrospect 7.5.285 with driver update and hotfix version 7.5.5.103 and using the latest client. Does any one have any ideas as to what the problem is related to? Even an starting point would be a help. 3 Quote Link to comment Share on other sites More sharing options...
nekr0phage Posted December 21, 2006 Report Share Posted December 21, 2006 This was a bug, it was fixed, you need to update. Quote Link to comment Share on other sites More sharing options...
starbee Posted March 22, 2007 Report Share Posted March 22, 2007 I am receving the same error. I am using Retrospect 7.5.370 with the driver update and hotfix version 7.5.10.104. I tried to do updates but it said I was all up to date. Any other ideas? Quote Link to comment Share on other sites More sharing options...
futureprospects Posted March 24, 2007 Report Share Posted March 24, 2007 After an upgrade from 6.5 I'm having this same problem across five servers running ubuntu 6.06. They all worked reliably on 6.5 We're now using Retrospect 7.5.370 and client version 7.5.112 I've tried removing the retropds.xx file and restarting the client as suggested in some other thread. Is there a fix for this? It's really annoying and there does seem to be a history of this bug. Is it ok to downgrade just the clients to an earlier version that worked or will I lose some functionality? Quote Link to comment Share on other sites More sharing options...
AmyJ Posted April 11, 2007 Report Share Posted April 11, 2007 The error -540 will be addressed in the next update. We don't have an availability date, but hope to have it out soon. Quote Link to comment Share on other sites More sharing options...
UoD Posted April 11, 2007 Report Share Posted April 11, 2007 I had made a post about the same error code this morning (see thread title "error -540 (trouble creating service) and unexpected EOF" thread number : 96030 - 04/11/07 05:46 AM). Will the EOF issue (casuing the error 540) also be addressed? This seems to be happening on any files that are dynamic (files that have a constantly changing size ... especially files that could shrink in size as the backup server is trying to grab them). Quote Link to comment Share on other sites More sharing options...
unitedfuture Posted May 29, 2007 Report Share Posted May 29, 2007 Interesting... I just replied to your post about this issue. Perhaps the threads should be merged? Quote: I had made a post about the same error code this morning (see thread title "error -540 (trouble creating service) and unexpected EOF" thread number : 96030 - 04/11/07 05:46 AM). Will the EOF issue (casuing the error 540) also be addressed? This seems to be happening on any files that are dynamic (files that have a constantly changing size ... especially files that could shrink in size as the backup server is trying to grab them). Quote Link to comment Share on other sites More sharing options...
AmyJ Posted June 4, 2007 Report Share Posted June 4, 2007 These issues are fixed in Retrospect 7.5.387. Please update if you are not running the latest build. Quote Link to comment Share on other sites More sharing options...
sbillis Posted August 22, 2007 Report Share Posted August 22, 2007 I'm still getting the error even when running 7.5.387 with Driver Updates and Hot fixes 7.5.12.103. Is there a Client update also? Quote Link to comment Share on other sites More sharing options...
kluejan Posted September 10, 2007 Report Share Posted September 10, 2007 hi, i have also updated to 7.5.387 and driver hotfix 7.5.12.103 and still getting the same error. i couldn´t find a client update file. regards Jan Quote Link to comment Share on other sites More sharing options...
kluejan Posted September 12, 2007 Report Share Posted September 12, 2007 i check the problem this day again and find out that i got this error if the backup tries to backup files with a ~ in the filename. in this case the backup of this volume ends and log an error 540 (creating service). regards Jan Quote Link to comment Share on other sites More sharing options...
ninman Posted October 2, 2007 Report Share Posted October 2, 2007 I had this problem when I initially upgraded to version 7.5 back in March of 2006. I submitted a service request (SR #1-7495104) and after a few months of troubleshooting received a replacement copy of C:\Program Files\Retrospect\Retrospect 7.5\retropds_linux86.pdu, dated 06/28/2006. This fixed the -540 problem with all my Linux clients. Subsequent Retrospect 7.5.xxx updates installed newer versions of retropds_linux86.pdu. In each case, up to and including 7.5.387, the -540 error returned after installing the update. Restoring the 06/28/2006 version of retropds_linux86.pdu has so far fixed the problem. It would appear that the fix from SR #1-7495104 may not been incorporated in subsequent releases. Todd. Quote Link to comment Share on other sites More sharing options...
JeffFisher Posted October 25, 2007 Report Share Posted October 25, 2007 I'm using the retropds_linux86.pdu from ninman and I'm able to also backup a number of Linux hosts that I haven't been able to back up in ages due to "trouble creating service" errors. When is EMC going to fix this problem? It's a joke that it has been going on this long and has made me question recommending Retrospect to anyone. Quote Link to comment Share on other sites More sharing options...
baxsie Posted January 25, 2008 Report Share Posted January 25, 2008 Interesting. After struggling with the Retrospect "-540 trouble creating service" error on my Linux clients, I came across a certain mysterious retropds_linux86.pdu that seems to fix the Retrosepct 540 trouble creating service errors. Since it was such a challenge to locate the file, I have stashed it here: retropds_linux86.pdu.zip Basically, make a backup of your original file, then copy this file over the one on your Retrospect server Windows box: C:\Program Files\Retrospect\Retrospect 7.5\retropds_linux86.pdu ***** DISCLAIMER ***** I truly do not know the origin of this file. It seems to fix the -540 errors, and generally work. Of course I make no warranty and although I hope it does work well, it might be messed up in some other facet. Hopefully (since it seems appears that this file originated at some point from Retrospect) the Retrospect folks will give us an official download, and an FAQ on fixing this error that is based on something other than forum lore and random downloads of questionable heritage. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted January 25, 2008 Report Share Posted January 25, 2008 Baxsie, I do remember TS providing a file like this to customers a long time ago. Where did you get this specific file from? What is the exact version of Retrospect you are running? Quote Link to comment Share on other sites More sharing options...
baxsie Posted January 25, 2008 Report Share Posted January 25, 2008 Thanks for the reply. > What is the exact version of Retrospect you are running? I'm running what I believe is the latest and greatest: Single Server 7.5.387 HotFix 7.5.13.100 The retropds_linux86.pdu that seems to work (posted above) has this clear text string in it near the start (it is a binary): ULnx7.5.111 The retropds_linux86.pdu that makes the -540 errors (included in some part of the 7.5.387 / 7.5.13.100 install) has this string in it: ULnx7.5.113 The ULnx7.5.113 version basically has less than 50% chance of making it through a backup of a given Linux client. Which makes it pretty much unusable. The ULnx7.5.111 posted above has not thrown a single -540 so far. However, I did get 12 of these errors on one of the four Linux clients: Generated MD5 digest for file "/var/spool/mqueue/dfm0FNcA7L026337" does not match stored MD5 digest. (repeated 11 more times, with various file names) To my understanding, using media verification, it would be impossible to have a MD5 mismatch unless there was a media error in the disk used as the backup destination. The client is not involved in generating or checking the MD5, correct? So there still may be some weirdness in ULnx7.5.111, since the drive I back up to seems to be otherwise stable, and none of the other files in the 669 GB (compressed size on the removable backup disk) of backup threw an error like this. > Where did you get this specific file from? Ummmm . . . let's just say I stumbled across it in a dark corner of the internet where proper gentlemen are not supposed to be seen. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted January 25, 2008 Report Share Posted January 25, 2008 Thank you for being such a good detective. I have opened a new bug based on your information. Quote Link to comment Share on other sites More sharing options...
ninman Posted January 25, 2008 Report Share Posted January 25, 2008 OK. True confession time. See my previous post on this subject (#100421 dated 10/02/07). The working retropds_linux86.pdu, dated 06/28/2006, is one I received from EMC Tech Support on 07/13/2006 in response to SR #1-7495104. Let me know if you need any more details. Todd. Quote Link to comment Share on other sites More sharing options...
baxsie Posted January 25, 2008 Report Share Posted January 25, 2008 EXPOSED! And I was being so coy Quote Link to comment Share on other sites More sharing options...
Mayoff Posted January 25, 2008 Report Share Posted January 25, 2008 Thanks. I am having this investigated to see what is different about the two versions of this file. Quote Link to comment Share on other sites More sharing options...
agblugano Posted February 28, 2008 Report Share Posted February 28, 2008 Ciao everybody, any news on the situation? I have the same problem to and would like to have an official solution. Even the last update (Retrospect version 7.5.508) didn't fix it. Anyway, may i install the .pdu file in this thread with no worries till a fix is provided? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 28, 2008 Report Share Posted February 28, 2008 The PDU file is a good option. We are looking into why the problem keeps getting fixed then breaking then getting fixed and breaking again We will fix it in the next release. Quote Link to comment Share on other sites More sharing options...
smoke_007 Posted March 20, 2008 Report Share Posted March 20, 2008 Thank you so much! I have 3 Linux server that backup every day, but one Linux server that would only backup about 15% of the time. I used this file and I've backed up the last few nights now!! I hope this file becomes part of a standard update release! This thread should be a sticky! Thanks again, Smoke_007 Quote Link to comment Share on other sites More sharing options...
FSim Posted March 29, 2008 Report Share Posted March 29, 2008 Also just want to say thank you to the posters on this thread. Found it via google NOT the search in the forum and it has fixed my problems with Error -540s on our new linux client. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 16, 2008 Report Share Posted April 16, 2008 Just so everyone knows: we have found and fixed this bug. We hope to release a beta for this bug fix in the next week or two. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.