Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member187605
Active Contributor
9,149

This message contains some internal system details which have been hidden for security. If you need to see the full contents of the original message, ask your administrator to assign additional privileges to your account.


Have you ever run into this error message before? And you were curious to see the original message? Here's how to get it.


Start the Central Management Console. Navigate to Data Services Application:

Select User Security:



Select the user or group you want to authorise and select "Assign Security":

Select the Advanced tab, then "Add/remove Rights":

Grant "View internal information in log" and apply changes in both panels.


Next time your DS job runs into an error, you'll see the complete original error message.

21 Comments
Former Member
0 Kudos

Hi Dirk Venken,

We have installed SAP DATA SERVICES 4.2 SP05,

Even after Granting the permission "View internal information in log" to Administrators & DS Users, DS Admin users.... Still we get the same error log.

I'm running with ADMINISTRATOR user account.

Error log:

"This message contains some internal system details which have been hidden for security. If you need to see the full contents of the original message, ask your administrator to assign additional privileges to your account."

Thanks,

Ramesh

former_member187605
Active Contributor
0 Kudos

I haven't had the chance to install SP5, yet. But I am not aware of any differences in functionality at this level. Can you double-check whether the permission has been really granted?

Former Member
0 Kudos

We are using SAP DATA SERVICES 4.2 SP04 and have exactly the same issue I have a ticket open with SAP to resolve the problem. Hidden Data in Email Alerts ( 601316 / 2015 )

You can see the full error in the management console but not in the emails running as administrator with view internal information in log specifically granted

Former Member
0 Kudos

Hi Dirk,

Is there a definition anywhere of what is considered "internal system details"? Is this determined by BODS or some form of error severity from the database server (we are on SQL Server 2008)?

This seems like complete over-kill to me. For instance we hit this yesterday and the true error was an "invalid column name" on a target table. Why hide this from a developer?

Former Member
0 Kudos

Sap have advised to increase the error lines, they are going to launch KBA2206689 which will explain this in more detail

former_member18162
Active Participant
0 Kudos

Here is the KB article which discusses the functionality (SAP Support Portal login required):

https://support.wdf.sap.corp/sap/support/notes/1923264

Cheers!
Julie

0 Kudos

Hi Dirk,

@dirk.venken

we have come across the same issue for one of our job, where in still we are not able to see the exact error message after applying the workaround which you have suggested.

DS- version is DS4.2 SP04

IPS - 4.1 SP5

I'm running with ADMINISTRATOR user account.


Error - "

Function call <*****> failed, due to error <*****>: <*****>. This message contains some internal system details which have been

hidden for security. If you need to see the full contents of the original message, ask your administrator to assign additional

privileges to your account."


In KB Article - 1923264, they have mentioned the below step, not sure where to check this -


"The Operating System user can see the error message in the log file at the OS level. The rows in the log file denoted with (R) contain the actual error, while rows denoted with (E) contain the "hidden for security" warning seen in Designer."


Awaiting for your earliest reply.


@ maurice.hickey - how did you find out the true error ?

Former Member
0 Kudos

We did not see the true error until we granted the "View internal information in log" right to the user.

former_member187605
Active Contributor
0 Kudos

On Windows you can find the log files under C:\ProgramData\SAP BusinessObjects\Data Services\log\

0 Kudos

Thanks for the reply Maurice and Drik.

please find the below screen shots, still i find the same issue from the log file

Screen shot of access provided as per the steps mentioned in this forum.

No idea, why we aren't getting the required log info ?

former_member187605
Active Contributor
0 Kudos

No, I am sorry. At first sight, the settings look ok.

Are you sure the user running the job belongs the group? Try to add the rights directly to the user and see what happens.

0 Kudos

Thanks Dirk for the reply.

Yes the user belongs to the group.

Tried the option suggested by you, still cant fetch the internal error message.

please check the below screen shots, hope i have followed what you intended me to do .

0 Kudos

just to add to this,

the same job successfully executed on our other environment i.e., 4.0 without any issues.

Former Member
0 Kudos
Big thanks. It working.
former_member205400
Active Participant
0 Kudos
I'm on 4.2 sp 8 patch 1 and I'm getting exactly the same issue that "Shashidhar Koppal" talked about. I'm running the job with the 'administrator' user and that user has full control and those permissions are set like he explained. Any more news on this?
former_member187605
Active Contributor
0 Kudos
 

I have no clue. This has always worked for me. And this method has been officially documented in SAP note 2128861 - How to enable error codes obfuscated in job execution log - Data Services 4.2.

You may have to create a support incident.
0 Kudos
Hi Dirk,

Is it possible to create Custom access level in BODS ? and how the user and usergroup content migration can be done (Dev to QA server)

 
former_member187605
Active Contributor
0 Kudos
 

It makes no sense to transport users and groups from DEV to QA, because the repositories and DS roles are totally different in those tiers of your landscape. In DEV: one local repo per developer, plus a central one. In QA, only single local repo.
former_member187605
Active Contributor
0 Kudos
 

Restarting DS wil solve the issue.
former_member187605
Active Contributor
0 Kudos
 

Restarting DS will solve the issue.
former_member187605
Active Contributor
0 Kudos
 

Restarting DS will solve the issue.