Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Journal Archive 64 bit conversion with errors

Created: 18 Feb 2014 • Updated: 16 Apr 2014 | 4 comments
This issue has been solved. See solution.

Hi All,

I recently finished converting my journal archive to 64bit as part of the 9->10 upgrade process. When it finished the process It returned:

Items Added: 7658826

Items missing content: 6497

Items with errors: 2715

Status: warnings

Is this somethign to be concerned about? How do I 'finish' the upgrade to 64 bit? I guess this window just doesnt give much information and I was hoping the communitiy could fill me in a bit!

Thanks!

Operating Systems:

Comments 4 CommentsJump to latest comment

GabeV's picture

Hello Nate,

If you open the Monitor Indexing Tasks window > click in the Task's name > click in the Archive Name, you should see a button called "Open Report File" that will tell you what happened with those items (missing content and errors). That would be the first step. You can post some of the entries here so we can help you.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

Nate.D's picture

I am not 100% sure what the errors are, they arent very descriptive but I saw some like this:

7372069    Unavailable    Unavailable    102    enqueueid:7372069,
vsekey:7372069,
url:7372069#crct,
state:error,
siphoned:aborted,
orphaned:false,
warning:none,
error-msg:
---enqueueid:7372069,
vsekey:7372069,
url:7372069#cont,
state:error,
siphoned:aborted,
orphaned:false,
warning:none,
error-msg:
---enqueueid:7372069,
vsekey:7372069,
url:7372069,
state:error,
siphoned:aborted,
orphaned:false,
warning:none,
error-msg:
---enqueueid:7372069,
vsekey:7372069,
url:7372069#pvid,
state:error,
siphoned:aborted,
orphaned:false,
warning:none,
error-msg:
---enqueueid:7372069,
vsekey:7372069,
url:7372069#afid,
state:error,
siphoned:aborted,
orphaned:false,
warning:none,
error-msg:
---enqueueid:7372069,
vsekey:7372069,
url:7372069#custom,
state:error,
siphoned:aborted,
orphaned:false,
warning:none,
error-msg:
---

And many entries like this, where I assume the conversion stopped and then started;

12/02/2014 16:18:19 The upgrade paused as it reached a checkpoint.
12/02/2014 16:18:24 The upgrade has resumed its processing.

12/02/2014 16:40:34 The upgrade paused as it reached a checkpoint.
12/02/2014 16:40:39 The upgrade has resumed its processing.

12/02/2014 17:01:50 The upgrade paused as it reached a checkpoint.
12/02/2014 17:01:55 The upgrade has resumed its processing.

If I was helpful in solving your issue please mark my post with a thumbs up or a solution!  Have a great day :)

Nate.D's picture

It looks like a missed a portion of this error:

SeqNo    SSID    URL    Error Code    Raw Error
3700918    Unavailable    Unavailable    102    enqueueid:3700918,

I also noticed a user having the exact same issue here: https://www-secure.symantec.com/connect/forums/ev1...

It looks like I may need to open a case with support.

If I was helpful in solving your issue please mark my post with a thumbs up or a solution!  Have a great day :)

SOLUTION
GabeV's picture

Nate,

Open a case with support, the fact that the SSID and URL are 'unavailable' seems to be an issue trying to locate the SSID from the indexing engine.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill