Installation and Technical Issues

[chorst]

We have recently seen an issue with the Sage MAS 500 Event log filling up by logging an error every time a user logs into MAS500. One of our customers had 1700 errors since the middle of January. They are all identical errors. We opened a case with support (case 4261693) and they were aware of the error, but did not have a solution. Any ideas for stopping these annoying errors?

The description for Event ID (0) in Source (Sage MAS 500) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE = flag to retrieve this description; see Help and Support for details. The following information is part of the event: D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\BSESMAC.SYS

I am told that the BSESMAC.SYS file normally resides in the system32 folder, but is moved to the MSSQL folder on 64-bit machines, which is what triggers the error.

Thanks.

Cliff

[hfahimi · Accepted solution]

We are aware of this error and actually have a fix for it. The fix is basically replacing a file on the SQL Server box. Please check the Sage online support downloads area (I am not sure if its there yet) or contact Technical Support for the file and instructions to address this error.

Thanks,

Hassan

[chorst]

Fantastic, Hassan! Thanks for the reply!

[TRoop]

Hassan,

We are close to upgrading to 64-bit. Is there any way I can get my hands on this fix??

Thanks... 

[TRoop]

Also...

Has this been released in an MU since this post in Feb 2009?? If so, I may not need it then... 

[chorst]

Tim,

The DLL for LicRegServerx64 is available on the MU download page. It was released in February 2009. Because it is a server DLL only for 64 bit, I do not believe it is included in subsequent MU's.

[TRoop]

Thanks Cliff!!

[mateusstock]

We have MAS500 7.2, with our DB installed on a 64-bit machine an we started having the same problem. How can I get the fix?