on 06-25-2010 9:24 AM
Hi Experts,
We have installed sql server 2005 sp3 and for some reason the sidadm user profile had some issue and I was not able to login.
The admin guys deleted the profile because of which I could login to the system. But the env. variable was not visible.
so added the standard variable.
Imp: There was some issue while sap startup and the dev_w0 was giving some error related to db connect and mentioned some note and also set the MSSQL_FORCEOLEDB=1. and then SAP came up.
When the env. variable dbms_set = mss was present in user variable of sidadm, and then tested the stms> system> communication --we got this error
DB Connect Link to database failed
Offline Call connect failed due to DbSL load lib fa..
This is tp version 372.04.71 (release 701, unicode enabled)
ERROR: No connect due to DbSl Load Lib Failure
ERROR: environment variable dbms_type is not set.
ERROR: Connect to DCO failed (20100625094219).
INFO: no trace information stored
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0249
standard output from tp and from tools called by tp:
-
After changing the env variab ( system ) DBMS_TYPE to mss and deleting from user variable we got the following err
This is tp version 372.04.71 (release 701, unicode enabled)
ERROR: Connect to DCO failed (20100625100539, probably wrong environmen
TRACE-INFO: 1: [dev trc ,00000] Fri Jun 25 10:05:39 2010
0.021323
TRACE-INFO: 2: [dev trc ,00000] DlLoadLib success: LoadLibrary("d
TRACE-INFO: 3:
0.021333
TRACE-INFO: 4: [dev trc ,00000] using "E:\usr\sap\DCO\DVEBMGS
0.021342
TRACE-INFO: 5: [dev trc ,00000] Thread ID:6508
0.023983
TRACE-INFO: 6: [dev trc ,00000] Thank You for using the SLOLEDB-i
0.023998
TRACE-INFO: 7: [dev trc ,00000] Using dynamic link library 'E:\us
0.024017
TRACE-INFO: 8: [dev trc ,00000] dbmssslib.dll patch info
0.024042
TRACE-INFO: 9: [dev trc ,00000] patchlevel 0
0.024052
TRACE-INFO: 10: [dev trc ,00000] patchno 92
0.024062
TRACE-INFO: 11: [dev trc ,00000] patchcomment Improved overflow
0.024076
TRACE-INFO: 12: [dev trc ,00000] np:(local) connection used on SE
0.024124
TRACE-INFO: 13: [dev trc ,00000] CopyLocalParameters: dbuser is '
0.024137
TRACE-INFO: 14: [dev trc ,00000] Using Provider SQLNCLI
0.034997
TRACE-INFO: 15: [dev trc ,00000] OpenOledbConnection: MARS proper
0.035082
TRACE-INFO: 16: [dev trc ,00000] Provider Release:9.00.4035.00
0.098421
TRACE-INFO: 17: [dev trc ,00000] Using Provider SQLNCLI
0.099260
TRACE-INFO: 18: [dev trc ,00000] OpenOledbConnection: MARS proper
0.099302
TRACE-INFO: 19: [dev trc ,00000] i'm dbo but there exists 1 users
TRACE-INFO: 20:
0.113172
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0232
standard output from tp and from tools called by tp:
Hello,
Please check schema with this note
Note 1294762 SCHEMA4SAP.VBS
regards,
John Feely
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> When the env. variable dbms_set = mss was present in user variable of sidadm, and then tested the stms> system> communication --we got this error
The SAP system does not run under user <sid>adm but under user SAPService<SID> - so you need to the set the environment for that user. Any environment setting for <sid>adm is pointless.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Its difficult to find the GUID for the user, because it was all with numbers...I found few env. set, so thought it must be for sidadm. So similarly there was another number like string, the env. was only for temp, so add the DBMS_TYPE for it and tested but didn't worked?
Markus, please suggest?
Hi Markus,
YES I have entered the parameter and restarted, but no LUCK?
If this could be useful:
After the installation of SCM7 the network guys updated the Windows and security patches. After that the SIDADM was not able to login and seems they deleted the profile because of which we can login through SIDADM. After that I have set the general parameter.
DBMS_TYPE: mss
MSSQL_DBNAME= DCO
MSSQL_SCHEMA=dco
PATH= to the \NTAMD64
SAPEXE = same as above
SAPSYSTEMNAME= hostname
The SAP is up but while upgrade the SPAM we are facing this issue. and tried all the thing
I have read in some note regarding DIR_LIBRARY. Should I try that?
Regards
Prash
> After the installation of SCM7 the network guys updated the Windows and security patches. After that the SIDADM was not able to login and seems they deleted the profile because of which we can login through SIDADM. After that I have set the general parameter.
Did you ever try to find out the root cause why the user was not able to log in? Since the profile was deleted all environment settings are gone. The only clean way would be to do a system recovery since it's not only the environment but also permissions and local policies that got deleted - including registry permissions and ACLs.
> The SAP is up but while upgrade the SPAM we are facing this issue. and tried all the thing
The environment of user SAPService<SID> doesn't seem to be right.
I suggest you open an OSS call and let the support have a look on your system. It's very difficult to help you without having system access.
Markus
Hi Markus,
Thanks a lot of your constant support whenever required.
With regards to the issue, the sidadm user had the problem. so does it required that sapservicesid was must have gone wrong.
SAP has recommended to go through the notes 128126 , 98678 but hardly it is useful.
If you think of any other alternative, do let me know. I shall try it.
Regards
Prash
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.