cancel
Showing results for 
Search instead for 
Did you mean: 

StorageArchive.exe failures at logon?

Brian_Day
Level 6
Is anyone else getting a lot of hard stops for StorageArchive.exe on their EV boxes. We seem to get numerous in a row popping up when logging into the box. All the same exactly description.

Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 10/19/2007
Time: 10:08:57 AM
User: N/A
Computer: servername
Description:
Reporting queued error: faulting application StorageArchive.exe, version 7.5.0.1250, faulting module msvcr80.dll, version 8.0.50727.762, fault address 0x0004ff28.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 53 74 6f ure Sto
0018: 72 61 67 65 41 72 63 68 rageArch
0020: 69 76 65 2e 65 78 65 20 ive.exe
0028: 37 2e 35 2e 30 2e 31 32 7.5.0.12
0030: 35 30 20 69 6e 20 6d 73 50 in ms
0038: 76 63 72 38 30 2e 64 6c vcr80.dl
0040: 6c 20 38 2e 30 2e 35 30 l 8.0.50
0048: 37 32 37 2e 37 36 32 20 727.762
0050: 61 74 20 6f 66 66 73 65 at offse
0058: 74 20 30 30 30 34 66 66 t 0004ff
0060: 32 38 28

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1001
Date: 10/19/2007
Time: 10:08:54 AM
User: N/A
Computer: servername
Description:
Fault bucket 501879929.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 35 30 31 38 37 39 39 32 50187992
0010: 39 0d 0a 9..
6 REPLIES 6

Maynard_K
Level 6
Employee
Are you using some sort of 3rd party Migration tool?  If so, log a call with Symantec support.  This has been occuring rather frequently as of late.

Brian_Day
Level 6
Tricky question. For the users enabled in EV, no 3rd party tool was used on them, but there are many other users in Exchange which were migrated in using Quest migration tools.

Maynard_K
Level 6
Employee
Sounds like the ol' notorious SELF attribute has once again surfaced.  ADModify will do the trick but may I recommend a case be opened with support as they are able to guide you through this process.

Brian_Day
Level 6
Is the problem with SELF being on or off? We have cases in our environment where the SELF permission has to be given for certain Exchange/Outlook functionality. I'll open another case on Monday.

Maynard_K
Level 6
Employee
The problem is that when this Quest tool performs a synch, the SELF attribute is modified before the synch and not set back the way it was once this synch occurs.  By using ADModify, you can bulk remove this affected attribute, and add it in again as it will need to be included for normal functionality of your accounts.  Words of wisdom, log a call with support.

Michael_Bilsbor
Level 6
Accredited
Hi,
 
I'd be interested if it was the SELF issue as I thought that affected the agent, not aware it affected StorageArchive.