21/2/2019 Knowledge Article

Cannot run reports - Error Code:

-2147467259
Title Cannot run reports - Error Code: -2147467259

Summary User reports they are unable to execute reports and receive error code -2147467259

Product JDA Warehouse Management

Module Reporting

Cause Corrupted mocarpt.mdb file

Additional If the error involves a problem connecting to the database, do the following:
Information
1. Go to the Windows Registry/regedit and search for MOCARPT.
2. There will be a key for the instance for the local-db-connection.
3. Check that it is properly pointing to the report server, and correct this if needed. See screen shot below.
4. Restart the application and report instance.

Legacy Article ID

Legacy Article
Number

Version ALL

Error Message -----------------------[ EXCEPTION ]--------------------------

Code Computer: SWGTSAGRPA01
Time: 07/19/17 17:16:24
App: mocarpt:2009.2.100
Error: -2147467259
Source: MocaCommands.GenerateReport (line: 493)
Descr: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.
Stack: MocaCommands.GenerateReport('Usr-Loading', 'SWGTSAGRPA01:4100', 'US_ENGLISH', '',
'printer', 'ANN-KYO-001', 2, 'ACMAN')
---------------------------------------------------------------

Unable to store report information in the report archive database.

Error: -2147467259

https://support.jda.com/articles/Knowledge/Cannot-run-reports-Error-Code-2147467259/p 1/2
21/2/2019 Knowledge Article
Desc: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.
Connection: Driver={SQL
Server};Server=RPDBSQLCLUSTER;Database=SG325WMD;Trusted_Connection=yes;
Command: insert into rpt_archive(rpt_id,descr,app_srv_host,app_srv_port,
gen_dt,expire_dt,filename,usr_id,file_size,prod_id,parm_val,dsp_rpt_id) values ('Usr-Loading','Carrier
Move Loading Document','SWGTSAGRPA01',4100,'07/19/2017 17:15:52','08/02/2017
17:15:52','rpt20170719171608_9688.rdf','ACMAN',11834,'LES','car_move_id = ''CMV0160984''|wh_id =
''652N''','Carrier Move Loading Document')

Resolution Instructions to copy the mocarpt.mdb file from QA/Test/Dev to the production instance.

1. Search for the MOCA DB file; for example (F:\htfrpt\MOCARPT\db\mocarpt.mdb).

2. Rename the current file to a .bak file.
3. Copy the empty mocarpt.mdb file from the original install directory. If there is no original install directory
you could copy from another working Dev, QA, or even another Prod instance.
4. Everything should start working again.
5. To validate the fix, either run another report, or manually run the insert statement into rpt_archive which
was erroring out in the trace file. If this works with no error, the mocarpt.mdb file is no longer corrupt.

URL Name Cannot-run-reports-Error-Code-2147467259

Attachment 1

Attachment 2

Attachment 3

https://support.jda.com/articles/Knowledge/Cannot-run-reports-Error-Code-2147467259/p 2/2