x Want to participate? Join the group to interact
  • State Suggested Answer
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 132 subscribers
  • Views 645 views
  • Users 0 members are here
Browse Forums
Announcements
271
topics
260
replies
Databases and Operating Systems
771
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
854
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
878
topics
3k
replies
Sage CRM for Sage 300
184
topics
415
replies
h@AIT

Database error (operation=GET-LE, error=105)

SUGGESTED
Posted By

Dear Gurus,

I am using SAGE 300 Premium 2018.
I installed and loaded SAMSYS, SAMINC and SAMLTD.

I am at the General Ledger Module --> G/L Transactions, trying to browse Journal Entries.

Whenever I scroll to the end of the entries, I will get this error: 

Description: Journal Header.    Database error (operation=GET-LE, error=105).    [Microsoft][SQL Server Native Client 11.0][SQL Server]Unclosed quotation mark after the character string 'ÞÞÞÞ?)) order by "BATCHID" desc,"BTCHENTRY" desc'.  Please refer this error to your database administrator or see your database documentation for further assistance.

This happens on both SAMINC and SAMLTD.
If I browse through a client database, there are no errors.

Kindly assist how do I resolve this error.
Thank you for your kind assistance.

Top Replies

  • in reply to h@AIT +2

    HI H 

    Well done. After reading all the above updates, it looks as if the original data when you installed and loaded SAMSYS, SAMINC and SAMLTD were corrupt or not compatible to the new environment.

Parents
  • 0
    SUGGESTED

    Hi All,

    I used a workaround to "fix" the issue.

    I got a database dump of a working company database from a different source, and loaded that as a dummy database.
    Then I dumped the SAMLTD data and loaded it to the dummy database.
    Now it works.

    Not sure what is the root cause and how to fix the original issue, but I am moving on from this weird error that has been tormenting me for days Confounded

    Thanks Tim and Shane for helping and trying out the data. Slight smile
    Appreciate it much!

Reply
  • 0
    SUGGESTED

    Hi All,

    I used a workaround to "fix" the issue.

    I got a database dump of a working company database from a different source, and loaded that as a dummy database.
    Then I dumped the SAMLTD data and loaded it to the dummy database.
    Now it works.

    Not sure what is the root cause and how to fix the original issue, but I am moving on from this weird error that has been tormenting me for days Confounded

    Thanks Tim and Shane for helping and trying out the data. Slight smile
    Appreciate it much!

Children

*Community Hub is the new name for Sage City