Sage 100

When opening report manager get following prompt - SY_reportmanager_ui it is not an error but like a informational screen with a triangle and an OK button. I confirmed the SY files are there. Not sure when it quite working but I do know it has worked on this version. This in 2016 premium. Any ideas?

HI Johnny. Does the report template still generate? Are you using macros? Can you provide a screenshot of what you are seeing?

Here you go - There is no - other error!!!!

Is it occurring on other workstations and/or users as well?

@JohnnyPabian, that error is the Launcher's way of telling you that it is unable to build (or ""instantiate"") the SY_ReportManager_UI object. It is probably an error 200 or some other meaningless error under the covers. Are you able to run any of the other management tasks from the Setup menu? In order to get more useful information, you *might* able to try the instantiation from a command prompt and query the error. File / Run / SYZCON. Once in the command mode: o=NEW(""SY_ReportManager_ui"",%sys_ss) That will probably generate an error of some sort which might be useful. Otherwise, you can do: PRINT %SYS_SS'LastErrorMsg$ to see if it gives you any additional info.

I have not seen this message before and can't locate anything on the Sage knowledgebase explaining what the issue is.

This is on all computers - even running MAS90 style. Agree - KB has nothing - Sage support sort of remembers this happening before but not sure how it was fixed. Syzcon produced error #90 - Unable to locate Object class definition Nothing in Activity log

Since it's an Error 90, one reason for that is ..\mas90\SY\SY_ReportManager_UI.pvc physical is missing or renamed. I get the same error as you when I rename it. If that's not it, do you see a Sy_ReportManager_UI.pvc in the LINKS folder? If so rename it and try opening Report Manager again.

Assuming that you discover that SY_ReportManager_ui.pvc actually exists, did you print the contents of %SYS_SS'LastErrorMsg$ after you got the error 90? That might tell us something.

The file is there. We even renamed the file and it did not throw a different error, No error printed with printing last error msg via syzcon yielded a blank return, I even recompiled the menus and had a backup file and looked at the MNUMOD.txt it is the same since when I installed it. Confirmed other SY_ReportManager files are present - I get 7. There is a SY_ReportCommonUI in the links folder - I renamed and still got the message.

I get 7 files in the SY folder that begin with SY_ReportManager

I am out of ideas, here, @JohnnyPabian. If it were me, my next step would be to walk through the program as it's loading to determine where the failure is occurring. This is a tedious process. I hope someone else has some idea.

yep I am thinking this is a processmonitor session.. urggggg @PhilipWhirley

Agree with @PhilipWhirley. Like him, I would also step thru / execute through the program x lines at a time (dev approach). I doubt its something you can see externally with ProcMon unless files were actually missing or Access Denied error is occurring.