web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

FRx Error Source: FSSolIV451 Error 40002: 01000

(1) ShareShare
ReportReport
Posted on by 20

Last month's FRx reports ran fine.  This month, some of the reports are not.

We are getting this error in place of each page of report (if 50 page report then 50 of these errors): 

  • FRx Reporting Engine
  • Source: FSSolIV451

Error 40002: 01000: [Microsoft][ODBC SQL Server Driver][SQL Server] The statement has been terminated.

Then this error with no report:  This report yielded no data

-----------------------------------------------------------------------------------------------------------------------------------

I found this and tried this but this only took away the error and the report does not run:

To resolve the issue I manually modified the ODBC configuration at the workstation for the system and application databases as follows:

  • Deselected “Use ANSI quoted identifers”
  • Deselect “Use ANSI nulls, paddings and warnings”
  • Deselected “Perform translation for character data”

-------------------------------------------------------------------------------------------------------------------------------

Solutions welcomed!

Thank you for looking at my question.

 

 

 

*This post is locked for comments

I have the same question (0)
  • Greg Byer Profile Picture
    2,586 on at

    Hi Beth,

    Normally this error is caused by having the ANSI options checked in the User DSN.  Since you've already done that, I would try doing the following:

    1.  Recreate the GL Index from scratch using the steps below.

    A. Close all instances of FRx and browse to the shared SysData folder with Windows Explorer. The location of the shared SysData folder can be verified in FRx under Admin | Organization | SysData (button).

    B. Delete or rename all files that end with the extension *.G32, *.LDB, and *.LCK.

    C. Start one instance of FRx and log into each company to recreate the *.G32 files.

    **If you get the error recreating any company please note what company had the issue so that we can verify that the ODBC connection is setup correctly.

    2. If the issue persists, browse to the FRx 6.7 code folder and run the following files.

    A. FRxReg.exe

    B. FRxReg67.cmd

    3. You can also manually register the .dll file contained in the error (FSSolIV451.dll) using the steps below.

    A. Use Windows Explorer to find the file, right-click on it, choose Open With, and Choose Program.

    B. In the Open With dialog box, click Browse, then browse to the Windows\System32 folder on drive C.

    C. In the System32 folder, highlight the Regsvr32.exe file and click Open.

    D. Click OK and you should receive a message that the file registered successfully.

  • Suggested answer
    Community Member Profile Picture
    on at

    Greg

    Thanks so much for taking the time to post this. You are a lifesaver. Been doing this a long time and never saw this error.

    Revising ODBC settings fixed the issue

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans