Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Get-Next (Ec=49153)

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
I received the Get-next(Ec=49153) message while doing a dbdump. How do I fix. Thanks.
 
49153 is a database access problem, either your requester is not loaded (pervasive) or the sql client does not have rights to dump data.

e
 
Thanks, for the information, but can't fix it.
How I can fix the problem ?

Thanks!
 
Error '49153' is a generic Pervasive Error message. Alone it does not give you very much information. To get more details and the actual error you should go to Start\Programs\Pervasive\Pervasive 2000i\Utilities\Function Executor.

Then File\Open, Then beside file name Click on Browse and browse to where your data is and select any of the files like “APADV.DAT” highlight it and click on Open. Then at the bottom of the form click Open and it will give you a more descriptive view of the Problem at hand.

You should get a btrieve error message box. Post the btrieve status code and the new description and we will have a look at it.

Take Care,

zemp

"If the grass looks greener... it's probably because there is more manure."
 
Hello Zemp,

Thanks for your help, this a report by Function Executor :

Btrieve Error on operation B_GET_NEXT (6)

Btrieve status 8
"The current positioning is invalid."

on file "F:\Accpac database\DATA\TP\APADV.DAT"
I received this "Get-next(Ec=49153)" message when try to copy or dump some database.

Error Get-Next(ec=49153)

Thanks!!
 
I have had a similar error with ACCPAC, running Pervasive SQL 2000i. the 49153 is a message saying you can't connect to the database. Fist thing i would try is in Accpac database setup make sure your system and Data database verify if this works then you know your ODBC is functioning correctly. in which case check the setting of the MicroKernels for the server and clients. If however it does not verify check the ODBC settings and correct the errors in the ODBC.

Let me know if this helps at all

DB
 
Thanks Diamondbell,

How I can check all the settings, could you please tell me the rights settings.

Thank you.

Satg
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top