I think the pictures show that you are able to successfully invoke the macro. So it sounds like you successfully transferred the macro catalog from your laptop to the server, and the macro processor is still able to read an execute the macros. That is believable, since your laptop and your server are both windows. If you have other macros in the same catalog, you could test them.
The problem is not related the the macro processor / macro catalog, it's related to the macro itself. The macro is executing, and when the macro executes it generates an error.
This is where you will likely be stuck for a while, unfortunately. It is very hard (impossible?) to debug a macro without having access to the macro code. If there is very detailed documentation for the macro, you might be able to guess at some possibilities. If you still have PC SAS running and the macro works there, you could turn on options MPRINT SYMBOLGEN MLOGIC and run the macro, and that might give you some clues as to the name of the environment variable that may be missing on your server. But you're still stuck trying to debug code without having the code.
... View more