[unknown]

Just got this nasty little error message (couple times in the last half hour)

The instruction at "(memory address)" referenced memory at "(memory address)". The memory could not be "written".

Have 4 gig in this machine, running XP...

High grade video card...

running a 22" and a 26" monitor...

Have also been having 'screen refresh' problems, where the screen does not refresh after moving or resizing program screens... Especially in Profile and Adobe... or the newly requested file just does not show, until I resize the screen...

What would you say, some faulty memory?

[unknown]

LogMeIn has this nifty little feature called EventViewer, basically a log of various things happening in your 'puter, such as errors...

Anyhow, scrolled back to the time yesterday, a whole host of messages:

1. An unexpected error has occurred in "Quickbooks": Returning NULL QBWinInstance Handle (about 3 times)

then

2. An unexpected error has occured in "QuickBooks: Premier Accountant Edition":
InitSystem OpenDBSession[4] failed. Error code code 0, msg Succeeded

3. An unexpected error has occured in "QuickBooks: Premier Accountant Edition":
Got unexpected error 5 in call to NetShareGetInfo for path \\Server\data\etc (this one numerous times)

4. An unexpected error has occured in "QuickBooks: Premier Accountant Edition":
QuickBooks has experienced a problem and must be shut down.

5. An unexpected error has occured in "QuickBooks":
Returning NULL QBWinInstance Handle

some more of 1

6. An unexpected error has occured in "QuickBooks: Premier Accountant Edition":
Error: CreateWindow failed. Trying to create a non-modal window of class: MauiReport

Log gives me info back to Feb 5...

had some instances on that date, apparently...


An unexpected error has occured in "QuickBooks":
Returning NULL QBWinInstance Handle

Seems like an almost daily occurrance, but have not noticed the QB connection before...

Seems like this is QB causing my troubles...

[David Blue]

Bert were you restoring a backup when these error happen and your on a server:
or
Was your Server completing an automatic backup.

Both QB and Simply have error problems with servers and backups:

When restoring or making a backup if you do it on the server you will/may cause a crash. "Memory problem cannot read". It will even at
times lock out anybody from accessing the QB or Simply data.

I called both Simply and QB.

From both I received the same answer:

Currently Simply has issues on servers, when backups are being performs, The same answer came from QB.

I am running a L7 processor with 8 gig of muskin ram, etc, etc.

I would check if the errors happened during automatic backup proceedure or if someone was creating or restoring a backup at the time.

All files on the server have to be dragged to the local computer, make backup, cut and paste to flash drive and the drag the file back to the server.

I only spent 15 plus hours with both groups to get to the honest answer.

DB

[unknown]

Dave, these errors do not happen during a backup.

However, I do use the server to do backups...

Cannot say that I have ever had problems making backups in a server environment...

Although, I only use the QB backup protocol when forced to by QB

When will accounting software get into the server age????

I have my backup software set to go at 6 each nite...

so that does not coincide...