Power Agent Issues

Scott Alexander

I just recently upgraded to a new laptop computer (windows 7, 64-bit), right about the same time I got my Joule/Quarq installed.

On this new computer, setting up the Joule wasn't a problem with Power Agent before, but now I cannot get PA to open any longer.

I get the following error code. Windows offers two options: 1) search the internet for a possible solution (which it never comes back with one), or 2) close the program.

Problem signature:

Problem Event Name: APPCRASH

Application Name: poweragent.exe

Application Version: 0.0.0.0

Application Timestamp: 456c61c8

Fault Module Name: msvcrt.dll

Fault Module Version: 7.0.7600.16385

Fault Module Timestamp: 4a5bda6f

Exception Code: c0000005

Exception Offset: 00018dbd

OS Version: 6.1.7600.2.0.0.768.3

Locale ID: 1033

Additional Information 1: 0a9e

Additional Information 2: 0a9e372d3b4ad19135b953a78882e789

Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Anyone have ANY idea what's going on here?

TerryO

Ever since I got my new, windows 7, 64 bit laptop, I have had nothing but problems with PA and Joule. I have the same setup with computer and Joule/Quarq. When you installed PA, did you download the latest version and install that? You could try an uninstall/reinstall. Have you had any other problems? Not to hijack the thread, but what happens when you plug in your Joule? Does it assign it a drive letter? Mine gets assigned two drive letters - E and F - and it takes forever (like 5 minutes with circle spinning). Then it takes PA like 4 minutes after clicking device download to show the Joule and longer to download the workout. I prefer to use training device download from WKO+ and same problem. Takes forever and crashes it half the time. Garmin works perfectly and both worked fine on Vista before new computer. Do you have any of these other issues? Saris and TP have been worthless. "Do I have the latest firmware?" - duh?!?!?!

Scott Alexander

I've tried the uninstall/reinstall method several times, going between C:/Program files and C:/Program Files (x86) - whatever in the heck that directory is!!!

Yes, Windows brings up an autoplay window too, when I plug in the Joule, and assigns it a drive letter. I've never checked to see if it assigns more than one.
Yes, I have the latest version PA as well. But, without PA, I cannot see if I have the latest firmware on the Joule or not.

The first few times I was playing with the Joule/PA it wasn't a problem, but now it seems to be. WTF?!?

My computer combo has never taken 4+ minutes for downloading tho, that's new to me.

TerryO

I was bored so I googled it. These errors are usually caused by viruses/spyware or registry errors. The malware is often from recently downloaded corrupt programs. Suggestions include running a full, thorough, virus and spyware scan and removing any newly downloaded software which could have caused the problem. If that doesn't work, you could try a system restore back to the last restore point before it stopped working. You can also inexpensively purchase software that identifies and corrects registry errors and other problems. I think that's what I'm going to do on my laptop today.

Scott Alexander

Posted By Terry Olivas on 16 Jun 2011 01:29 PM

You can also inexpensively purchase software that identifies and corrects registry errors and other problems. I think that's what I'm going to do on my laptop today.

What software? Never heard of this because I've never had this problem.

 

Scott Alexander

For what it's worth, I found this link: pcsupport.about.com/od/findbyerrorm...-error.htm, that showed to run the "sfc /scannow" command from the run/command prompt.

I did it, and I no longer receive the 'can't start' error, but instead I get no error at all, and PA still doesn't start up.

One thing or another...UGH.

I'm still trying to figure out why some stuff you have to "run as administrator" and others you don't. Win 7 is frustrating me to say the least.

Scott Alexander

@Terry, today I paid attention when uploading my ride, and my Joule was assigned both E and F drives, like you mentioned. It also took longer to upload today - but that might be due to the fact that my ride today was 65 miles (my longest yet w/ the Joule).

Bomber

I just reinstalled my laptop a few days agp (XP) and had problems with the Power Agent... luckily I had an older version os the power agent set-up in mt back-up files, and that worked without any problems...
So, it looked to me as if it is the new version of the Power Agent that has issues..

TerryO

@Scott - believe me, it's not the ride. When I had my previous computer, it loaded all rides fast.

@Bo - how did you reinstall the previous version? Did you uninstall then reinstall the older version? Is there any way you could send me the older version so I could try?

Scott Alexander

@Bo, I'm willing to try anything at this point, if you have the older version. Maybe drop it into a box.net or similar account for us to use?

gonnzo

@Scott - I had different issues PA and Win7 (16bit) a couple of months ago and got fantastic support from Saris. They didn't have the answer right away, but kept working on it consistently over 2 weeks until they got it. I highly recommend you contact them. That solution was posted here, though it sounds quite different from the problems you're having. http://endurancenation.us.dnnmax.com/Training/TrainingForums/tabid/101/afv/topic/aff/26/aft/5383/Default.aspx



Send them an email, you might get lucky.

Scott Alexander

Was pulling up the CycleOps/Saris website to call them today about why PA didn't start up in W7 64-bit.

And, voila, PA started up! Have no idea what's different now than the last time (have had a few windows updates since then, but that's it).

TerryO

@ Scott - I think I just fixed mine. Will test my solution out again tomorrow and repost.

TerryO

OK. I figured it out. With the Joule plugged in, after it shows that it is on E: and F:, go to device manager, go to disk drives. There will be 2 Joules. Go to the second one and right click it then click disable. Problem solved. Back to working with TP device agent and Power Agent smoothly.

DCorso

 @Scott - you may need to set the compatibility settings for any 32-bit app that doesn't behave properly in W7 64bit.  Right click on the shortcut, comapibility tab and adjust.