5.3.46 QS Data grind error

[TheMagicJBone]

Has anyone else had problems with grindq erroring out when grinding data? I have a good trans.log, the terminals refresh without errors, and I can grind the log after EOD, but it just will not grind whatever log is in the data folder. The error pops up as soon as I hit view or print in rpt.exe; it's too fast for anything to show up in the debout. This has been a few days now, so I know it's not a bad log. I can run a manual grind on data, and it runs fine, but rpt.exe is somehow doing it wrong. Any thoughts?

 

[bigblok403]

It should show up in one of the debouts unless it's a windows error. I would guess debout.g01 or debout.txt

 

[TheMagicJBone]

It should, but it doesn't. It errors as soon as I hit the view or print buttons, before it writes to debout.g01.

 

[bigblok403]

Can you run rpt.exe from the command line at all?

 

[posknowitall]

How about the dates? Sounds like the dates may off somewhere. You can also try to overwrite files in the data folder with ones from a good dated sub. Check to be sure files are not read only in data. I have seen that cause some problems as well.

 

[awbbar]

does the account that runs grind have admin privileges.
check services login info for ctrlsvr/edcsvr.
then check user priv.
it should not be local account.
make you have correct bootdrv share.

 

[TheMagicJBone]

I checked all the above and then some, with no luck. I'm now getting the error at another of this customer's sites. They don't have CDM, they're not pushing any data at all from any other location. This is a stumper.

 

[posknowitall]

Might be a long shot...Try deleting the default printer on the server an create it again. I seem to remember something like this years, and years, and years ago.