Exception message with details in Swing

I saw a lot of applications where, when an exception occurred, application shows to client dialog window where he may see exception and also this window has button Details if you want to see detailed information about exception. Do you know, does Swing have such kind of window or not?

Swing has any kind of window you want. The programs you have seen are catching the exception and displaying a window.
You need to create the component your self or use a third party component.
SwingLabs has an error dialog with the details button that you might want.

Similar Messages

MRP Exceptions list with details

Hi gurus,
I would like to know if somebody has a list of most important MRP exceptions with details.
I explain after MRP run, I go in MD06 transaction to display MRP material list. When I display this list I have exceptions and I don't understand all of these exceptions.
Does somebody have a list of principle exceptions with explanations and details or a link to find such a list?
Thank you in advance.

Hello
You can check the exception messages in the table T458A and T458B.
96    Stock fallen below safety stock level
98    Abnormal end of materials planning
70    Max. release qty - quota exceeded
01    Newly created order proposal
02    New, and opening date in the past
03    New, and start date in the past
04    New, and finish date in the past
61    Scheduling: Customizing inconsistent
62    Scheduling: Master data inconsistent
63    Production start before order start
64    Production finish after order finish
50    No BOM exists
52    No BOM selected
55    Phantom assembly not exploded
53    No BOM explosion due to missing config.
58    Uncovered reqmt after effective-out date
56    Shortage in the planning time fence
40    Coverage not provided by master plan
69    Recursive BOM components possible
05    Opening date in the past
06    Start date in the past
07    Finish date in the past
10    Reschedule in
15    Reschedule out
20    Cancel process
30    Plan process according to schedule
25    Excess stock
26    Excess in individual segment
57    Disc. matl partly replaced by follow-up
59    Receipt after effective-out date
27    Excess Stock Applied to Superceding Mat.
60    Disc., Rec. Applied to Superceding Mat.
27    Underdelivery tolerance
42    Order proposal has been changed
44    Order proposal re-exploded
46    Order proposal has been manually changed
80    Reference to retail promotion
82    Item is blocked
Regards,
Velmurugan S

Exception Message Selection Group

Hi all,
I'm trying to create exception messages with MRP/MPS run under selection group 5(Exception during BOM explosion) and 6 Exception during availability check. Can someone pls let me know of when such an exception/error message can be triggerd?
Thanks and Regards
Deepak Prasanna S

Dear,
If you donot know when this EM should appear why are you changing it?
anyway...explanation is as below
5 and 6 triggers in the following condition
EMGroup -5
                EM           text-when this mesages apprearas
     50     No BOM exists
     52     No BOM selected
     53     No BOM explosion due to missing config.
     54     No valid run schedule header
     55     Phantom assembly not exploded
EMGroup -6
25     Excess stock
     26     Excess in individual segment
     40     Coverage not provided by master plan
     50     Shortage in the planning time fence
     57     Disc. matl partly replaced by follow-up
     58     Uncovered reqmt after effective-out date
     59     Receipt after effective-out date
     70     Max. release qty - quota exceeded
     96     Stock fallen below safety stock level
I hope u understood....please come back if required
Edited by: Rajesha Vittal on Dec 21, 2007 8:11 PM

MRP exception message configuration in SPRO

Hi all,
Please advise where we can do configuration settings of exception message in SPRO.

Please check the first link of my post. Path and usefull info is mentioned there:
MRP exception message:
spro -> pp -> mrp -> evaluation -> exception messages -> define & group exception messages.
Define and Group Exception Messages
In this step, you define the following parameters for exception messages:
Whether exception messages are displayed for particular exception situations
If a particular exception message is not relevant to your company, select the field No exception message. In the planning run, this exception message is then no longer created for this situation.
The priority in which exception messages are to be displayed
If several exception messages exist for one MRP element, you can assign priorities to determine which exception message is to be displayed in the MRP evaluations. The system always displays the exception message with the highest priority directly in the list. The exception message selected with the next highest priority can be displayed in the list by accessing the additional data.
You enter the priority of the exception messages in the field entitled Excep.mssge priority.
You can see the sequence of priorities by selecting the possible entries pushbutton on the input field. Thus, you can gain an overview of the previous sequence of the exception messages. The exception messages with the higher number also has higher priority.
How exception messages are grouped to exception groups
For the collective display of the MRP list and the stock/requirements list, as well as for all material lists created as a result of the single-item, multi-level planning run, exception messages are grouped into exception groups. In the standard system, a grouping exists that you can change, if necessary, in the field entitled Selection group. You can adapt the long text of the exception group in the step Check Exception Group Texts.
Depending on which exception messages MRP lists are created
In the initial screen of the planning run as well as in in the MRP group, you can define that the system is only to create an MRP list if certain exceptional situations exist (creation indicator "Create MRP list - depending on exception messages"). The exception messages that lead to the creation of the MRP list are selected in the field entitled Create MRP list.
Actions
1. Define whether the exception message is set.
2. Define the priority of the exception message.
3. If necessary, change the exception groups.
4. If necessary, select the exception for the creation of the MRP lists depending on the exception messages.
Edited by: Afshad Irani on Jun 3, 2010 4:27 PM

Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

Hi all,
I have TFS2012 and run several projects.
We encounterwed with such an error while using Build server.
Overall Build Process
Initial Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
00:00
Get the Build
00:00
Update Build Number
Initial Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Final Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Result = Ephone_DIT_Deploy_20150424.1
01:56
Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
Initial Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
00:00
Get the Build Directory
Initial Property Values
Result = d:\temp\217\CTI\Ephone_DIT_Deploy
01:53
If Not String.IsNullOrEmpty(ConfigurationFolderPath)
Initial Property Values
Condition = True
01:53
Run TfsBuild for Configuration Folder
Initial Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp"
00:08
Getting sources
00:02
Labeling sources
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
00:19
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:10
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
MSBuild Log File
00:08
Generating list of changesets
00:20
Built Skins\SkinEPhone.cs for default targets.
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
00:03
Creating work item
Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Final Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
Final Property Values
Condition = True
Final Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
Final Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
Please have a look and guide where to find a problem
Thanks ahead

Hi Hooi,
I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
Best regards,

MS SQL server is going down frequently(10 days of gap) with exception message: "A severe error occurred on the current command. The results, if any, should be discarded".

MS SQL server is going down frequently(10 days of gap) with exception message: "A severe error occurred
on the current command. The results, if any, should be discarded". We are facing this issue for past two month.But funny thing is server will be up automatically with out any service restart manually. Also if we try to restart the SQL
server service manually then SQL server will be in a dead lock situation and it will not come up even if we wait for long time. Then we should do a windows server machine restart to
make the SQL sever up. As a suggestion from Microsoft to fix this kind of similar issue,
we have installed service pack 3 for SQL Server. But even after we are facing same issue.
Server Details:
Server OS: Windows Server 2008 R2
Two type of database servers are installed on server:
1. MS SQL Server 2008 R2
2. My SQL
Also Reporting server is configured for the purpose of generating SSRS report from a dot net website.
NOTE:Immediately after the data retrieval/save, we are closing the connection explicitly by the
application.
we have checked the windows event log and below are the details:
Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Application information:
    Application domain: /LM/W3SVC/5/ROOT-1-130718142067856406
    Trust level: Full
    Application Virtual Path: /
    Application Path: E:\WebSpaceFolder\ACSQuiK\Production\
    Machine name: DBSERVER
Process information:
    Process ID: 148
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
    Exception type: SqlException
    Exception message: A severe error occurred on the current command. The results, if any, should be discarded.
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
Log Name:      Application
Source:        Report Server Windows Service (MSSQLSERVER)
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Report Server Windows Service (MSSQLSERVER)" />
    <EventID Qualifiers="0">107</EventID>
Could anybody can suggest any kind of fix for this issue? Thanks in advance.

Hi YesYemPee,
I have tried but still not clear about your issue, I would like you provide more details information about your issue based on below points to better analysis about the issue:
What action did you do and caused the error "A severe error occurred on the current command. The results, if any, should be discarded", did you run report on the web application or something else then the error happen?
If you rendering the report and got the error, please try to provide us more error information in the log files which path like:
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles
If it is not the case in step1, Please try to provide SQL Server Error log(SQL Server Logs) and more details information.
If you still have any problem, please feel free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

Report to get the Material with Exception message"10" Rescheduling in

Hello All
We want to get the report to get the materials with exception message"10".We can get deatils from T code MD06,but it is restricted to MRP Controller/Vendor and we can get the details from Table "MDKP".Plese provide any report or T code to get the details of the exception message "10"
Thanks
Suresh kumar

Hello
You can use BAPI_MATERIAL_STOCK_REQ_LIST todata from MD04 or BAPI_MATERIAL_MRP_LIST to get data from MD05.
BR
Catano

JPA error with nested exception for more details

Hi All,
A strange thing is that when i can deploy javaee app successfully. But some time, it is failed and i have to wait for 10, 15 minutes then i can deploy again. When i got error, below is the error message:
I don't know if you can find a hint.
INFO: EclipseLink, version: Eclipse Persistence Services - 2.3.2.v20111125-r10461
SEVERE: Local Exception Stack:
Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
                at org.eclipse.persistence.exceptions.DatabaseException.errorRetrieveDbMetadataThroughJDBCConnection(DatabaseException.java:361)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:602)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206)
                at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:211)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120)
                at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224)
                at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495)
                at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233)
                at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
                at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
                at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
                at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
                at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
                at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
                at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
                at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
                at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
                at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
                at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
                at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
                at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
                at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
                at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
                at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
                at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
                at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLRecoverableException: Closed Connection
                at oracle.jdbc.driver.PhysicalConnection.getMetaData(PhysicalConnection.java:4508)
                at com.sun.gjc.spi.base.ConnectionHolder.getMetaData(ConnectionHolder.java:345)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:589)
                ... 42 more
SEVERE: Exception while invoking class org.glassfish.persistence.jpa.JPADeployer prepare method
SEVERE: Exception while preparing the app
SEVERE: Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
javax.persistence.PersistenceException: Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
                at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:517)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:211)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120)
                at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224)
                at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495)
                at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233)
                at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
                at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
                at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
                at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
                at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
                at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
                at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
                at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
                at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
                at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
                at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
                at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
                at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
                at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
                at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
                at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
                at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
                at java.lang.Thread.run(Thread.java:619)
Caused by: Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
                at org.eclipse.persistence.exceptions.DatabaseException.errorRetrieveDbMetadataThroughJDBCConnection(DatabaseException.java:361)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:602)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206)
                at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
                ... 40 more
Caused by: java.sql.SQLRecoverableException: Closed Connection
                at oracle.jdbc.driver.PhysicalConnection.getMetaData(PhysicalConnection.java:4508)
                at com.sun.gjc.spi.base.ConnectionHolder.getMetaData(ConnectionHolder.java:345)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:589)
                ... 42 more
SEVERE: Exception while preparing the app : Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
Local Exception Stack:
Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
                at org.eclipse.persistence.exceptions.DatabaseException.errorRetrieveDbMetadataThroughJDBCConnection(DatabaseException.java:361)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:602)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206)
                at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:211)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120)
                at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224)
                at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495)
                at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233)
                at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
                at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
                at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
                at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
                at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
                at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
                at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
                at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
                at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
                at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
                at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
                at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
                at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
                at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
                at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
                at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
                at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
                at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLRecoverableException: Closed Connection
                at oracle.jdbc.driver.PhysicalConnection.getMetaData(PhysicalConnection.java:4508)
                at com.sun.gjc.spi.base.ConnectionHolder.getMetaData(ConnectionHolder.java:345)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:589)
                ... 42 morethanks,
-Hoang Long

r035198x wrote:
Yep, the appserver got hold of a usable connection but the connection was closed before the appserver had finished/committed with it. It could be that the connection was closed by the database or some firewall timeout setting.
A good start is to investigate options of configuring your appserver's connection eviction policies including forcing a validation SQL to be executed when a connection is acquired. Make sure that such a query doesn't impact on performance and have some performance and integration testing before rolling out.i found that if i close the computer which causes this issue, hence other dev computers can deploy normally.
"deploy" here i mean deploy to a running instance on each dev's machine.
From this, i would guess the common database server itself rejects connection from clients.
I will try to investigate more if i am missing something.
And here i found a link that possibly a first good attempt:
[http://www.eclipse.org/forums/index.php/m/505809/]
EclipseLink automatically recovers from communication failures, but there is little we can do to diagnose the failure. We basically execute a query and have to wait for the JDBC driver, or DataSource's response, if it hangs for 10minutes, then we are waiting. You could set the JDBC timeout hint on your query, but whether the JDBC driver honors this is up to the driver. You should see the SQLException in your logs, provided your log level is warning or lower.
If you cannot fix your firewall, they you could change your connection pool settings to use a min number of connections of 0, so there will never be idle connections. But then you will be reconnecting a lot.
You could also use a third party connection pool or DataSource that supports a timeout setting on the pooled connections, or spawn a thread in your application the clears the connection pool every 30minutes.regards,
-HL

Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.boots

When attempting to create a new Account in siebel integrated with OEDQ the following error occurs.
ERROR
Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.bootstrap.library.path)(SBL-APS-00118)
STEPS
The issue can be reproduced at will with the following steps:
1) from EDQ director we have imported the EDQ_CDS,EDQ-REFERENCE DATA & EDQ_HISTORICAl DATA packages sucessfully.
2) Created dnd.param file in SIebel server SDQCOnnector folder.
3) Copied the libdnd.so file to siebsrvr lib directory(32 bit)
3) In dnd.param file we have mentioned the javalib file and instllation directory path(<Siebsrvr roo>/dnd/install)
4) Unzipped the EDQ-Siebel Connector files in dnd/install folder
5) Copied the dnd.properties file in dnd/install directory and modified it accordingly to point to installed EDQ instance.
6) Configured the Siebel components for EDQ integration.
7) Realtime EDQ jobs are running.
8) Create a new Account
Env details are
On : 8.2.2.14 [IP2014] version, Client Functionality
EDQ 11.1.1.7.4
IBM JDK 1.7 32 bit
Using Open UI
Any Champ have faced this issue and overcame it please let me know the resolution steps. your help is
Regards
Monoj Dey
9007554589

Hi Monoj,
A few questions:
- What OS is Siebel running on?
- What version of the Siebel connector are you using?
- Which libdnd.so file are you using?
- What's the contents of your dnd.parms file?
thanks,
Nick

Display detail exception message in af:messages

Hi!
I'm using ADF BC 10.1.3.3. I've created a backing bean event that calls Row.validate() method since before I call commit I want to ensure all the validation is passed or else the user is redirected to another page without committing the changes. Well, after the Row.validate call I'm catching the exception. But the problem I'm facing is that I'd like to display the detailed message of the exception caught which holds the actual validation message I defined on the model layer. If I use only Exception.getMessage() I receive the JBO-27024: Failed to validate a row with... message.
But using the Exception.printStackTrace I can see in JDeveloper output console something like this:
oracle.jbo.RowValException: JBO-27024:
+...+
+ at java.lang.Thread.run(Thread.java:595)+
+## Detail 0 ##+
oracle.jbo.RowValException: THE ACTUAL VALIDATION MESSAGE I DEFINED ON MODEL LAYER
+ at oracle.jbo.rules.RulesBeanUtils.raiseException(RulesBeanUtils.java:206)+
+...+
Is there a way I could get the message from Detail 0 in my Catch block in the backing bean? I thought that using getStackTrace could help but there are only records to "+at java.lang.Thread.run(Thread.java:595)+" and not from Detail 0 part.
I hope my question is clear and maybe there is another approach to achieve this.
I'm doing it this way since the jspx opened doesn't consists of all the attributes from the VO's row but the validation on the Model layer is executed on those attributes anyway. So I need to display a massage that the process can't be completed and it would be very nice to display the actual problem instead of the JBO-27024 message.
Thank you in advance,
regards!
BB

Thanks John,
I was catching all exceptions and Exception class doesn't have any appropriate methods. Catching RowValException I'm able to get reference to all detail exceptions.
Regards!

RFC Exception COMMUNICATION_FAILURE with Message RFC destination RFC does n

Hi all , i did a small application in webdynpro abap by calling BAPI . MY application is when i enter the studentid and click the submit button i shoutl get student details .
but when i'm clicking the submit button i'm gettting the error
"RFC Exception COMMUNICATION_FAILURE with Message RFC destination RFC does not exist. Occurred " can any one help me out.

hi rajeev.....
    i am sure that you would have used service call.
   in service call, in the destination part, you would have given a name. the service call automatically creates a destination in this name. but your user id would not have had that rights. so only you get this error. either use a already existing destination or get the access for that.
---regards,
   alex b justin

MD04 and PO return delivery quantity with exception message 15

Hi, Please suggest me how to get rid of PO return delivery quantity from MD04 where it is showing as POitem with receipt quantity and exception message 15 - reschedule out and reschedule date is showing current date.
Here we have received x qty from vendor and then moved y qty to blocked stock and then did return delivery (here return delivery did without any reference), we will not receive y qty anymore in future, how to get rid of this qty from MD04.

Hello
Please refer to the following note for more details about this scenario:
634038 - MRP: Returns order and delivery
This note explains in detail the customizing settings that you might use to turn a return delivery not relevant to MRP.
Best Regards
Caetano Almeida

Issue in MD04 transaction with exception message 26

Dear All,
I am facing 2 issues:
1) Even if the sales order line is confirmed and fulfilled, we are getting the stock for that material against the same sales order in the MMBE Transaction.
2) For the above material present in those sales Order which are confirmed and fulfilled, We are getting the entries for that material in Transaction MD04 ( Stock requirement list of the material after we run the MRP for a particular materia) with the exception message 26.
From our end, we have used the report sdrqcr21 which delete the wrong entries from "VBBE" so that MD04 will show incorrect entries but this approach is not helping us in the above situation.
Regards,
Rakesh

Rakesh,
This is one issue. There is nothing wrong with the software, this is standard behavior. You have built or procured more stock than was required by the sales order. The remaining unnecessary stock is now sitting in inventory, and is displayed in MD04 under the Sales order segment. This stock can never be used again within SAP, unless someone re-opens the sales order or performs some transaction to remove the stock from being 'Sales order on hand' stock.
Some companies will scrap this material, using their standard scrapping policies. Others will transfer this un-usable E stock to general stock, if it can actually be reused.
Rgds,
DB49

Re scheduling out with exception message 15 in MD04

Hi All,
In stock/requirement list the Purchase order is split into several Quanities on the same day with exception message 15 instead of displaying single PO. Also, attached the screen shot for your reference.
Please let us know what could be reason for this.
Regards,
Prabhakar.V

Hi All,
I tried both the customization and run MRP but still Multiple PO item is appearing in the stock/requirement list and problem is not resolved yet.
Could you please suggest to proceed further.
Thanks and regards,
Prabhakar.V

Working with MRP Exception Message

Hi Team,
In MD04, i am getting exception messages like below.
20 - Cancel the Process
15 - Postpone the process
10 - Bring Process Forward
I have already read the SDN postings and also the below link.
What is rescheduling and how does it work - ERP Manufacturing (PP) - SCN Wiki
But question is, Instead of MRP raises this exception message like "10 - Bring Process forward". This exception message proposes new start date for the planned order.
Q1: Instead of raises this as exception message, during MRP run, the planned order start date can be directly modified by the system know?
Q2: On daily basis, How to act on this MD04 exception messages? How the MRP Controller should act on this exception messages? Should the planner need to modify the planned order dates manually as proposed by the exception message?
Q3: Do w have any mass transaction to act on this exception message?
Thanks

But question is, Instead of MRP raises this exception message like "10 - Bring Process forward". This exception message proposes new start date for the planned order.
Exception message '10' is raised to 'firmed' receipts - not planned receipts. MRP cannot change the firmed receipts (exception - roll-forward periods), hence adjustment in case of this message is out of the question. Rest assured, the planning run does adjust the receipt as much as possible.
Q1: Instead of raises this as exception message, during MRP run, the planned order start date can be directly modified by the system know?
Have you seen exception message '10' to a planned order which is not fixed/firmed? System adjusts when possible.
Q2: On daily basis, How to act on this MD04 exception messages? How the MRP Controller should act on this exception messages? Should the planner need to modify the planned order dates manually as proposed by the exception message?
This may involve many manual decision from the planners and should not be automated. You can help out a planner through reports, but the decision should not be taken automatically.
If you find it interesting you can go through responses from Dogboy 49 and myself in the threads shared below:
Handling of MRP Exception Message
md04 exception
Q3: Do w have any mass transaction to act on this exception message?
No, you may think of developing something using BAPI_MATERIAL_STOCK_REQ_LIST or MD_STOCK_REQUIREMENTS_LIST_API function modules and providing hyperlinks to the users so that they can directly be inside the corresponding change transaction according to the MRP element.
However, 10, 20 and 15 all of these three exception messages come due to rescheduling for the firmed receipt elements. In MD07 you can get a collective overview of number of these messages in the exception group 07 (standard).
Best Regards.
Rajen

Exception message with details in Swing

Similar Messages

Maybe you are looking for