Since I'm having a PSOS script issue that there is apparently no way to debug server scripts using FMP remotely, is there a problem with just installing FMP on the same server with FMS, then debugging the script itself on the server?
Yes, you can do this. Although I'm puzzled as to why you would need to. Why not just debug the script locally by using Perform Script instead of PSoS?
There shouldn't be any issue with doing that. Though if you are using a Windows Server OS, FMP/A isn't tested for it, so it might not work at top speed, but still worth a try. Might be a good idea for you to post some of your findings here as well. Just to see if there is anything we can do to help you out.
Need PSOS since I need server paths, not local paths.
1) Comment out the PSoS step.
2) Insert a Perform Script step that performs the same script.
It won’t do you any good to install FMP on the server to attempt to debug. You’ll get exactly the same behavior.
If you need to figure out what paths the server script is creating, do this:
1) In your script, insert an Exit Script script step that returns the path information.
2) In the parent script (the one that calls the PSoS session), use something like Show Custom Dialog to show you the result using Get ( ScriptResult ).
should be no problem with installing FMP on a server - but probably that won't solve the problem or help solving the issue.
Since a 'PSoS' logs in 'fresh' like a new user-session, often that script doesn't have the expected environment, wrong layout (TO), globals not set (global fields, $/$$ variables,). If You run the script from a client, it might be working ok - but not when running as PSoS...
Gotcha. Thanks for that info.
Retrieving data ...