In Touch with Dynamics GP

This blog is intended to be a useful resource for Microsoft Dynamics GP users and professionals in the UK and the wider Microsoft Dynamics GP community as a whole.

Tuesday, 26 April 2011

How to create 32 bit ODBC data sources for Dynamics GP from a 64 bit server.

Hi folks , this is a real quick handy hint. As you are probably no doubt aware Dynamics GP can not see 64 bit ODBC although it is compatable with  64 bit operating systems (versions 10 and 2010 only, service pack specific).

The 32 bit drivers are still on the server however if you create a datasource through ODBC settings it will create a 64 bit one by default.

To access the 32 bit drivers:

1. Browse out to %systemdrive%\Windows\SysWoW64\odbcad32.exe

2. Created short cut on desk top to odbcad32.exe

3. Created 32 bit odbc using odbcad32.exe

You will then have 32 bit ODBC datasources.

Dynamics GP Bank Management - Checkbook [checkbook id] is already in user by user [username].

Hi folks I have been quiet for a while as we have been exceptionally busy here a Touchstone and something had to give somewhere and that was the blog I am afraid.

Anyway I have just spent a rather frustrating half an hour trying to resolve a support case, where I could find no mention of the fix under partnersource or elsewhere on line despite this being a standard error message. Therefore I thought I would post this out there to save everyone else the frustration.

The error message is “Checkbook [checkbook id] is already in user by user [username]” or if you’re in the UK “Chequebook [chequebook id] is already in user by user [username]”.

This message was occurring when the user had crashed out of a reconcile and then tried to re access the reconcile window Transactions>Financial>Bank Management>Reconcile.

We had tried Clearing the Bank Management ACTIVITY under routines>financial>Bank Management but we still got the message.

We also tried clearing the DEX_LOCK and DEX_SESSIONS from the tempdb by running delete statements against both, but we still got the message.

We had checked the Contents of the CB100006 as suggested in an article by VAIDY however there was nothing here either.

In the end though we needed to remove a record from the CBEU1020 CE ACTIVITY table.

select * CBEU1020 returned the locked record.

Then we ran a delete statement (as there was only one record in there)

Delete CBEU1020

And the issue was resolved.