x Want to participate? Join the group to interact
  • State Suggested Answer
  • +2 person also asked this people also asked this
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 141 subscribers
  • Views 5921 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
210
topics
416
replies
Sage Intelligence Reporting
121
topics
322
replies
Greytrix

Error 504 while printing report in v12

SUGGESTED
Posted By

Hi All,

We have completed the migration from v6.5 to v12. But while printing the standard reports we are getting error.The architecture of the system is multi-tier i.e. application server and Database server are both on different server. Please refer the below screenshot for the same.

error | Job 5 - ERR 504 en provenance du serveur d'édition : Erreur provoquée par le moteur d'impression Crystal .NET.
BPC1.rpt - - Message 1/3 : Erreur à l'exécution du rapport: F:\Sage\SafeX3\EDTV2\EDTSRV\srvedit\Data\X3_******\ENG\Report\BPC1.rpt
- Message 2/3 : Erreur de connexion: Table:SALESREP - Emplacement x3v12.SEED1.SALESREP
- Message 3/3 : Error in File BPC1 556_11324_{3EF14044-F3EF-4C80-8327-0B2E4516E990}.rpt:
Unable to connect: incorrect log on parameters.
Details: [Database Vendor Code: 18456 ]

 Any inputs on the same will be highly appreciated.

  • 0
    SUGGESTED

    Hello,

    Have you seen the following KB on this already?


    ERR 504 en provenance du serveur d'édition : Erreur provoquée par le moteur d'impression Crystal .NET. xxxxxxxxxxxx.rpt - - Message 1/3 : Erreur à l'exécution du rapport: g:\Sage\SafeX3\EDTV2\EDTSRV\srvedit\Data\X3_mcc-sql-01_1812\ENG\R

    Sage X3
    Products



    Country
    North America

    Description

    ERR 504 en provenance du serveur d'édition : Erreur provoquée par le moteur d'impression Crystal .NET.
    XXXXXXXXX.rpt - - Message 1/3 : Erreur à l'exécution du rapport: g:\Sage\SafeX3\EDTV2\EDTSRV\srvedit\Data\X3_mcc-sql-01_1812\ENG\Report\xxxxxxxxx.rpt
    - Message 2/3 : Erreur de connexion: Table:BPARTNER - Emplacement x3v12.SEED.BPARTNER
    - Message 3/3 : Error in File xxxxxxxxxx 7504_10776_{18CD1C78-9B77-4568-BB63-A2C94EBBC9E2}.rpt:
    Unable to connect: incorrect log on parameters.

    ERR 504 from the editing server: Error caused by the Crystal .NET print engine. XXXXXXXXX.rpt - - Message 1/3: Error in the execution of the report: g:Sage-SafeX3-EDTV2-EDTSRV-srvedit-Data-X3_mcc-sql-01-1812-ENG-Report-xxxxxxxxxxxx.rpt
    - Message 2/3: Connection Error: Table:BPARTNER - Location x3v12. Seed. BPARTNER
    - Message 3/3: Error in File xxxxxxxxxxxxxx 7504-10776-18CD1C78-9B77-4568-BB63-A2C94EBBC9E2.rpt:
    Unable to connect: incorrect log on parameters.



    Disclaimer
    Support

    Sage Customer Support does not provide assistance for issues related to third party products or enhancements, hardware, report customizations, state or federal tax-related questions, or specific accounting questions. Please contact your Sage business partner, network administrator, or accountant for assistance. Please review this document for additional information on the scope of Sage Customer Support Services.

    Cause

    A 64 bit ODBC connection and 32-bit ODBC connection were configured on the server where both were pointing to X3.



    Resolution

    Remove the 64- bit ODBC connection



    Category
    Configuration
  • 0 in reply to Rafael

    Hi Rafael,

    Thank you for the reply.

    But we have used the path of  64-bit ODBC and DBMS in console for database configuration. Please refer the below screenshot for the same.

    Kindly suggest for the same.

  • 0 in reply to Greytrix

    Is all firewall turned off?

  • 0 in reply to Rafael

    Yes, all firewall are off.

  • 0
    SUGGESTED

    Hi,

    Whats is the SSMS version on your application server and DB server?
    During the application and print server configuration on the console, you had any warning or error?
    There are some issues related to the versions of these components, on my machines, I try to follow this logic: 
    If SQL 2016 = SSMS 16.5.3
    If SQL 2017 = SSMS 17.9.1 
    http://online-help.sageerpx3.com/erp/12/public/prerequisites_windows-sql-server-2017.html

    I hope it helps you or gives a hint on the solution

  • 0

    I have seen this error can occur after migration if you have got "adxodbc" file in your child folder directory.  If you have, then may be worth regenerating this file using the "adxodbc" command

*Community Hub is the new name for Sage City