Frx 6.7 problem

Jess M.

unread,

Oct 25, 2005, 10:25:06 AM10/25/05

to

Coming up with an error

The GL Index is locked by user since 12:00 AM

This on FRX 6.7 with Great Plains 8

Also is there a generic password that we can use if the administrator
password is unknown.

Thanks

GK

unread,

Oct 25, 2005, 1:35:01 PM10/25/05

to

Kill the gl index file (.g32 file) in the sysdata folder, and relogon to FRx.
If this does not work, look for a .ldb (access lock file) in the sysdata
folder. Make sure no one else is in FRx and delete the lock file, then
delete the .g32 file and log back onto FRx.

Gerald

unread,

Oct 25, 2005, 3:08:03 PM10/25/05

to

Follow GK instructions and if it did not work, delete one more file... that
is the
FRxRm32_{username}.mdb in the Sysdata directory. Then run FRx Again.

Gerald

JeffC

unread,

Nov 17, 2005, 4:28:02 AM11/17/05

to

In FRx 6.7.4031 and earlier, the "GL index is locked" message indicates that
a lock file is in place for the GL index (G32) for the company. While this
typically means that a user is building the GL index, it is possible that the
lock file was left behind when a previous user's attempt to build failed or
was cancelled. You can get past this by deleting the .LCK file that
corresponds to the .G32 file name (this is in the Sysdata folder).

In FRx 6.7.5014 and later, the lock file system is much smarter. When an
index build is in progress, a lock file is created, and reports or index
builds that follow will wait for an index build to finish or take over if the
lock file is stale. You should not really run into this type of problem with
the later versions.

Just for reference:

*.G32 files contain information about a company for access during report
design. These files can safely be deleted because they will always be
rebuilt by FRx.

*.LDB files are lock files for Microsoft Access databases (which includes
.G32 files). This file typically only exists if another user is accessing
the file, so you normally would not be able to delete an .LDB file. These
files do not have a direct impact on FRx - we do not look for them, but their
existence is indicative of the database being in use (which would prevent FRx
from deleting/rebuilding it).

FRxRm32_username.mdb files do not relate to GL indexes. These files store
user-specific overrides for Report Launcher.

I hope this information helps!

Thank you,
Jeff

--
Jeff Cutting
FRx Software Corporation
Software Development Engineer

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.

David Treleaven

unread,

Jan 2, 2006, 12:33:35 PM1/2/06

to

JessM,

Thanks for the FRx questions. The steps that were given from gk, Gerald,
and JeffC will be able to clear the GL Index error you were receiving. For
assistance with recovering the Administrator password you will want to
contact support.

Thanks,

David Treleaven
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================

Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Can ada.

This and other support options are available here:

BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469

Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.

=====================================================