Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrade Macola to 7.9.300 on Win2016 & SQL1026

Status
Not open for further replies.

AndrewForrest

Programmer
Jan 27, 2004
43
0
0
AU
Hi All,

Next Stage of the upgrade....

Having solved the invoice post problem on 2012 platform we have now created a new Win 2016 server with SQL 2016 and installed Macola 7.9.300
Previous upgrade for 2012 was 7.8.900 bring over database and then upgrade macola to 7.9.300.
Win 2016 upgrade path, install 7.9.100 (only available install for 2016) upgrade to 7.9.300 bring databases across from 2012 box.

The problem we now have is that Macola on the new box crashes when we try to print to Screen.
we have tried this with 2 or 3 different programs, you can see it getting data, and the menu bar at the says "starting Program" then nothing displays until the error message after about 1 minute.


First an MSL System Warning - abnormal clean up
then a Colbol error - JMW0001I-I error
screen dump attached.

When we close Macola we get the "Programs still open" message.


"Don't worry about the world coming to an end today.
We're already in tomorrow in Australia."
 
 https://files.engineering.com/getfile.aspx?folder=7066df09-c858-4fba-b73a-ec970c1945e3&file=Error79300.docx
Hi Peter,
Thanks for responding, Yes they where and yes they do, we have solved the problem. Because we are a Australian/European based company when we set up servers we install English/Australian and get rid of the English/USA language pack. What we believe happened is that when we removed the Eng/USA it corrupted the font used by the screen print prog. The official repair was to copy out all the fonts, delete them from the client and then copy back, if that failed then delete them again and copy from a different client that worked (bit difficult as it was only set up on the server for testing), however what we did was reload the Eng/USA language pack which solved the problem, we have removed the Eng/USA pack and it still works.

Onwards and upwards with the testing.

Regards
Andrew

"Don't worry about the world coming to an end today.
We're already in tomorrow in Australia."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top