PM 5 Beta Fails to Start

[Kirk Baker]

Beta 2 fix does not work I am afraid. 

Really?  What kind of error message are you getting now?  Screen shots are helpful.  Use the 'Attachments and other options' link when you're composing your reply to this message and there you'll be able to upload your JPEG format screenshot.

Thanks,

-Kirk

[rahendo]

Beta 2 working OK for me so far. No problems after about 10 starts and use.

[boltoch]

Kirk

Thanks for the excellent support Beta V2 working fine for me.

Regards

Chris

[NeilR]

Beta2 fixed my problem, as I indicated in my duplicate thread.

I did notice, just before learning about Beta 2,  that if I ran PM5 normally it would (maybe) briefly display the splash screen before disappearing without any warning and leaving Kirk nothing to investigate.

If, however, I right clicked the shortcut or icon and "Ran as Administrator" *then* I would get the crash screen posted above, with instructions to send via internet to Camerabits.  The automatic send did not work but I assume it saved the crash file somewhere.  I didn't investigate that piece because within 5 minutes I was on beta2.

I was logged in with Administrator level privileges throughout my test.

So, Frank and any others still having issues might want to try "Running as Administrator" if they are not getting any crash data for Camerabits.  This is Windows, of course.

[greyhoundx]

I just downloaded and installed PM 5 Beta 2 and nothing happens when I try to start it - no splash screen - nothing, even when right clicking to run as administrator. The errorlog.txt file is empty. I never had the PM 5 Beta 1 installed. I do have PM 4.6.9 installed and running fine. Windows 7 SP1 64-bit - 8 GB RAM.

Windows application event log - General and Details:

Faulting application name: Photo Mechanic.exe, version: 5.0.0.0, time stamp: 0x4ff78907
Faulting module name: WRusr.dll, version: 8.0.1.203, time stamp: 0x4fefd362
Exception code: 0xc0000005
Fault offset: 0x00013210
Faulting process id: 0x1990
Faulting application start time: 0x01cd5f2085fb2f60
Faulting application path: C:\Program Files (x86)\Camera Bits\Photo Mechanic 5\Photo Mechanic.exe
Faulting module path: C:\Windows\system32\WRusr.dll
Report Id: c3e5bd40-cb13-11e1-97bd-005056c00008


- System
  - Provider
   [ Name]  Application Error
   - EventID 1000
   [ Qualifiers]  0
    Level 2
    Task 100
    Keywords 0x80000000000000
   - TimeCreated
   [ SystemTime]  2012-07-11T04:49:15.000000000Z
    EventRecordID 66394
    Channel Application
    Computer Rick-PC
    Security
 - EventData
   Photo Mechanic.exe
   5.0.0.0
   4ff78907
   WRusr.dll
   8.0.1.203
   4fefd362
   c0000005
   00013210
   1990
   01cd5f2085fb2f60
   C:\Program Files (x86)\Camera Bits\Photo Mechanic 5\Photo Mechanic.exe
   C:\Windows\system32\WRusr.dll
   c3e5bd40-cb13-11e1-97bd-005056c00008

Looks like the WRusr.dll is part of Webroot's SecureAnywhere product - 1 of 3 anti-malware programs I run in real-time, which PM 4.6.9 has no problem with:

http://community.webroot.com/t5/tkb/articleprintpage/tkb-id/WSA-C@tkb/article-id/1

[heavymeister]

PM 5 beta does not open at all on a Win XP machine at work
Tried reinstall and reboot etc. a couple of times to no avail.

On my MacBookAir with OS 10.7.4 it runs fine except after a couple of hours browsing through a folder with 1800 files the thumbnails show "Unable to render image".

I am missing the "Sharpen" checkbox in the "Send via Email" dialogue. Can you please add this again?

Thanks,
HM

[Kirk Baker]

PM 5 beta does not open at all on a Win XP machine at work
Tried reinstall and reboot etc. a couple of times to no avail.

PM5 does not support Windows XP.  Unfortunately the installer isn't preventing it from being installed.

On my MacBookAir with OS 10.7.4 it runs fine except after a couple of hours browsing through a folder with 1800 files the thumbnails show "Unable to render image".

Sounds like you have Public Beta 1.  Public Beta 2 should not have this issue.

I am missing the "Sharpen" checkbox in the "Send via Email" dialogue. Can you please add this again?

I'll look into it.  If it's missing it's unintentional.

-Kirk

[Kirk Baker]

I just downloaded and installed PM 5 Beta 2 and nothing happens when I try to start it - no splash screen - nothing, even when right clicking to run as administrator. The errorlog.txt file is empty. I never had the PM 5 Beta 1 installed. I do have PM 4.6.9 installed and running fine. Windows 7 SP1 64-bit - 8 GB RAM.

Looks like the WRusr.dll is part of Webroot's SecureAnywhere product - 1 of 3 anti-malware programs I run in real-time, which PM 4.6.9 has no problem with:

Can you try disabling SecureAnywhere temporarily and see if that makes any difference?

-Kirk

[greyhoundx]

Hi Kirk - never mind, the gremlin is gone.    Right after my post I had tried it with SecureAnywhere off, same problem. Right before I shutdown for the night I downloaded the latest Windows 7 updates. Booted up a short bit ago, saw your prompt reply, turned off SecureAnywhere and got the startup screen. Entered my demo code, everything is fine. Turned on SecureAnywhere, started up PM 5 again, everything is fine. Like my users tell me so often - it wasn't working, honest ! Sorry, I should have given the gremlin time to move along before reporting. 

PM 5 looks great ! Thanks for the prompt response and all your hard work. Congrats on the new release.

[greyhoundx]

Sorry Kirk, but it's back. I downloaded and installed Beta 3 on Friday, but once again it won't even try to start when Webroot SecureAnywhere is running. If I shut down SecureAnywhere, then PM 5 Beta 3 will run. This time I waited to see if the issue would persist after rebooting/shutting down, which it has.

But PM 4.6.9 and all the previous versions do not have this problem, they start right up, no problem with Webroot SecureAnywhere running. I have tried running PM 5 Beta as Administrator, but it still fails. I have added "photo mechanic.exe" to explicity allow it in SecureAnywhere but no difference, PM 5 Beta 3 fails to even display a splash screen when Webroot SecureAnywhere is running.

Exact same info in the Windows 7 SP1 64-bit application log, as when I had this issue for a bit with Beta 2:

Faulting application name: Photo Mechanic.exe, version: 5.0.0.0, time stamp: 0x5000cbec
Faulting module name: WRusr.dll, version: 8.0.1.203, time stamp: 0x4fefd362
Exception code: 0xc0000005
Fault offset: 0x00013210
Faulting process id: 0x16f50
Faulting application start time: 0x01cd630332999c80
Faulting application path: C:\Program Files (x86)\Camera Bits\Photo Mechanic 5\Photo Mechanic.exe
Faulting module path: C:\Windows\system32\WRusr.dll
Report Id: 73b9b2e0-cef6-11e1-b17e-005056c00008

- System
  - Provider
   [ Name]  Application Error
  - EventID 1000
   [ Qualifiers]  0
   Level 2
   Task 100
   Keywords 0x80000000000000
  - TimeCreated
   [ SystemTime]  2012-07-16T03:29:30.000000000Z
   EventRecordID 67297
   Channel Application
   Computer Rick-PC
   Security
- EventData
   Photo Mechanic.exe
   5.0.0.0
   5000cbec
   WRusr.dll
   8.0.1.203
   4fefd362
   c0000005
   00013210
   16f50
   01cd630332999c80
   C:\Program Files (x86)\Camera Bits\Photo Mechanic 5\Photo Mechanic.exe
   C:\Windows\system32\WRusr.dll
   73b9b2e0-cef6-11e1-b17e-005056c00008

[Kirk Baker]

Sorry Kirk, but it's back. I downloaded and installed Beta 3 on Friday, but once again it won't even try to start when Webroot SecureAnywhere is running. If I shut down SecureAnywhere, then PM 5 Beta 3 will run. This time I waited to see if the issue would persist after rebooting/shutting down, which it has.

But PM 4.6.9 and all the previous versions do not have this problem, they start right up, no problem with Webroot SecureAnywhere running. I have tried running PM 5 Beta as Administrator, but it still fails. I have added "photo mechanic.exe" to explicity allow it in SecureAnywhere but no difference, PM 5 Beta 3 fails to even display a splash screen when Webroot SecureAnywhere is running.

Exact same info in the Windows 7 SP1 64-bit application log, as when I had this issue for a bit with Beta 2:

Faulting application name: Photo Mechanic.exe, version: 5.0.0.0, time stamp: 0x5000cbec
Faulting module name: WRusr.dll, version: 8.0.1.203, time stamp: 0x4fefd362
Exception code: 0xc0000005
Fault offset: 0x00013210
Faulting process id: 0x16f50
Faulting application start time: 0x01cd630332999c80
Faulting application path: C:\Program Files (x86)\Camera Bits\Photo Mechanic 5\Photo Mechanic.exe
Faulting module path: C:\Windows\system32\WRusr.dll
Report Id: 73b9b2e0-cef6-11e1-b17e-005056c00008

- System
  - Provider
   [ Name]  Application Error
  - EventID 1000
   [ Qualifiers]  0
   Level 2
   Task 100
   Keywords 0x80000000000000
  - TimeCreated
   [ SystemTime]  2012-07-16T03:29:30.000000000Z
   EventRecordID 67297
   Channel Application
   Computer Rick-PC
   Security
- EventData
   Photo Mechanic.exe
   5.0.0.0
   5000cbec
   WRusr.dll
   8.0.1.203
   4fefd362
   c0000005
   00013210
   16f50
   01cd630332999c80
   C:\Program Files (x86)\Camera Bits\Photo Mechanic 5\Photo Mechanic.exe
   C:\Windows\system32\WRusr.dll
   73b9b2e0-cef6-11e1-b17e-005056c00008

Prior to you telling me about this issue, I had never heard of Webroot SecureAnywhere before.  I can tell you that we have no code that explicitly tries to keep anti-virus software from working with PM.  You'll have to take it up with the Webroot folks.

I can tell you that we have switched to Microsoft's latest VisualStudio development environment and we're using their latest Microsoft Foundation Classes for all of our Windows programming, but other than that, PM 5 is mostly PM 4.6 with a lot of new features.  I don't think that using the latest MFC or VisualStudio should cause problems for any anti-virus software, but who knows?

PM 5 does not need to be run as an Administrator.

I looked up WRusr.dll and it belongs to Webroot.  Why is it trying to get linked up with Photo Mechanic 5?  If it would just stop trying to connect itself to PM, I'm sure the problem would stop.

-Kirk

[greyhoundx]

Thanks Kirk. Webroot has been around since 1997, and the previous product  - Spy Sweeper - since 2002. SecureAnywhere is the latest offering, starting last year:  http://en.wikipedia.org/wiki/Webroot

I'll communicate to Webroot what is happening. My only concern is that it has never interfered with PM 4.6.x - even now 4.6.9 works fine with Secure anywhere running, only PM 5 has a problem. So they may argue that something in PM 5 has changed, but we'll see.

I'll let you know what I find out. Thanks.

[Kirk Baker]

Thanks Kirk. Webroot has been around since 1997, and the previous product  - Spy Sweeper - since 2002. SecureAnywhere is the latest offering, starting last year:  http://en.wikipedia.org/wiki/Webroot

I'll communicate to Webroot what is happening. My only concern is that it has never interfered with PM 4.6.x - even now 4.6.9 works fine with Secure anywhere running, only PM 5 has a problem. So they may argue that something in PM 5 has changed, but we'll see.

I'll let you know what I find out. Thanks.

I just don't have any idea what I can do to make some third party software happy when it decides to inject itself into my application.  How could I address that?  Their DLL is crashing, not Photo Mechanic.  (At least that's what I see from your crash reports.)

-Kirk

[greyhoundx]

They replied to me that they checked the logs (since it's cloud based !?!) and then white-listed the application. That was 2 days ago and it's been working since. Thanks for your input.

[Frank]

Beta 2 fix does not work I am afraid. 

Really?  What kind of error message are you getting now?  Screen shots are helpful.  Use the 'Attachments and other options' link when you're composing your reply to this message and there you'll be able to upload your JPEG format screenshot.

Thanks,

-Kirk

Just tried PM5 again and it works fine now gremlin seems to have gone.

Thanks again for your help.