Closed EAM 12.0.0.6716 BETA Access Fault

[Hiballer]

Just got this today in the afternoon:

 

 

32-bit machine. Unfortunately, I was not running with debug logging enabled. And, by the way, the update logging problem has not been cured. They are all showing "\manual Update" and "Unknown update error" same as version 11.

 

I DO realize this is BETA, so all I am doing is reporting.

 

Bill

[Hiballer]

Thanks for moving this. I didn't realize there was a Public area for BETAs.

 

This morning, the logs were correctly displayed. Now running BETA 6723.

 

Bill

[Frank H]

Hi,

 

We still have that update log issue under investigation and (probably) is not fixed yet.

it is a very rare issue, debuglogs do not help and we cannot reproduce it.

 

Do you remember what you were doing when that Access violation showed ?

 

Thanks

[Hiballer]

Actually, I was down in the basement working on a project and when I came back up and wiggled the mouse to kill the screensaver, there it was. It had not just popped up. It had been there for a while.

 

However, I got this from the Event Viewer, Administrative Events. it was repeated exactly the same three times.

Log Name:      Application
Source:        a2service.exe
Date:          09/18/2016 01:00:12
Event ID:      0
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Prinserver
Description:
The description for Event ID 0 from source a2service.exe cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Access violation at address 00390FEF. Write of address C0000000

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="a2service.exe" />
    <EventID Qualifiers="0">0</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-09-18T05:00:12.000000000Z" />
    <EventRecordID>16610</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Prinserver</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Access violation at address 00390FEF. Write of address C0000000</Data>
  </EventData>
</Event>

:

 

Bill

[Hiballer]

Now using version 6723.

 

The non-update bug is back. I am informed this evening that my EAM has not updated in 2 days, yet I have it set for every 4 hours. This is the 32-bit computer. For some reason, the 64-bit machine is running without this problem.

 

After a manual update, I am now running version 6731

 

Bill

[Frank H]

Thanks.

 

If you think you suffer from issues, pls enable debuglogging, try to reproduce ot wait until it reproduces  and sendus the logs.

 

Thanks !

[Hiballer]

So far, version 6740 repeat 6740 on both my machines seems to be working pretty well. I haven't had any crashes yet. I've been running with debug logging enables all along just in case.

 

Bill

[Frank H]

Nice to hear-

We just released 6752 repeat 6752.

 

Looking forward to your feedback, thanks !

[Hiballer]

Hmmm. Just noticed that my 32-bitter says it hasn't updated in 19 hours. I have it set for every 4 hours. I'll do a manual and get the new version.

 

 

EDIT: got it!

 

Bill

[Hiballer]

Bad news! When I tried to update my 64-bitter to 6754 the earlier version froze up badly. It crashed so hard that it froze my entire desktop with the "tell us what happened" dialogue box on the screen. The mouse would disappear inside the box and outside NO click would register with the OS (Windows 7 Ultimate 64-bit). I had to hold the power button to recover, which is never a good thing.

 

I am now running version 6752 and it seems to have recovered. The problem being that I was in the middle of a 65GB transfer from one disk to another, which also came to a screeching stop. Now I will have to do the whole thing over again.

 

Bill

[Frank H]

Thanks.

Please note that running beta software on a production machine is a bad idea.

Betas contain bugs and may cause issue. This is why we release a new beta every day until public beta will be released (update from 11 to v12)

 

Thanks

[Frank H]

Did you have debuglogging enabled during the crash ?

[Hiballer]

Yes, debugging was enabled, and I was advised to run the BETA on my 64-bitter here in this forum. Fortunately, the copy software remembered where it was as continued the copy from the point at which the machine froze.

 

Debugging logs are usually quite large even when zipped, but I can send them via email if required.

 

Bill

[Frank H]

ok that's good, you can send me a pm with the zipped logs.

 

thanks

[Hiballer]

Will do.

 

Bill

[Frank H]

Thanks, we are still investigating the issue.

[Frank H]

Hi Hiballer.

the crash issue should have been fixed in beta build 6786.

 

Thanks for your feedback and help.