Anyone familiar with the XUSER and MAXDB?

[Former Member]

I completely de-installed the NSP and J2E installations from earlier this year. /usr* and Maxdb was completely removed.

The install of the new ABAP/NSP went smoothly. The install of the new J2E bombed in step 18 (Setup DataBase Connection Information). Error has to do with "creation of the xuser". I'm a MAXDB newbie and this terminology is foreign to me. See Error and xuser_default log below.

I am able to use the MAXDB database manager to connect to both NSP and J2E database. The superdba and control passwords for NSP and J2E are different (admin and abcd1234 respectively).

Any of your insights into this XUSER guy would be greatly appreciated.

Cheers ... Bart

-

---

Start of Error Message -

---

ERROR 2006-06-02 08:14:51

CJS-00030 Assertion failed: The creation of the xuser entry via 'c:\sapdb\programs\bin\xuser.exe -c JBH\SAPServiceJ2E -U DEFAULT -u XXXXXX -d J2E -n JBH -S SAPR3 -t 0 -I 0 set' aborts with returncode 2. Check the logfile xuser_DEFAULT.log for more information.

ERROR 2006-06-02 08:14:51

MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.

ERROR 2006-06-02 08:14:51

FCO-00011 The step SdbCreateXuser with step key |NW_Java_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|Sdb_Xuser|ind|ind|ind|ind|6|1|SdbCreateXuser was executed with status ERROR .

-

---

Start of Error Message -

---

-

---

Start of xuser_DEFAULT log file----

---

FATAL: Open xuser entry file failed: could not read USER data [5]

-

---

Start of xuser_DEFAULT log file----

---

[Former Member · Accepted solution]

Hi Bart,

Did you stop/remove X_server and other SAPDB related services before starting new installation ?

Regards,

Mike

[Former Member]

Just to close this thread.

I did start over. The un-install was very clean including the removal of XSERVER. But this time I removed the MAXDB remnants using the CLEANUP program mentioned in one of the other threads.

The clue about XUSER utility was good but I couldn't get it to work as advertised.

Both J2E and NSP are now running fine.

Thanks to Mike and Natalia for their thoughtful replies.

Cheers ... Bart

[Former Member]

Hi Mike,

No, I did not stop/delete the XSERVER service. The old NSP, J2E, and MAXDB de-installed brilliatly (or so I thought!). I only needed to manually remove some remnat files in /sapdb* and /usr*. Based on your comment, I'm now wondering if I need to remove the new, partially installed J2E and the succuessfully installed NSP and the XSERVER service and start completely over.

Natalia,

Those were good clues and documentation sources. I did locate the entries in the registry that you pointed to. Essentially there are 4 entries of the form:

S-1-5-...........<num> where <num> is 1043,1044, 1047, and 1048 I assume these are encrpyted representation of each of the DB users.

Each of those had Udata REG_BINARY entry.

But, I didn't have clue on how to make any changes here (e.g. add permission notify).

Do we need Robert Langdon to crack this code? Or could you give an idea how to do this in the registry.

TIA!

Cheers ... Bart Hughes

[former_member229109]

Hello Bart,

Open the registry editor and check the permissions for the folders HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech\User\*. The user SAPService<sid> must have the permission "Notify". Otherwise the existing xuser entry cannot be modified.

***

If you've got access to OSS/Service Market Place, then please take a look at notes 39439 & 820824.

The information about XUSER could be found in MAXDB library at http://dev.mysql.com/doc/maxdb/index.html

Thank you and best regards, Natalia Khlopina