When I am trying to restore multiple files, I keep getting errors such as " error initializing printer" or cannot create font. This only happens when restoring multiple files, not a single file. I tried copying the hole database to the 19data directory and then had to run database management and I still get the above errors. I called tech support who saw the error and played stupid that it so happens to be all my computers. funny thing, the function works fine in all other versions.
Please help..their solution was to restore each file separately which would take me 3 weeks
I'm sorry for the frustration. I have not run into this issue, nor could I reproduce - which probably just means something subtle is going on. Here's what I did to try to reproduce:
- Backed up some ProSeries Ty19 files to my desktop
- Deleted them
- Right Clicked in HomeBase, chose Restore, selected all the files, and chose "Restore Clients"
Is there anything different I'm doing?
Can you post a screenshot of the error(s) or detail the exact message(s) you are getting? That might help us look in the code to see what situation the error is used for. Also, if you're comfortable doing so, can you email \32bit\Logs\proseries.txt to email@example.com? The 32bit folder will be wherever you install ProSeries - usually either C:\\ProWin20\32bit or C:\\BasWin20\32bit
did you try to restore more than 100 files at a time? it happens when restoring a lot of files...
Also, the database maintenance crashes with the same error when fixing more than 100 files.
Tech support has gotten the screen shots and claim to have not recognized the codes..Thats interesting since its Proseries codes
Yes - I restored 1036 files in TY19. This probably means there's something environmental going on that accounts for the difference in experience. What's weird (to me) is that these are all printer related errors, which obviously has nothing to do with restore. It's possible somewhere in that process printer settings are being accessed or queried, but it'll take some time to investigate.
Thanks to google, I do see that these are Windows errors and something other products have run into.
Based on some of those posts, I have some followup questions
- Do you have any issues printing from ProSeries?
- Is your default printer a network printer?
- Can you try setting your default printer to something local, or even set "Print to PDF" as your default
No matter what I do, I get the same error but the default printer is mentioned in the error codes.
I copied all data right into the 19data file....None of the files show up so I started running database maintenance. It now crashes with the same error after about a 100 files....
why is Proseries doing this when its not a print function?
why is it only 2019? all my other year softwares have worked fine. something changed in the Proseries 2019 backend we are not being notified aboout
Is it crashing at the same file every time? If so, can you try not restoring that one? If it's crashing after 100 in general, can you restore 99, then the next 99, and so forth?
To help further troubleshoot, can you also email C:\ProWin20\32bit\Logs\proseries.txt to firstname.lastname@example.org?
It crashes anywhere from 60-200....However, it does update those files to the homebase so the same file is not crashing the system...
when I re run the database maintenance, it starts where it left off...I have to close the software as it becomes unusable...
Is there any resolution to this issue? I am experiencing the same issue and have worked with support for many hours. We do have a work around and am currently importing 60 at a time but at this rate it will take me 6 or 7 more hours to get all data restored. This is a new Admin Master with new OS and new aspp install.
I was at 795 imported when I posted that. I am still at it but am now at 1018 of 1606. Still crashing every once in a while with the same issue or the OLE issue. Print issue appears to less frequent after installing a network printer and setting it as default and not leaving the default Microsoft PDF. Think it may take longer to work with a support person than to just import 60 at at time. Unless they think that they can fix it.