Run STP on server as "yourself"

[SandSand]

Hello clever folks.

I have a SAS server and I run some stp's on the server through EG 4.3.

In many cases I would like the stp to access corporate fileshares / network folders. Primarily to import and export excel files.

However I need to run the stp on the server as my personal windows account, and not some system account.

How do I do this?

/Martin

[nrose]

Hi,

You need to run the STP on a workspace server rather that the STP server. Try reading this to find out more:

http://support.sas.com/documentation/cdl/en/biasag/61237/HTML/default/viewer.htm#wsspovw.htm

NIck

[SandSand]

Thanks Nick

However it does not seem to work either. I still get "ERROR: Insufficient authorization to access"

/Martin

[nrose]

Sounds like you may have permission issues. Make sure the workspace server, stored process, and underlying data can be accessed by that account at the metadata level, and that the data can be accessed at the OS level.

Nick

[SandSand]

Hi again..

Yes I have permission issues, but I don't know where to go to solve them.

The problem is that our corporate policies prohibit use of machine accounts for the fileshares / network folders I want to save to/read from. So the point is that since I am actively running the stored process myself, through EG, the SAS server should attempt to read/save my files using credentials from my personal windows account, since that is the account that has the access to these folders.

I hope my problem is more clear now, and would like any advise.

[SandSand]

It turns out it might have nothing to do with SAS, but rather windows server setup.

Referring to: http://support.sas.com/kb/41/477.html "Authorization errors can occur in SAS® Enterprise Guide® when you use Integrated Windows Authentication".

It is a setting in the windows server. I have not had this change to our server setup testet yet. But as a workaround I have set up a connection profile in EG and not selecting IWA, but instead filled in my credentials manually in the connection profile.

Accessing the network folders now works!