Jump to content

Multi Server 6.5 w/ a 165 MB config65.dat !?!?


Recommended Posts

Howdy,

 

My Retrospect Multi Server (W2K Server, PIV 2.8, 1 GB RAM) has never been stable. Lately

it has been completely unusable. The Retrospect GUI locks after a few minutes although

sometimes backups continue to happen. The last two times I killed the app I got a

assert_log.

 

The log is odd too. Here is a snippet.

 

Code:


 	Quit at 4/22/2005 12:23 PM

 

+ $[15]Retrospect$[16] version 6.5.350

Launched at 4/22/2005 12:24 PM in user account $[1]mppc-int\administrator$[2]

+ Retrospect Driver Update, version 5.4.110

 

+ $[15]Retrospect$[16] version 6.5.350

Launched at 4/22/2005 1:22 PM in user account $[1]mppc-int\administrator$[2]

+ Retrospect Driver Update, version 5.4.110

 

<snip>

 

- 4/22/2005 11:31:51 PM: Copying $[*!20612,,14,+3]Drive C (C:)$[3] on GKIM10503$[4]

4/22/2005 11:31:51 PM: Connected to $[*!20780,,14,+3]GKIM10503

$[*20750] Can't access registry for "$[01]S-1-5-21-131850980-3233613587-1789475758-2135$[02]", error -1101 (file/directory not found)

4/22/2005 11:43:04 PM: Snapshot stored, 44.3 MB

4/22/2005 11:43:08 PM: 1 execution errors

Completed: 8073 files, 809.7 MB, with 29% compression

Performance: 142.8 MB/minute

Duration: 00:11:16 (00:01:00 idle/loading/preparing)

 

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001


 

Are the odd characters because it is Unicode or is that a sign of a problem?

 

Any idea how too avoid this next time? I've been using Retrospect for over ten years but I

haven't been paying as much attention to the program for the last few years.

 

At one point tech support asked me how many storage sets I have. I answered "two" since

that is how many I had in production but I use Retrospect to archive data so I have created

and forgotten about a hundred sets. Does that cause a problem?

 

Is there anyway to get my old client database? There are clients in the database that I don't

know the password for. If I can get Retrospect running on the old config65.dat for long

enough I will change the password but that is not likely.

 

My most important question is how to avoid this next time. I have deleted and recreated the

\Application Data\Retrospect\ directory before (accompanied by a complete reinstall) and the

improvement didn't last. Recreating my scripts and especially readding all my clients is a

long process. I don't want to do it once a month.

 

TIA,

 

Dan

Link to comment
Share on other sites

Hi

 

I'm not sure this is a problem with Retrospect. It looks to me like Retrospect is having trouble due to some problems in Windows.

 

The cant access registry error is documented here

http://kb.dantz.com/article.asp?article=6488&p=2

 

Did the other errors have red marks next to them in the log? If that is the case they are not directly involved with the backup. Retrospect supresses a lot of logging messages but sometimes some extra data will get through. I think that is what is happening in this case.

 

Thanks

nate

Link to comment
Share on other sites

Hi Nate!

 

I’m not concerned about the registry errors. I just left in one backup to show that Retrospect is doing its job on occasion.

 

It is this part that I was wondering about:

Code:


  

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001

MapError: unknown Windows error 998

TProcessToken::SetPrivilege: LookupPrivilegeValueW failed, winerr 998, error -1001


 

Is it normal to have a config65.dat over 100 MB? That seems excessive to me.

 

How can I avoid having it bloat again?

 

The hardest part of rebuilding my config is connecting all the clients. Is there a way to export and import the client database?

 

TIA,

 

Dan

Link to comment
Share on other sites

  • 3 weeks later...

I deleted the config and it worked well for a week but now it is crashing again.

 

This time I have something in the Retrospect log though. The system logs still look good.

 

I have run Memtest and OnTrack and neither have found hardware problems. The "TMemoryappl.gifmhalloc: ignoring exception in OS allocation" part is new to the last run.

 

Any help would be appreciated.

 

Dan

 

Here is the Retrospect log.

 

+ Retrospect version 6.5.350

Launched at 5/19/2005 11:11 AM in user account MPPC-INT\ADMINISTRATOR

+ Retrospect Driver Update, version 5.4.110

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

TMemoryappl.gifmhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

MemPack: HeapValidate failed

MemPack: HeapValidate failed

 

+ Retrospect version 6.5.350

Launched at 5/19/2005 11:15 AM in user account MPPC-INT\ADMINISTRATOR

+ Retrospect Driver Update, version 5.4.110

Link to comment
Share on other sites

Hi

 

I haven't seen this one before:

 

mhalloc: ignoring exception in OS allocation

MemPack: HeapValidate failed

 

At first glance I would say the OS isn't managing memory properly. How much RAM is on this machine again? Are any other programs acting funny?

 

Thanks

Nate

Link to comment
Share on other sites

The machine is a home built with:

P4P800 Deluxe

2.6 GHz PIV (Northwood)

1 GB Crucial in 2 DIMMs

120GB boot drive

6 250GB drives on the various onboard busses

LiteOn LDW-811S (is that supported?)

 

I have a twin (minus the storage drives) that was built the same week and has never had a problem.

 

It is rock solid other than Retrospect. When Retrospect is acting up the OS and other applications respond fine. Deleting the config file and reconfiguring gets it working for a while. Last time it was about a month.

 

I can run Memtest or OnTrack overnight without a problem. I'm running SANDRA now and it seems OK.

 

The next test will be to install 6.5 on another machinge and see if the problems follow the config file. I can't find my 6.5 installer though. Can you point me to one?

 

Would you like the config file to see how it acts for you?

 

Dan

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...