on 2007 Jun 04 7:25 AM
Hi I had the problem as mentionned in other threads regarding the connection problem for the DI API, with the error "Cannot connect to SBO-Common and the "accessviolationexception". It became clear to me that logging in to the UI via the command line argument to get the logged in user, and with the same user to the DI API works fine for the "manager" but not for the users u create in SBO. Is there something i forget to put in SAP so that the user gets the rights to connect to this DI API or is it a setting in SQL server, or something else ?
Could you please help me out. Have to finish this project before the end of the week
Thanks in advance
Seemed to work after closing and restarting SBO. Strange and i don't know why but it is solved anyway. thanks for the help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had only 1 license. So i made a superuser called marc and put the license to that name. That does not work. When i connect the license to the manager again, ot works fine. So there is a difference between the 2 but what can i do more then say that it is a superuser. Please advise. Thanks already for the forst reply
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
do both users have b1 licenses?
if you make the other user a superuser does the error go away?
if so it may be user authorizations within b1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
8 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.