cancel
Showing results for 
Search instead for 
Did you mean: 

Can't create repository in Content Server

elena_abramova
Explorer
0 Kudos

Hello all.

I need to create repository in content server 6.40 for 4.6C R/3.

I customize transaction OAC0, then go to CSADMIN to create it,

but get error "HTTP error: 401 (unauthorized) "Permission denied: adminContRep&configSet"",

when I put the name and password of Administrator of Content server.

In other systems (ent 4.7, erp2005) I can create repository in this content server without any problems.

What is the reason of this mistake?

Thank you.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Does the username you entered has domain administrator rights. pls revert.

Anirudh,

elena_abramova
Explorer
0 Kudos

Dear Anirudh.

Yes, of cause. This user has all needed rights.

The problem is only in 4.6C system.

In all other systems (4.7, ERP2005) with the help of same user we can create repository .

Best regards, Elena

Former Member
0 Kudos

Hi Elena,

My general workaround on these issues is as follows:

- Set admin security to 0 in the content server ini file.

- Set the directory and file rights to the content server directory to everyone to do everything.

- Check that the certificate requirement mathces for content rep definition for SAP and content server.

This generally removes all hindrances to creating content reps, but remember to turn it back on.

Espen

elena_abramova
Explorer
0 Kudos

Hi Espen.

Thank you.

Your advice "Set the directory and file rights to the content server directory to everyone to do everything" helps me.

Best regards, Elena

Former Member
0 Kudos

Hi Elena,

Glad to hear that it solved your problem

I would appreciate if you awarded points for the answer.

THanks,

Espen

Former Member
0 Kudos

The other problem that you might have faced is the userID/password that you enter when you get the prompt.You need to enter userid/password for the content server in the format : <domain>\<userID> and <password>. This helped for me. I already had full rights assigned to the content server directories on my windows 2003 content server.