cancel
Showing results for 
Search instead for 
Did you mean: 

You have been logged with temporiray profile+SIDADM

Former Member
0 Kudos

Hi All,

I am getting error while login in to the system with SIDADM user

"You have been logged with temporiray profile.you can not access your files and files created in this profile will be deleted when you logoff and try logging later ,Please see the event log for details contact your Adminsitrator"

SAP system is working fine and but i am unable to run r3trans and environment variables also missing.

OS:Windows Server 2008

Please suggest any one and guide

Accepted Solutions (1)

Accepted Solutions (1)

former_member206552
Active Contributor
0 Kudos

Good Morning,

this is a pure windows problem

Please have a look at the following thread as i had it once before was due to a corrupt profile, had to rename my profile to old and create a new one. below is a procedure on how

http://social.technet.microsoft.com/Forums/windowsserver/en-US/734fae1e-9a47-415c-b53e-e1cdbdd8c38d/...

Hope it helps

Marius

former_member206552
Active Contributor
0 Kudos

Morning

you can also check

There are some SAP Notes which explain about require environment variables under windows platform.

Check these notes. May be useful if you decide to manually set environment of SAP users.

[Note 94801 - Environment variables/Registry (Windows NT)|https://service.sap.com/sap/support/notes/94801]

[Note 556232 - Environment settings for R/3/Oracle on Windows|https://service.sap.com/sap/support/notes/556232]

[Note 31559 - NT: Setting environment variables for R/3 kernel|https://service.sap.com/sap/support/notes/31559]

You may need to compare and cross check with other running SAP System.

source : https://scn.sap.com/thread/2147935

Hope it helps

Marius

Former Member
0 Kudos

Hi Marius,

Thanks for the repply.

I need to floow below prcoedure right ,

I have often found that even renaming the profile or deleting it may not always work. If you continue to get this error then you will need to go into the registry using an alternate admin account to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList and delete your old profile key that has a ending in s-1-5-21-*.................................bak. Then you should be able to log on without an issue.

Is their any problem for running system for changing this its a SAPSID ?

Please suggest

former_member206552
Active Contributor
0 Kudos

Hi

The problem that you might have after doing this is setting the ENV manually as i do not know if they where set as system variables or as user variables. but i would just suggest be moving the profile first to another drive and keeping it as a backup (i always do backups ), and re logon to see if a new profile has been created and check and see if R3trans works or checking the enviroment variables with running

cmd.exe

'set'

this will show you the variables that are active

just to add you will need to do these activities as a user who has administrator rights.

Best Regards

Marius

Former Member
0 Kudos

Hi Marius ,

Thanks for u r repply,how can i move the profile and take the abckup.

Please sugegst me its very urgent for me

former_member206552
Active Contributor
0 Kudos

Hi

logon as a user that has administrator rights on the system and go to

C:\Users

and move C:\Users\SIDADM to C:\temp

then logon with SIDADM again and this will create a new profile for the user

bxiv
Active Contributor
0 Kudos

You could always leave it in place to and just rename the the folder to oldSIDADM or SIDADM.backup; this will cause windows to not find the user information and also recreate the SIDADM user folder.

Also is SIDADM a local account on the server or is it a Windows Domain account?  You may have issues communicating correctly with the domain which caused your issue.  I don't think I have ever seen a local account go unavailable...but after a decade or so some events are cloudy! 

Former Member
0 Kudos

Hello All,

After rebooting the server issue resolved.

Thanks

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Have you imported the profiles in rz10.

check the ownership of the profile file @ os level.

It should be sidadm.

Check the ownership and permission of R3trans.

Check the cmd R3trans -d.

paste the error message if any error appears during R3trans -d  and paste logs of trans.log.

Regards

Yugandhar

Former Member
0 Kudos

Hi Yugandhar,

I have not imported the profiles.

If I run the cmd prompt R3trans -d "message is r3trans is not recognizing".

Thanks