MATMAS IDocs are failing in 51 Status?

Hi,
I am sending across Material from one SAP System 4.5B Version to SAP System ECC 6.0.
I am using Mass send transaction to send these material (BD10). Here I am giving all the material number and the target system name and send it across in full. Now, the idocs are getting created but on the inbound side they are failing in 51 Status with a error text "<b>Message incomplete (seriousness, area, number, or exception missing)</b>".
Can anyone let me know what could the reason? Is there problem with configuration setting or else problem lies in EDI Setting.
Raghuram.

we can run the IDOC in foreground and see what exactly the error.
go to t-code: BD87
enter the IDOC number and execute.
run the IDOC in foreground ( with selection from Menu >> Restrict and Process.)
and then select Foreground
You need to choose proper line item when you selecting the above said Restrict and process.
Thanks
JK

Similar Messages

Idocs are failing

Hi,
We have a Z program which creates Inbound idocs by processing the files at the application layer. Once the idoc is procesed, based on our business requirement we split the parent idoc into more than one idoc with different message type and process them once again. Now we are seeing a new problem, the child idocs are not getting processed at all and simply moving into the status 51 with with a special message "Application log is already open and cannot be reopened." or "Period indicator T is not defined". These messages are not maintained by us as we maintain some messages to update the application log. There is no instance where we have failed to close the application log. Strange things is idocs gets posted when I manually process it by using program RBDPROCESS. They either get posted or will remain in status 51 - with valid message.
I have checked all the settings for ALE and Idocs. Everything is working fine. Actually we have three testing sytems, the same setup works fine on one system but is failing on the other two boxes.
Please help me to resolve this.
Thank you,
Ganesh Prasanna.T

hi ganesh,
i believe u split ur idocs based on some conditions. plz chk if u r meeting all the conditions.
also ask basis team if they have any option 2 clear the buffer like if any.
am not very much sure.
just try n chk out if helpful.
reward if helpful
kiran

Requirement for Alert when outbound idocs are failing

SAP A -
IDOCS -
> SAP B
We currently have a SAP A system sending outbound idocs to SAP B system via ALE. The current issue is when SAP B system is down. The outbound idocs being sent from SAP A system fail.
We want to get a alert when the System B is down.
What are the options available in SAP to achieve this requirement.
Thanks in advance for any inputs that will be provided.
Regards,
Chandra Kumar

Dear Chandra,
The logical solution to the problem is as below,
You need to have a Function module which checks the RFC connections between two systems before sending idoc. If the connection is found OK then the idoc should be send else a Alert message should be raised u201CSystem B is down, idoc can not be processedu201D
Please let me know if this solution helped in resolving your query.
Regards
Dinesh

BLAREL IDOC is failing to post in SRM

Folks,
We are trying to update the Release Orders from backend PO into the SRM GOA.
From the sourcing in SRM we create a GOA and distribute the GOA to backend system.
After distribution a contract is created in the backend system. In the backend from contract we create a purchase order. When this happens the IDOC BLAREL is triggered from R/3 to SRM . From the R/3 end there is no error, however in the SRM end the IDOC goes into error with the message "Object Linkage for Global Outline Agreement does not exist".
After some analysis we found that
1.The table SRRELROLES does not contain an entry with the correct OBJTYPE. Its checking for object type BUS2014 but in the table there is an entry for BUS2000113.
2.The status of the contract is u201CIn Distributionu201D, even after Backend contract is created successfully in the R/3 system
3.We have manually executed the BBP_GET_STATUS_2 and CLEAN_REQREQ_UP but they were of no help either.
4.IDOC configurations seem to be correct because not all the BLAREL Idocs are failing.
5.We have also found that in few Idocs Plant in the contract is different from the plant in the PO created in R/3
Now we are not sure whether the problem is because of point 2 or point 5.
Please let me know if anyone has experienced similar problems and resolved them.
Thanks, Amith

Hi Amit your analysis pefectly correct.
Your first point is very valid point.
in the goa , you might have deleted any one of the item
so you have two entries in bbp_pd one is new another one is deleted.
and when PO created and release orders trying to update wrong.
sap has to offer a notes.
Muthu

IDOC is Getting Fail with - 56 Status EDI Partner profile not available

Hi,
I am trying to Post invoice Data into IDOC on ECC Side.
My Scenario is File u2013 XI u2013 ECC(IDOC).
But It is Getting Fail with 56 Status u201C EDI: Partner profile not available u201C
On Control record I am getting this
Port                      BLANKKKKKKKKKK
Partner Number              CLNTDEC110      Logical system for Client
Partn.Type       LS                    Logical system
Function                                  BLANKKKKKKKKKK
Port                            SAPDPI
Partner number             CLNTSAMPLE
Partn.Type                      LS         Logical system
Partner Role                   BLANKKKKKKKKKK
My configurations are Like this :----
On ECC Side MY SID is DEC
On ECC side I have two logical system in CLNTDPI100 for PI
                         CLNTDEC110 for ECC.
I have Partner profile on ECC system on CLNTDPI100 logical system    - we20
Added message type in inbound side of partner Profile (INVOIC-INVOIC02)
ON SAP PI/ XI System MY SID is DPI
IDX 1 has Port name SAPDEC
On Message mapping EDI_DC40 is mapping with constants with below given value
<INVOIC02>
   <IDOC BEGIN="">
      <EDI_DC40 SEGMENT="">
         <TABNAM> </TABNAM>
         <DIRECT>2</DIRECT>
         <IDOCTYP> </IDOCTYP>
         <MESTYP>INVOIC</MESTYP>
         <SNDPOR>SAPDPI</SNDPOR>
         <SNDPRT>LS</SNDPRT>
         <SNDPRN>CLNTDPI100</SNDPRN>
         <RCVPOR>SAPDEC</RCVPOR>
         <RCVPRT>LS</RCVPRT>
         <RCVPRN>CLNTDEC110</RCVPRN>
      </EDI_DC40>
Regards
PS

Check the following :
in We 02 which partner number is displayed just in the posted IDOC -> 2nd coloum in the IDOC list .and verify if the
same you have in Partner profile. Actually this details comes from ECC business system's logical system name which you give in SLD.
in we 19 - take the error iDOC numner and open the IDOC ->click on the first line -> check entries as you mentioned
above sender port should be PI port not empty.you need to check the partner profiles properly
follow these steps
1. create a RFC destination of tyoe H for Pi system- 2. create a Port and assigen the RFC destination to it
3 create logical system for PI BD54 PICLNT001 say , 4 with the same name create a partner profile in We20
    in parter profile maintain the inbbound message parameters and add the PI port as receiver port in it .Give the basic type also .
now
for sender details in ur case PI : u have port (defined in PI IDX1),patner number (LS defined in ECC PICLNT001), parter type LS.
for receiver you have port defined (as above), partner number the logical system for ECC system.
in we 19 ,, edit the control record as above and go to the tab inbound processing and test the internal posting
it should work fine. in the adapte specific attribuet for receiver ECC system , maitain the same LS name , if any wrong entry is
there then change the LS in sld to poing to correct LS/
refer this
http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/technology/sap/26/
Regards,
Srinivas

What are the ways to handle Idocs which are failed to post to R/3

Hi Experts
What are the ways to handle Idocs which are failed to post to R/3 after sucessfully configuration of the Scenario.
Thanks & Regards
Aravind

Hi
Check the Idoc Status in R/3 with WE05.
Idocs will fail in following conditions
1) Idoc will be in error if all the mandatory field are not mapped.
2) If partner profile is not maintained.
3) Most of the times, idocs will be in error due to functional issues.....check the status and take help from functional guys.
Once the error resolved, reprocess the same idoc using BD87
Regards
Abhijit
Edited by: Abhijit Bolakhe on Mar 18, 2010 3:11 PM

Idoc are posting to ECC with Status 64

Hi All,
We are receiving IDOC with status 64 from PI.
We used tried by changing the options in partner profiles
--> Trigger by Background program
The inbound IDoc is processed in the background. In this case, make sure, that the report RBDAPP01 is scheduled in the transaction SM37 as a regular job with the correct variant to process all IDoc´s, which have this processing option maintained.
--> Trigger immediately
When using this setting, it is important to have sufficient resources for the immediate processing of the inbound IDoc´s. One dialog work process must be available for every single IDoc.
If this dialog work process is not available, the IDoc cannot be processed and stays in status 64.
I reffered the notes
555229 ‘IDocs hang in status 64 for tRFC with immediate processing’
734576 ‘IDocs retain status 64, but should be processed immediately’
1055679 ‘IDoc-tRFC inbound with immediate processing may not work’
Still the idocs are in 64 status, every time im re-processing them manually. even after re-processing some of them are going to 51 or 54.
Please help me.
Regards
Bhargava Krishna

Hello,
Can you please explain your issue is with "Trigger by Background program" or "Trigger immediately"?
For Trigger immediately, if there is no free dialog work process available than IDocs are posted with status 64.
For Trigger by Background program, Background job RBDAPP01 will process IDocs depending on variant you define to select & process IDocs(i.e., IDoc Status = 64).
It is always recommended to use "Trigger by Background program" for high volume interface which has large number of IDocs.
Help on RBDAPP01
Regards,
Sameer

Idocs are unable to transfer from R3 to PI system, IDOC status is 03

Hello Gurus,
Idocs are unable to transfer from R3 to PI system, IDOC status is 03
in sm58 getting below error
RFC are working fine
"EDISDEF: Port SAPCEP segment defn Z2SH_DESCR000 in IDoc type MATMAS03 CIM"
Regrds
vamsi

Hi,
I am also facing same problem, Can any one suggest me what is the issue..

SMS_WSUS_CONFIGURATION_MANAGER - MessageID 6600 - The request failed with HTTP status 503: Service Unavailable

Hi all,
knowning that there are already a lot of posts concerning above message, I have to write an additional one as I could not find a solution on the web yet.
Situation:
Windows Server 2008 forest including empty root and two child domains, one child domain does have SCCM SP1 (central primary site WND) installed on W2k8 x64 machine including WSUS 3.0 SP1 => everything is working fine.
Second child domain also contains a SCCM SP1 server (primary site HUN) running on W2k8 x64 and is defined as child site of central site WND => everything is working fine too - except Software Updates.
WSUS 3.0 SP1 installed on both SCCM servers by creating additional web site (not using "defautl web site") and configured ports 8530 and 8531 (SSL not used!). No proxy necessary/used. All WSUS 3.0 requirements for W2k8 are installed (IIS roles)
Error:
SMS_WSUS_CONFIGURATION_MANAGER - MessageID 6600:
SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "xxxx0003".
Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted.
Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.
wsusutil checkhealth =>OK
downloading updates from WSUS at central site (SUSDB and WSUS folder equal in size) =>OK
wsus admin console able to connect and configuration possible => OK
IIS ports configured within SMS are equal to those configured for WSUS website
SCCM config (using Configuration Manager Console) does look correct - ConfigMgr Software Update Point role properties and Software Update Point Component properties
wcm.log does report an error: (SCCM Log files at the end.)
"The request failed with HTTP status 503: Service Unavailable"
IIS log files of both websites (default web site and WSUS Administration website) do not show any errors.
Questions:
What else should I look at? (registyr, SUSDB content,..)
What exactly does happen during the attempt to configure the upstream server by the SMS_WSUS_Configuration_Manager component? I guess a SMS process tries to contact a webservice - would it be possible to debug in more detail ?
And finally - Who does know the solution ?
wcm.log:
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4468 GMTDATE=Mi Jul 16 10:49:47.758 2008 ISTR0="xxxx0003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
wsusctrl.log (looks fine to me - is able to connect to local WSUS !):
SMS_EXECUTIVE started SMS_WSUS_CONTROL_MANAGER as thread ID 6156 (0x180C). SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 2732 (0x0AAC)
This is a WSUS Role as WSUS registry key exists. SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Waiting for changes for 0 minutes SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Timed Out... SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
There are no unhealthy WSUS Server components on WSUS Server xxxx0003 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully checked database connection on WSUS server xxxx0003 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:02 6156 (0x180C)
Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:02 6156 (0x180C)
wsyncmgr.log (as a result of being not able to configure upstream server I guess):
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4476 GMTDATE=Mi Jul 16 10:03:51.481 2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 16.07.2008 12:03:51 4476 (0x117C)
Sync failed: WSUS server not configured. Source: CWSyncMgr:oSync SMS_WSUS_SYNC_MANAGER 16.07.2008 12:08:51 4476 (0x117C)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4476 GMTDATE=Mi Jul 16 10:08:51.636 2008 ISTR0="CWSyncMgr:oSync" ISTR1="WSUS server not configured" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 16.07.2008 12:08:51 4476 (0x117C)

I just experienced the exact same scenario. After much digging I found that csakg6so posted a fix at
Windoows-Noob
Run Internet Explorer as the SYSTEM account (psexec -s -d -i cmd.exe & C:\Program Files\Internet Explorrer\iexplore.exe)
Go to internet options
Go to conections
Go to LAN settings
Uncheck all boxes
The original post said to reboot, but that wasn't necessary for me.
After initiating a manual Software Update sync the WCM.log and WSyncMgr.log errors do not return and new updates are synchronized.

FILE to IDOC SCENARIO NEED MANDATORY FIELDS IN MATMAS IDOC

Hi
I'm learning a scenario like File to Idoc which is i need some what are the mandatory fields for creting the message mapping.. between source file and MATMAS IDOC... because it was showing several fields.
is there any way to find out the fields we need to map compulsory... for sending IDOC successfully.
Thanks
Babu

Hi Babu !
Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
It will display a document, telling you which fields are optional and which mandatory.
Regards,
Matias
PS: please award points if helpful.

Problems connecting to SSRS using IReportServerCredentials, the request failed with http status 401: unauthorized

We have a hosted SSRS server and we access it's reports using the reportviewer in an ASP.net application.
We are getting the error: The request failed with HTTP status 401: Unauthorized. When trying to run one of the reports. I have confirmed that the login details work when logging into the report manager page directly.
I have implemented an instance of IReportServerCredentials in a separate class (below) and I call it from the page before it tries to access the report. I'm not sure if this is all I need but can't seem to find any other info.
I have managed to gain access connecting to the external server from my PC and accessed the report, but when I promote the code to production and run it from there on my local PC I get the unauthorized message again: the request failed with http status
401: unauthorized
The class:
[Serializable]
public sealed class MyReportServerCredentials :
IReportServerCredentials
public WindowsIdentity ImpersonationUser
get
// Use the default Windows user. Credentials will be
// provided by the NetworkCredentials property.
return null;
public ICredentials NetworkCredentials
get
// Read the user information from the Web.config file.
// By reading the information on demand instead of
// storing it, the credentials will not be stored in
// session, reducing the vulnerable surface area to the
// Web.config file, which can be secured with an ACL.
// User name
string userName =
ConfigurationManager.AppSettings
["MyReportViewerUser"];
if (string.IsNullOrEmpty(userName))
throw new Exception(
"Missing user name from web.config file");
// Password
string password =
ConfigurationManager.AppSettings
["MyReportViewerPassword"];
if (string.IsNullOrEmpty(password))
throw new Exception(
"Missing password from web.config file");
// Domain
string domain =
ConfigurationManager.AppSettings
["MyReportViewerDomain"];
return new NetworkCredential(userName, password);
public bool GetFormsCredentials(out Cookie authCookie,
out string userName, out string password,
out string authority)
authCookie = null;
userName = null;
password = null;
authority = null;
// Not using form credentials
return false;
The call to the class, just before the report is run:
if (GetConnection.GetConnectionString().ToString().Contains("IP of external server removed"))
invoiceviewer.ServerReport.ReportServerCredentials = new MyReportServerCredentials();
We have tried so many things here, we don't even care whether the server authenticates or not but it appears to be as standard. Our hosting company has also drawn a blank and changed so many settings to no ava

Hi Nasa1999,
According to your description, you are getting the error: The request failed with HTTP status 401: Unauthorized when you access the report using the ReportViewer in an ASP.net application.
Regarding the 401 error, it could cause by the Service Principal Name(SPN) for the account the Reporting Services is running under hasn’t been registered when the Reporting Services is configured to use Kerberos authentication. So in your scenario,
please check if you are using Kerberos authentication. If that is a case, please make sure SPN is configured correctly. For more information, please refer to the similar thread:
The request failed with HTTP status 401: Unauthorized. in SSRS.
If issue persists, please check the Reporting Service error log (default location: %programfiles%\Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles) around the time that the error message thrown out.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

"The request failed with HTTP status 401: Unauthorized"

Hi,
I'm trying to get both RSS feeds and SSRS reports on a web application which is having NTLM authentication without Kerberos. The catch is proxy setting, if I give <proxy autoDetect="false" /> in web.config of my sharepoint web
application SSRS reports will be rendered in SQL Server Report viewer perfectly (I deploy using BIDS), but RSS viewer webpart will not display my internet feeds. If I give
<proxy autoDetect="true" /> RSS feeds are displayed properly but SSRS report will throw the following error.
The request failed with HTTP status 401: Unauthorized.
Description:
An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[WebException: The request failed with HTTP status 401: Unauthorized.]
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) +412862
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +300
Microsoft.SqlServer.ReportingServices2005.Execution.ReportExecutionService.ListRenderingExtensions() +53
Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.ListRenderingExtensions() +207
Microsoft.Reporting.WebForms.ServerReport.ListRenderingExtensions() +130
Microsoft.ReportingServices.SharePoint.UI.WebParts.ActionMenu.OnPreRender(EventArgs e) +180
System.Web.UI.Control.PreRenderRecursiveInternal() +108
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Control.PreRenderRecursiveInternal() +224
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3394
I tried to work around this by adding proxy settings with bypass list.
<system.net>
    <defaultProxy useDefaultCredentials="true">
      <proxy proxyaddress="http://<proxy IP address>:<port>" bypassonlocal="true" usesystemdefault="true" />
      <bypasslist>
  <add address="<my report server>" />
  <add address="http://<report server>:8080/reportserver/" />
  <add address="<IP of my report server>" />
      </bypasslist>
    </defaultProxy>
</system.net>
This makes RSS feed to work but SSRS throw the above error. I would need some advice from Microsoft on how to fix this.
Note: My sharepoint site cannot be anonymous. I have just once service account that runs sql server service, report service, sharepoint services etc. This account is local admin on all servers, has highest access on sql box, run SSRS web service and app
pools, etc.
I have four servers, 2 WFE in windows load balanced, 1 app server (running Central admin and report service in sharepoint integrated mode), 1 db server hosting all content and config dbs and report server db.
Regards,
Manoj
Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3618

Hi,
Thanks to share your post.
For the issue,
do you mean that the error happen with the use of NTLM authentication without Kerberos? If yes, the possible cause should be the lacking of Kerberos.
My suggestion is to implement the Kerberos authentication in your environment. You may check it and test it. For the detailed steps of implementing of the Kerberos:
http://blogs.msdn.com/b/martinkearn/archive/2007/04/23/configuring-kerberos-for-sharepoint-2007-part-1-base-configuration-for-sharepoint.aspx.
http://blogs.msdn.com/b/james_world/archive/2007/08/20/essential-guide-to-kerberos-in-sharepoint.aspx.
Hope this could help you!
Leo

The request failed with HTTP status 404: Not Found

Hi
BPC version we are using is : 5.0.502
When we Publish all reports using the steps below:
a. Log into BPC Web
b. Click on Available Interfaces> Select BPC for Administration
c. Under Web Admin Task Click Publish Reports
d. Select all of the reports and click the green check mark to publish the
reports.
I am getting following message 'System.Exception: The request failed with HTTP Status 404: Not Found. Event log relation to this error is given below.
Event Type:     Error
Event Source:     OutlookSoft log
Event Category:     None
Event ID:     0
Date:          12/8/2008
Time:          11:26:42 AM
User:          N/A
Computer:     BPCAPP
Description:
==============[System Error Tracing]==============
[System Name] : OSoftCPM
[Message Type] : ErrorMessage
[Job Name]     : AuditMgrService/SetAuditReportFiles
[DateTime]     : 12/8/2008 11:26:42 AM
[UserId]       : MMPlanning
[Exception]
    DetailMsg : {The request failed with HTTP status 404: Not Found.}
==============[System Error Tracing End ]==============
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.
We tried ' Publish all reports' as the resolution of error 'object variable or with block variable not set' on modifying an application as per sap note Note 1131320
If anyone knows the resolution for the above issue, please help me.
Thanks in advance
Sajeev Abraham

Hi
Thanks for the response.
Below are the full contents of the error message pop-up.
( System.Expection: the reguest failed with HTTP status 404:Not found at
Microsoft.Visualbasic.CompierServices.lateBinding.LateGet(Object o, Type,String name, Object
[]args,sTRING[]paramnames, Boolen[]CopyBack)
at OSoft.Services.WebServices.ReportmanageProxy.ReportManageProxy.SetPubishReport(String strAppSet,string
strApp,string strFiter)
url is given below
http://<HostName>/osoft/Admin/WebAdminMain.aspx
BPC Deployment is Multiple server ( Two servers) Database and Application deployed seperately.
Sql Reporting server is working.. I could connect using sql management studio.
Thanks

'System.Exception: The request failed with HTTP Status 404

Hi
BPC version we are using is : 5.0.502
When we Publish all reports using the steps below:
a. Log into BPC Web
b. Click on Available Interfaces> Select BPC for Administration
c. Under Web Admin Task Click Publish Reports
d. Select all of the reports and click the green check mark to publish the
reports.
I am getting following message 'System.Exception: The request failed with HTTP Status 404: Not Found. Below are the event log relation to this error.
Event Type:     Error
Event Source:     OutlookSoft log
Event Category:     None
Event ID:     0
Date:          12/8/2008
Time:          11:26:42 AM
User:          N/A
Computer:     BPCAPP
Description:
==============[System Error Tracing]==============
[System Name] : OSoftCPM
[Message Type] : ErrorMessage
[Job Name]     : AuditMgrService/SetAuditReportFiles
[DateTime]     : 12/8/2008 11:26:42 AM
[UserId]       : MMPlanning
[Exception]
    DetailMsg : {The request failed with HTTP status 404: Not Found.}
==============[System Error Tracing End ]==============
We tried ' Publish all reports' as the resolution of error 'object variable or with block variable not set' on modifying an application as per sap note Note 1131320
If anyone knows the resolution for the above issue, please help me.
Thanks in advance
Sajeev Abraham

Hi,
This forum is for BI Integrated planning an BW/SEM BPS. For BPC related questions please post this message in the forum for Enterprise Performance Management (Enterprise Performance Management (SAP EPM)).
Best regards,
Gerd Schoeffl,
SAP NetWeaver RIG BI

MATMAS idoc with classification details - reg

Hi,
I am working in a project related to the transfer of Material Master from one system to another ( Both are R/3 systems).
I am currently using the message type MATMAS with basic type MATMAS05. With the above message type i am able to generate an idoc from source system with all of the details except for the classification details.
For classification i have configured the message type CLFMAS and CHRMAS, in the CLFMAS i am able to successfully generate an idoc with BD91/BD92 tcodes. But when the idoc is generated, the idoc gives the list of charactersistics managed in the class at each segment level but not able to retrieve the values maintained by me during the material master creation. In order the target values for each of the characteristics in the class is empty.
Please clarify me with the following queries:-
a) Is that really required to push both CLFMAS and CHRMAS for a material master classification related field values ?
b) How to get the characteristics values maintained in the material master at the idoc level ?
c) How to link the CLFMAS generated idoc and the MATMAS idoc to link the relationship?
Thanks for the understanding.
Thanks and Regards,

Classification of a material has to be send with CLFMAS IDOC separate from the material.
Usually you first distribute all characteristics and classes, then the materials, finally the classification.
You have to enter the new material number in segment E1OCLFM field OBJEK of your classification Idoc.

MATMAS IDocs are failing in 51 Status?

Similar Messages

Maybe you are looking for