No PARAMETER statement is found

Hi everyone,

Our customer intermittently gets a program error when running a nominal period end. It occurred on their June, August, October and November periods ends this year.

The customer does have bespoke on their system but none in the nominal - it's all in Supply Chain.

I am unable to replicate the error offsite with a copy of their full system.

Any suggestions gratefully received!

Thanks,
Alex

Find more posts tagged with

Pegasus - Partner General Discussions

Comments

alan-bourke

A look at the error log generated would be useful. At least it would rule bespoke in or out.

alex

Should have provided more info.....

The period end appears to complete and the current period is rolled forwards. However the TB does not balance and this is because the period end has attempted to post a sales transfer journal for the new period (customer uses real time but not OPA) and the journal has only partly posted. The transfer can be run manually and it then works correctly.

Customer is running in a virtualised environment - RDS servers all have windows 2008 R2.

alex

No Opera error log is generated Alan, I only have an application error in the windows event log.

joe_cancglin

Does it happen on all user machines or the server?
Have you run a 'Validate Database' in VFP to validate the data?

alex

Hi James,

The same user always runs the nominal period end and she always uses the same RDS server so the error has only ever occurred on here. I can request they try it on a different server but as the problem is intermittent I'm not sure the results will be that reliable....

I will try a validate database next time they are all out of the system.

Thanks,
Alex

alan-bourke

Can the user send reports to PDF successfully?

What's the Windows error log say?

0712131256598360.doc

alex

The user can create PDF's. After I have fixed the part posted journal they manually ran the SL Transfer for the new month and this process created the N1412 folder and the PDF images of the sales transfer files within it.

Event log details are:-

Event ID: 1000
Faulting application name: opera.exe, version: 0.0.0.0, time stamp: 0x47139f24
Faulting module name: vfp9r.dll, version: 9.0.0.7423, time stamp: 0x49a31c32
Exception code: 0xc0000005
Fault offset: 0x0011624d
Faulting process id: 0x2ebc
Faulting application start time: 0x01d00f31039ed9b7
Faulting application path: C:Program Files (x86)PegasusO3 Client VFPopera.exe
Faulting module path: C:Program Files (x86)Common FilesMicrosoft SharedVFPvfp9r.dll
Report Id: 202dff5a-7b35-11e4-b3e5-00155d003307

alex

If it makes a difference the customer does not use the Opera PDF printer. They have this un-ticked but they do use 'Advance Previews'. It is set up this way as we were previously advised that it is better to use the XFRX driver in terminal services sessions to avoid locking/printing delays on the PDF printer.

alan-bourke

I'd try using the PDF printer for the next month end just to see. I've never had issues with it running Opera II on TS / Citrix farms.

Copyright © 2025 Infor. All rights reserved.