Troubles Posting

[vivian3]

We currently have Great Plains installed and recently one of the machines has had trouble "posting". The computer can post one record at a time- usually. However if there is more than one to post it will not work.

The error we receive is this: Failed to close table.

Then in order to complete the post the user has to log out of her system and go to our server computer, go to batch recovery and complete the posting there.

Does anyone have any idea on how this problem would come about or how I can fix it?

Thanks

 

[jazgeek]

1 things to try

1. is the problem machine or user specific (try on another machine with the user logged in)
2. destroy and recreate odbc connection on bad machine
3. uninstall tcp/ip as a protocol - reboot - reinstall on bad machine
4. change Network card on bad machine


if the answer to number 1 is user related, delete and recreate the user in great plains.



-----------
and they wonder why they call it Great Pains!

jaz

 

[vivian3]

ok,

We can log onto our server computer and post from there, but we cannot post from her machine or our accounts receivable machine. (all logging on as her user) Our accounts receivable can do everything she needs to do from her machine tho.

I don't think it'd be the network card because she can log onto our server and run our access databases perfectly fine.

I guess we'll have to try options 2 & 3.

Thanks for the suggestions.

 

[jazgeek]

don't discount the network card, I've seen dropped packets before cause problems such as what you described.

-----------
and they wonder why they call it Great Pains!

jaz

 

[VictoriaYudin]

The 'Failed to close table' error usually occurs when you've lost connection to the SQL server. Great Plains is VERY sensitive to the network connection and requires a much more steady connection than other applications.

I have also seen new workstations at a client's office come with the network card set to time out (or go to sleep) after short periods of inactivity. This caused MAJOR issues for Great Plains.

 

[vivian3]

I just find it strange that our Accounts Receivable can do all of her posting from her machine, but when our Accounts Payable tries posting from that same machine it doesn't work.

Both of these work stations have windows 98 se installed. We've been wondering if this has caused any of the problems. As well, the problems seem to have risen when we installed the crystal reports feature.

Thanks for the ideas, they are much appreciated.

 

[jazgeek]

I'm not 100%, but I don't believe win98 is a supported platform anymore with GP.

-----------
and they wonder why they call it Great Pains!

jaz

 

[VictoriaYudin]

what version of GP are you running?

 

[vivian3]

I believe it's 7.0. I did double check the system requirements and they all seem to be exceeded, and I believe win98se is a recommended operating system for that version.

 

[VictoriaYudin]

While it is on the list for GP 7.0, I don't know if I'd recommend Win 98 for any version of anything, ever.

 

[vivian3]

I know, but when that's what you're stuck with.....

I think somehow I'll have to try the following:

"2. destroy and recreate odbc connection on bad machine
3. uninstall tcp/ip as a protocol - reboot - reinstall on bad machine"

 

[VictoriaYudin]

Let us know how it goes!

 

[vivian3]

will do