x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 6 replies
  • Subscribers 240 subscribers
  • Views 4919 views
  • Users 0 members are here
Browse Forums
Sage 100 Contractor Announcements
119
topics
57
replies
Sage 100 Contractor General Discussion
1k
topics
4k
replies
Sage 300 CRE Announcements
168
topics
526
replies
Sage 300 CRE General Discussion
3k
topics
8k
replies
Sage Construction Management Announcements
4
topics
0
replies
Sage Construction Management General Discussion
15
topics
20
replies
Sage Estimating Announcements
39
topics
3
replies
Sage Estimating General Discussion
188
topics
442
replies
Jared.Stroeb

ODBC Error when attempting DELETE query

Posted By

I am trying to automate archiving of the Log files generated by sage.  We generate an average of 15,000 log entries a day and the LogViewer in sage is so slow it is nearly unusable after a month.  I am querying the data older than seven days and then inserting it to our SQL Server.  Using the same connection string I can query data from the QLM Master Log but when I go to delete data I get an error.

With my Sage user service account:

ERROR [42000] [Simba][SimbaEngine ODBC Driver][DRM File Library]Access denied.

With my personal Sage user account.  I was failing at opening second connection with this error: (Still not sure why but not directly relevent)

ERROR [08001] [Simba][SimbaEngine ODBC Driver][DRM File Library]Invalid account name.
ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
ERROR [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr).

Once i adjusted my code to no longer attempt a second connection open I get the same error:

ERROR [42000] [Simba][SimbaEngine ODBC Driver][DRM File Library]Access denied.

Any help would be appreciated.  Specifically what access is required by the sage account to run my delete command?  

  • 0
    Jared, did you figure this out? We have a development project going on now and our desktop version of our application connects and performs its operations fine, it is only when we try to convert to a service that we get the same error you posted. Any help would be appreciated.
  • 0 in reply to Jason A. Smith
    I had been working with Jared on this, but we have not achieved our desired solution. We actually never came up with a way to delete the data using an ODBC connection.

    Although working on the solution has been put on hold we did still have a plan for this. First we would copy the existing log data into a backup for the event that any of this is ever needed, then rename the flat files that hold the data log viewer displays. From speaking with support they were able to direct us to and verify the exact files, but were not willing to work with us on a solution. They did also let us know that the log file would be automatically recreated if moved/deleted (we have not tested this but I expect the information to be correct).

    We would then run the process on a schedule either kicking off nightly if logviewer > x entries or automatically every few days.

    If I remember correctly this would have been this file and directory:
    \\[servername]\Timberline Office\9.5\ACCOUNTING\Global\Master.QLM
    \\[servername]\Timberline Office\9.5\ACCOUNTING\Global\PVData\master_QLM
  • 0
    Hi Jared,
    What version of Sage 300 CRE are you using, including the revision and update number? We had some ODBC Simba issues in version 16.1. Our latest update 16.1 revision 6 has all of the known issues fixed.

    April
  • 0 in reply to jstone1
    You'll want to upgrade to 16.1 revision 6 to get the latest fixes. Knowledgebase article 30617 has the links for the latest downloads. If upgrading doesn't resolve it, we can open a support ticket to do more investigating.

    April
  • 0 in reply to April Dahl
    FYI, the issue that we are experiencing is with v15.1. Our customer cannot upgrade until later in the year, so we have to work with what we have. Our application is installed on Sage 300 CRE workstation, not the server, and we have been unable to get any service-based ODBC communications working. Our desktop version works like a champ.

*Community Hub is the new name for Sage City