Sage 100

Newly upgraded Sage 100 ERP 2013(v 5.00.0.9) customer. Some users can't print (error attached) getting a message that the report is not found or does not exist. (Any and all crystal reports standard/custom). The problem goes with the windows user not the Sage user. The users connect to a terminal server with an rdp. Seems rights related to me but everyone has full rights to the sharepoint and below.(No network configuration was changed during the upgrade.) Upgraded version running on the same server as their previous version. I'd rather not call the helpdesk, any ideas would be greatly appreciated.

Do all of the users have the drive mapped?

Brett - Is this Standard or Advanced? Just a guess here, but if it is advanced check what account the service is running under and be sure it is a domain admin.

I noticed you've not installed PU1. Perhaps this was patched?

If it is advanced, what about the rights to the local temp folder? The location may have changed for 2013.

@RobertWood the drive is mapped for everyone. @JohnLeonard it's standard. @MarkKotyla I should've looked there. I would've thought that the knowledgebase would've mentioned it. I'll check now. (I didn't actually do the upgrade...it's just my problem now, lol)

Doesn't seem to be a PU1 issue.(according to the release notes.) I will go ahead and load it as soon as I can but it does work for most users so I'm sure I can fix it in the meantime if I can figure out a cause.

I was having a similar issue with opening a file via a script. @AlnoorCassim pointed out that the folder name had a space in it. His solution, to fix the path string, got me towards a solution. That specific solution won't work here, but his point that the ""space in your path .. may be the root of all evil"" may apply.

@MichaelNottoli I can't say that I hadn't thought about that because I had.(I wouldn't have used a space if it had been me.) I'm baffled by the fact that it works for some users. Same path.

Some thoughts .. When they run through RDP is MAS setup to run as a RemoteApp? If so the Start In folder should be set to Y:\Version 2013\MAS90\Home Also since this issue follows the Windows user I presume their Y: drive mapping is done through a network logon script. Is it possible the pushd command is being used instead of NET USE One more thing - if they RDP into a desktop session (not RemoteApp) you could try setting up a new desktop shortcut for MAS 90 that uses the UNC instead of mapped drive. To avoid Error 12's make sure the Start In has the UNC path to ..\mas90\Home Hope that helps.