I am attempting to pass existing stored procedures into a SAS program (SAS version 9.4M4) that's executing in batch mode on my org's dedicated SAS Azure server. When submitting Proc STP for my test program within SAS Enterprise Guide, it runs successfully. When I run the program through batch mode using the SASSRV account with highest privileges however, I receive the following error in the log:    Proc STP Program="/Financial Research/AzTest"; Run;    ERROR: Insufficient information provided for a connection to the metadata server. ERROR: Failed to connect to the metadata server. NOTE: PROC_STP: ====== Proc STP Execution Ending ====== NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE STP used (Total process time): real time 0.00 seconds cpu time 0.00 seconds   When I saw this error, I added the following before Proc STP:    Options MetaServer='server address' MetaPort=**** MetaUser=sassrv MetaPass=**************;   Rinse, repeat, and received this error in the log:    ERROR: Stored Process /Financial Research/AzTest does not exist. For this specific test stored process, I added 'Read Metadata' authorization for the SAS General Servers user group in SAS Management Console so that the SASSRV user could have read access to the metadata in the event that was the issue...but to no avail.    I feel like it has to do with some kind of permissions issue between the SASSRV account and the metadata, but I'm stumped. Any help is appreciated!  ... View more

My org is in the process of migrating SAS from an onsite server to Azure and simultaneously upgrading from 9.4M3 to 9.4M4.    The install of 9.4M4 on Azure and the migration of the metadata seem to have worked, but when I'm testing stored processes using the SAS stored process web portal, I am getting the error "STP: User has insufficient authorization to access \\source code repository\file path".   Some of our stored processes are stored in the server metadata & those execute as expected, but the issue seems to be with stored processes with source code with a physical .sas file stored in one of the source code repositories. In SAS Management Console, I can view the source code for these stored processes via the Stored Process Wizard, so read-access IS present at some level.    Further, the SAS System Services user group has the same permissions as our previous server where these stored processes will still execute. Needless to say, I'm stumped. I have a feeling there's an issue with the file path of the source code repositories, but those should remain static during the migration. Any help is appreciated!     ... View more