After Driver Update 8.1 "Not Connected"

[Paul Ripley]

I just downloaded and installed the 8.1 driver update. I logged out and back in and opened Retrospect. Now I'm getting the dreaded 127.0.0.1 and "not connected".

 

I reinstalled the 8.1 engine and restarted the computer. The "Launch on system startup" box was checked. I opened the Retrospect pref pane, and it shows that the engine is stopped. I cannot start the Retrospect engine using the pref pane.

 

Any suggestions?

[Paul Ripley]

I uninstalled Retrospect and then reinstalled the console and the engine. Everything was working properly.

 

After following the installation instructions for the Driver update, again I could no longer turn the engine back on.

 

I went through the uninstall-reinstall-install driver update three times. The engine cannot be turned back on with the driver update in the Application Support/Retrospect folder.

 

I give up.

 

Mac Pro 2008; 10.6.3

[rhwalker]

Well, because you haven't provided any information about the version of Retrospect engine (8.1.x.x) or Retrospect console (8.1.x) that you have installed and uninstalled so many times, there's really not any way that we can begin to help.

 

It may be that the RDU was only tested with certain versions of the Retrospect engine.

 

Without information, I give up too.

 

Russ

[Paul Ripley]

Well, because you haven't provided any information about the version of Retrospect engine (8.1.x.x) or Retrospect console (8.1.x) that you have installed and uninstalled so many times, there's really not any way that we can begin to help.

 

It may be that the RDU was only tested with certain versions of the Retrospect engine.

 

Without information, I give up too.

 

Russ

 

 

Gosh Russ,

 

I'm using the last released version, Retrospect-81626, that I downloaded on 11/10/09. If you have something more recent, please enlighten the rest of us poor souls.

 

There was NOTHING in the release notes about which versions of the engine were compatible /tested. I would guess that would be appropriate information. You think?

 

Now that you have the information, let's hear your intelligent response. Waiting...

[rhwalker]

Good luck with that attitude. Apparently you don't understand how these user-to-user support forums work.

 

This is not just for YOUR personal benefit, but for the benefit of others with your same problem.

 

Months down the road, when others are researching their problems, they won't have a clue whether the suggestions you were (or might be) given are applicable to their situation or not. These posts last for years. Updates do come. For anyone researching their problem, looking at your original post, won't have a clue (nor did I) what version you were using.

 

And it is common that users post in these forums, insisting that they have the "latest" version, when they don't.

 

Or, it may just be that you don't know how to write a bug report or to request help. If that's the case, then I am sorry that you were offended.

 

Good luck,

 

Russ

[Paul Ripley]

Ross,

Even after I supplied the information you requested, you still provided zero help.

 

Maybe it's time for you to move out from mommy and daddy's house.

 

 

[whgiii]

I had the same problem, so removed the newly installed driver update. That was the only way I could get the engine running again.

[Tree]

If one can carefully read around the attitudes and posturing, what might be beneficial to future readers of this thread would be to point out a few things.

 

First, Russ asked that the specific version be provided, both of Engine and Console. This is for posterity, sure, so that others can find solutions pertaining to their particular installation. But it also requires of the original poster that they confirm the version number for both of these elements. Why is that crucial? Because they are two separate animals and it could very well be that a mismatch in version numbers between Engine and Console is the whole reason for the problem.

 

I hate it that we have to basically update "twice" whenever a new release comes out, but that's what it amounts to. The automatic updating built into the Console's operation will get the Console updated... but not the engine. For that, one must download and update manually. Extremely inelegant, frustrating to users, and a built-in source of problems that EMC desperately needs to change. But that's how things work now.

 

Once EMC does release a version that handles updating better, then this post will become irrelevant to users who employ the new version. That's why we need to carefully report that we're talking about version 8.1.626.

[rhwalker]

Once EMC does release a version that handles updating better, then this post will become irrelevant to users who employ the new version. That's why we need to carefully report that we're talking about version 8.1.626.

It's also why EMC needs to fix the Console interface so that it reports the version of each engine that the console sees. It's confusing and difficult for new users to learn how to drill down into the engine package on the engine machine and find the right file so that the engine version can be reported. Ever since the beginning (what, two years ago) of the (still ongoing?) beta test period, it's been requested that the console be able to report the version of each engine. Yes, if the engine is working well enough to be able to log the version in the logs, you can get the information that way, or in the numerous crash reports that are so readily available.

 

I'm sure that some feel I have an "attitude", but I really don't. I'm just trying to provide efficient help.

 

The following links may be useful to newcomers - they were frequently provided by Walt Reed, formerly of Retrospect tech support years ago, who is missed:

How to ask questions the smart way

Be precise about your problem

 

See also:

How to report bugs effectively

 

Russ

[CallMeDave]

Even after I supplied the information you requested, you still provided zero help.

 

Perhaps because the post didn't include even a whit of apology for your sarcastic and confrontational message ([color:gray]"let's hear your intelligent response. Waiting... "[/color])

 

Maybe it's time for you to move out from mommy and daddy's house.

 

Russ happens to be a partner in an established American law firm. I don't know if he's smarter then you are, but for sure he's smarter then I, and even I have every intention of eventually moving out of the basement, as soon as the Cheetos run out!

[CallMeDave]

The engine cannot be turned back on with the driver update in the Application Support/Retrospect folder.

 

Using [color:purple]RetrospectEngine.bundle 8.1.626.1[/color] (Monday, November 9, 2009 10:10 AM) on an iMac G5 (OS X Server 10.5.8), I am able to successfully start the engine with the newly released RDU ("Driver Update and Hot Fix, version 8.1.1.103").

 

I did have an existing .rpx file on the folder ("rdu.rpx") dated July 31, 2009 that resulted in an error written the Operations Log until I removed it. Suggest you check the contents of the files in the Application Support/Retrospect folder to look for conflicting items.

 

 

Dave

[whgiii]

I suspect that I also have a file conflict since I cannot get the engine to start after installing the driver update. How do I go about identifying the conflicting file?

[CallMeDave]

How do I go about identifying the conflicting file?

 

I'm guessing that there needs to be only one ".rpx" file of any name. That should be your first investigation.

 

Other then that, you can probably get by with only:

 

- config80.bak (will make itself)

- config80.dat

- operations_log.utx (will make itself)

- retro.ini

- Retrospect 8.1 Driver Update.rpx

- RetrospectEngine.bundle

- RtrExec.dir/

[whgiii]

My Retrospect Folder matches your list with one exception: I have a file "assert_log.utx" What is that? Also, I was able to find an rpx file (noam.rpx), but only if I open the Package Contents of RestrospectEngine.bundle. Should I mess with that?

[CallMeDave]

Should I mess with that?

 

It's tempting for me to say "yes, delete that file" and then chuckle that you'd take such advice from a guy living in his mommy's house, but even _I_ have some scruples!

 

Since you've already reinstalled the Engine, perhaps it's time to ask if you've re-downloaded the driver update file?

 

Are you getting anything in your System or Console logs when you try and start the Engine?

 

You haven't described the hardware you are using; this would probably be the time for a thorough listing.

 

Dave

[whgiii]

I have tried reinstalling the engine and the driver update. Regardless, the engine will not restart after following instructions to add the driver update. The only way to get the engine going again is to remove the driver update. I'm not sure where to look for the information you requested from console or system logs. What specific hardware info would you like? Thanks for sticking with me on this!

[olli]

I have the same problem. This is on a Mac Pro 3,1; Snow Leopard 10.6.3. Here is what I have found:

 

- The driver update is the only .rpx file contained in the /Library/Application Support/Retrospect folder.

 

- The operations_log.utx and assert_log.utx files do not list any information regarding the crash, even nothing about the start attempt of the engine.

 

- The kernel extension got loaded - you have to manually unload it before you can start the engine again after the removal of the driver update.

 

- However, while the update is installed, you cannot start the engine.

 

Please find attached the information I could pull from the system after the crash: an excerpt from my system.log and the corresponding crash report. That is all there is.

 

I hope this is helpful.

[whgiii]

Since I have given up trying to install the driver update (for the same reasons that you describe), please post any solutions that you find. Thank you.