Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error

Hi,
I have a sccm 2007 infrastructure with multiple site. from some period of time one site start to have problems after some switches changes.
I try to locate the problem but until now no succes.
Any ideea?
Thks

mp.msi log
Property(S): SystemFolder.BFC13682_FB8F_4455_9724_4DDBBBF713D7 = C:\WINDOWS\system32\
Property(S): X64Perf.BFC13682_FB8F_4455_9724_4DDBBBF713D7 = C:\WINDOWS\system32\CCM\X64Perf\
Property(S): CCMSERVERDATAROOT = d:\sms
Property(S): Incoming.BFC13682_FB8F_4455_9724_4DDBBBF713D7 = d:\sms\CCM\Incoming\
Property(S): Outgoing.BFC13682_FB8F_4455_9724_4DDBBBF713D7 = d:\sms\CCM\Outgoing\
Property(S): CcmSystemVDirName = CCM_System
Property(S): CcmSystemRegVDirName = CCM_System_WindowsAuth
Property(S): CcmSystemAltAuthVDirName = CCM_System_AltAuth
Property(S): System.8D24F0F7_99DC_460C_9DA6_4193612E0D59 = C:\WINDOWS\system32\CCM\ServiceData\System\
Property(S): IA64Dir.181B4E66_9269_4E84_9E55_B6E7B91A7472 = C:\WINDOWS\system32\CCM\IA64\
Property(S): System.181B4E66_9269_4E84_9E55_B6E7B91A7472 = C:\WINDOWS\system32\CCM\ServiceData\System\
Property(S): x64Dir.6E186A08_E33E_4FBC_A39A_E3456945465F = C:\WINDOWS\system32\CCM\x64\
Property(S): System.6E186A08_E33E_4FBC_A39A_E3456945465F = C:\WINDOWS\system32\CCM\ServiceData\System\
Property(S): SMSCACHEDIR = Default
Property(S): SMSCACHEFLAGS = Default
Property(S): DISABLESITEOPT = Default
Property(S): DISABLECACHEOPT = Default
Property(S): SMSCACHESIZE = 5120
Property(S): x64.1A064B3F_A0C0_4EAC_8EE8_5AA5F0B33E3E = C:\WINDOWS\system32\CCM\x64\
Property(S): IA64.15899AB9_39B9_4695_BC16_3CCBF38F7EEB = C:\WINDOWS\system32\CCM\IA64\
Property(S): CCMINSTALLMSMQ = FALSE
Property(S): CCMINSTALLMP = 1
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): ARPNOREMOVE = 1
Property(S): ARPNOMODIFY = 1
Property(S): CCMENABLELOGGING_Default = FALSE
Property(S): CCMLOGLEVEL_Default = 1
Property(S): CCMLOGMAXSIZE_Default = 2000000
Property(S): CCMLOGMAXHISTORY_Default = 1
Property(S): SecureCustomProperties = CCMENABLELOGGING;CCMLOGLEVEL;CCMLOGMAXHISTORY;CCMLOGMAXSIZE;CCMDEBUGLOGGING;CCMOSINSTALLPATHS;CCMINSTALLMSMQ;CCMINSTALLMP;SMSUPGRADEPRODUCTS;CCMSERVERDATAROOT;SMSUPLEVELPRODUCTS;USESMSPORTS;SMSPORTS;CCMHTTPPORT;SMSSP1COLOCDOWNGRADE;USESMSSSLPORTS;SMSSSLPORTS;SMSSSLSTATE;CCMHTTPSPORT;CCMHTTPSCERTNAME;SMSFWKUPGRADEFROMPREV4BETA2;CCMFWKUPGRADEFROMPREV4BETA2;SMSCWS;CCMSHAREMODE
Property(S): AdminProperties = CCMENABLELOGGING;CCMLOGLEVEL;CCMLOGMAXHISTORY;CCMLOGMAXSIZE;CCMDEBUGLOGGING;CCMOSINSTALLPATHS;CCMINSTALLMSMQ;CCMINSTALLMP;CCMSERVERDATAROOT;CCMALLOWSILENTREBOOT;CCMHTTPPORT;CCMHTTPSPORT;CCMHTTPSCERTNAME;SMSCWS
Property(S): CcmDefaultPolicyAuthorityPriority = 10
Property(S): SmsDetectColocationDowngrade_ErrorMessage = A newer version of the Configuration Manager Client is installed. Cannot continue installing this version of the management point.
Property(S): ButtonText_Next = &Next >
Property(S): ButtonText_Back = < &Back
Property(S): ButtonText_Cancel = &Cancel
Property(S): ButtonText_Finish = &Finish
Property(S): ButtonText_Install = &Install
Property(S): ButtonText_Close = &Close
Property(S): ButtonText_OK = &OK
Property(S): ButtonText_Abort = &Abort
Property(S): ButtonText_Ignore = &Ignore
Property(S): ButtonText_No = &No
Property(S): ButtonText_Yes = &Yes
Property(S): ButtonText_Retry = &Retry
Property(S): ButtonText_Exit = &Exit
Property(S): FilesInUse_Info = Setup has detected that it needs to update some files that are currently in use by other processes.
To prevent having to reboot the machine, please close the following applications:
Property(S): DefaultUIFont = DefaultDlgFont
Property(S): DialogBox_Title = SMS Management Point Setup
Property(S): WelcomeDialog_Info = This will install the Systems Management Server Management Point.
Property(S): InstallDialog_Title = Install
Property(S): InstallDialog_SubTitle = The product is now ready to install
Property(S): InstallDialog_Info = Click Next to proceed.
Property(S): ProgressDialog_Title = Please Wait
Property(S): ProgressDialog_SubTitle = Setup is configuring your system.
Property(S): CompleteDialog_Title = Setup Complete
Property(S): CompleteDialog_SubTitle = Setup has finished updating your system.
Property(S): CompleteDialog_Info = Setup was successful.
Property(S): UserExitDialog_Title = Setup Aborted
Property(S): UserExitDialog_SubTitle = Setup was cancelled
Property(S): UserExitDialog_Info = The SMS Management Point setup was cancelled.
Property(S): InstallErrorDialog_Title = Setup Aborted
Property(S): InstallErrorDialog_SubTitle = Setup failed
Property(S): InstallErrorDialog_Info = Setup encountered an error and could not continue.
Property(S): SystemFolder.1114972D_590D_4AB6_BA2E_779928CEDCC2 = C:\WINDOWS\system32\
Property(S): X64Perf.1114972D_590D_4AB6_BA2E_779928CEDCC2 = C:\WINDOWS\system32\CCM\X64Perf\
Property(S): CcmDefaultPolicyAuthority = SMS:MP:Default:{B391E30E-C8BD-41FC-8B8C-540C4365DBE0}
Property(S): MPVDirRoot.67022EC1_A401_46E9_91FC_2DF2ED04CF15 = C:\WINDOWS\system32\CCM\SMS_MP\
Property(S): x64.0A840968_9A21_4DA4_A2B3_06C6AEAA2EC9 = C:\WINDOWS\system32\CCM\x64\
Property(S): MPVDirRoot.0A840968_9A21_4DA4_A2B3_06C6AEAA2EC9 = C:\WINDOWS\system32\CCM\SMS_MP\
Property(S): IA64.41483201_CB1F_4581_8423_CA84BCFA8A59 = C:\WINDOWS\system32\CCM\IA64\
Property(S): MPVDirRoot.41483201_CB1F_4581_8423_CA84BCFA8A59 = C:\WINDOWS\system32\CCM\SMS_MP\
Property(S): Res1033.0EACD2EE_412B_4985_9727_96BC217AABD8 = C:\WINDOWS\system32\CCM\1033\
Property(S): Res1033.4CB41E5B_59DE_4D09_98C5_332377961F73 = C:\WINDOWS\system32\CCM\1033\
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): USESMSPORTS = TRUE
Property(S): SMSPORTS = 80
Property(S): USESMSSSLPORTS = TRUE
Property(S): SMSSSLPORTS = 443
Property(S): USESMSSSL = TRUE
Property(S): SMSSSLSTATE = 0
Property(S): CCMENABLELOGGING = TRUE
Property(S): CCMLOGLEVEL = 1
Property(S): CCMLOGMAXSIZE = 1000000
Property(S): CCMLOGMAXHISTORY = 1
Property(S): CURRENTDIRECTORY = D:\sms\bin\i386
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 4972
Property(S): VersionDatabase = 110
Property(S): VersionMsi = 3.01
Property(S): VersionNT = 502
Property(S): WindowsBuild = 3790
Property(S): ServicePackLevel = 2
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 3
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\WINDOWS\TEMP\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\WINDOWS\system32\config\systemprofile\Application Data\
Property(S): FavoritesFolder = C:\WINDOWS\system32\config\systemprofile\Favorites\
Property(S): NetHoodFolder = C:\WINDOWS\system32\config\systemprofile\NetHood\
Property(S): PersonalFolder = C:\WINDOWS\system32\config\systemprofile\My Documents\
Property(S): PrintHoodFolder = C:\WINDOWS\system32\config\systemprofile\PrintHood\
Property(S): RecentFolder = C:\WINDOWS\system32\config\systemprofile\Recent\
Property(S): SendToFolder = C:\WINDOWS\system32\config\systemprofile\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): LocalAppDataFolder = C:\WINDOWS\system32\config\systemprofile\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\WINDOWS\system32\config\systemprofile\My Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 15
Property(S): PhysicalMemory = 4095
Property(S): VirtualMemory = 5202
Property(S): AdminUser = 1
Property(S): LogonUser = SYSTEM
Property(S): UserSID = S-1-5-18
Property(S): UserLanguageID = 1033
Property(S): ComputerName = CCAZ341
Property(S): SystemLanguageID = 6153
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 19
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 15:42:16
Property(S): Date = 4/9/2014
Property(S): MsiNetAssemblySupport = 2.0.50727.42
Property(S): MsiWin32AssemblySupport = 5.2.3790.3959
Property(S): RedirectedDllSupport = 2
Property(S): Privileged = 1
Property(S): USERNAME = TGAdmin
Property(S): COMPANYNAME = Teagasc
Property(S): DATABASE = C:\WINDOWS\Installer\15b9a.msi
Property(S): OriginalDatabase = d:\sms\bin\i386\mp.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
Property(S): SMSCWSADSPATH = IIS://LocalHost/W3SVC/1
Property(S): CCMSHAREMODE = 1
Property(S): IISAnonymousUserAccount = IUSR_CCAZ341
Property(S): ROOTDRIVE = E:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 21613138
Property(S): PrimaryVolumeSpaceRequired = 29783
Property(S): PrimaryVolumeSpaceRemaining = 21583355
Property(S): INSTALLLEVEL = 1
Property(S): CcmAdministratorsGroupName = Administrators
Property(S): CcmUsersGroupName = Users
Property(S): CcmCreatorOwnerAccountName = CREATOR OWNER
Property(S): PrimaryVolumePath = C:
Property(S): SOURCEDIR = d:\sms\bin\i386\
Property(S): SourcedirProduct = {B391E30E-C8BD-41FC-8B8C-540C4365DBE0}
Property(S): CCMHTTPSPORT = 443
Property(S): CCMHTTPSSTATE = 0
Property(S): CCMHTTPPORT = 80
Property(S): ProductToBeRegistered = 1
MSI (s) (44:D4) [15:42:16:906]: Note: 1: 1708
MSI (s) (44:D4) [15:42:16:906]: Product: SMS Management Point -- Installation operation failed.
MSI (s) (44:D4) [15:42:16:906]: Cleaning up uninstalled install packages, if any exist
MSI (s) (44:D4) [15:42:16:906]: MainEngineThread is returning 1603
MSI (s) (44:C0) [15:42:17:015]: Destroying RemoteAPI object.
MSI (s) (44:F8) [15:42:17:015]: Custom Action Manager thread ending.
=== Logging stopped: 4/9/2014  15:42:16 ===
MSI (c) (6C:F0) [15:42:17:015]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (6C:F0) [15:42:17:031]: MainEngineThread is returning 1603
=== Verbose logging stopped: 4/9/2014  15:42:17 ===

Similar Messages

  • SMS_STATE_MIGRATION_POINT Health check failed for port 80 with status code 500

    My SMS_STATE_MIGRATION_POINT gets a red cross because the health check of the SMS_STATE_MIGRATION_POINT is “sometimes” failing. I don’t understand why its fails sometimes? Any suggestions.
    gr, Iwan
    Health check operation succeeded SMS_STATE_MIGRATION_POINT 4/15/2010 2:51:29 PM 22044 (0x561C)
    Completed availability check on local machine SMS_STATE_MIGRATION_POINT 4/15/2010 2:51:29 PM 22044 (0x561C)
    Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK SMS_STATE_MIGRATION_POINT 4/15/2010 2:56:29 PM 22044 (0x561C)
    Health check operation succeeded SMS_STATE_MIGRATION_POINT 4/15/2010 2:56:29 PM 22044 (0x561C)
    Completed availability check on local machine SMS_STATE_MIGRATION_POINT 4/15/2010 2:56:29 PM 22044 (0x561C)
    Checking store for cleanup of failed or stale state stores... SMS_STATE_MIGRATION_POINT 4/15/2010 3:01:29 PM 22044 (0x561C)
    Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_STATE_MIGRATION_POINT 4/15/2010 3:01:29 PM 22044 (0x561C)
    Health check request failed, status code is 500, 'Internal Server Error'. SMS_STATE_MIGRATION_POINT 4/15/2010 3:01:29 PM 22044 (0x561C)
    STATMSG: ID=6207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_MIGRATION_POINT" SYS=SWAMS0083 SITE=P01 PID=13560 TID=22044 GMTDATE=Thu Apr 15 13:01:29.777 2010 ISTR0="500" ISTR1="Internal Server Error" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_STATE_MIGRATION_POINT 4/15/2010 3:01:29 PM 22044 (0x561C)
    Completed availability check on local machine SMS_STATE_MIGRATION_POINT 4/15/2010 3:01:29 PM 22044 (0x561C)
    Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK SMS_STATE_MIGRATION_POINT 4/15/2010 3:06:29 PM 22044 (0x561C)
    Health check operation succeeded SMS_STATE_MIGRATION_POINT 4/15/2010 3:06:29 PM 22044 (0x561C)
    Completed availability check on local machine SMS_STATE_MIGRATION_POINT 4/15/2010 3:06:29 PM 22044 (0x561C)
    Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK SMS_STATE_MIGRATION_POINT 4/15/2010 3:11:29 PM 22044 (0x561C)
    Health check operation succeeded SMS_STATE_MIGRATION_POINT 4/15/2010 3:11:29 PM 22044 (0x561C)
    Completed availability check on local machine SMS_STATE_MIGRATION_POINT 4/15/2010 3:11:29 PM 22044 (0x561C)
    Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK SMS_STATE_MIGRATION_POINT 4/15/2010 3:16:29 PM 22044 (0x561C)
    Health check operation succeeded SMS_STATE_MIGRATION_POINT 4/15/2010 3:16:29 PM 22044 (0x561C)
    Completed availability check on local machine SMS_STATE_MIGRATION_POINT 4/15/2010 3:16:29 PM 22044 (0x561C)
    Call to HttpSendRequestSync succeeded for port 80 with status code 200, text: OK SMS_STATE_MIGRATION_POINT 4/15/2010 3:21:29 PM 22044 (0x561C)
    Health check operation succeeded SMS_STATE_MIGRATION_POINT 4/15/2010 3:21:29 PM 22044 (0x561C)
    Completed availability check on local machine SMS_STATE_MIGRATION_POINT 4/15/2010 3:21:29 PM 22044 (0x561C)
    Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_STATE_MIGRATION_POINT 4/15/2010 3:26:29 PM 22044 (0x561C)
    Health check request failed, status code is 500, 'Internal Server Error'. SMS_STATE_MIGRATION_POINT 4/15/2010 3:26:29 PM 22044 (0x561C)
    Completed availability check on local machine SMS_STATE_MIGRATION_POINT 4/15/2010 3:26:29 PM 22044 (0x561C)

    I'va got the following event in my security event log this is strange because the Windows Firewall is off and the problem is not always there, 8 out 10 time the health  checks passes.
    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          4/15/2010 7:01:27 PM
    Event ID:      5159
    Task Category: Filtering Platform Connection
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:      ********
    Description:
    The Windows Filtering Platform has blocked a bind to a local port.
    Application Information:
     Process ID:  13560
     Application Name: \device\harddiskvolume2\programs (x86)\microsoft configuration manager\bin\i386\smsexec.exe
    Network Information:
     Source Address:  0.0.0.0
     Source Port:  9000
     Protocol:  17
    Filter Information:
     Filter Run-Time ID: 0
     Layer Name:  Resource Assignment
     Layer Run-Time ID: 36

  • 'Services.exe Terminated Unexpectedly with status code 128' on  SAP server

    get message 'Services.exe Terminated Unexpectedly with status code 128' on SAP Server when start windows 2000. & SAP server shut down

    Hi,
    Please check the link below.
    http://support.microsoft.com/kb/318447
    Rgds,
    Suman

  • Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 400, Bad Request.

    Hi All,
    I am seeing the following error for SMS_AWEBSVC_CONTROL_MANAGER component with Message ID: 8100
    Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests.  The http status code and text is 400, Bad Request.
    awebsctl.log file has below errors:
    Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    AWEBSVCs http check returned hr=0, bFailed=1
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    Health check request failed, status code is 400, 'Bad Request'.
    SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
    13920 (0x3660)
    Management point and Application Catalog Website Point are installed on the same Server where I am seeing the error for Application Catalog Web Service Point role. Management Point and Application Catalog Website Point are functioning properly. Application
    Catalog Website is working.
    Thanks & Regards, Kedar

    Hi Jason,
    Application Catalog Web Service Point and Application Catalog Website Point; both are installed as per below configuration on same Server:
    IIS Website: Default Web Site
    Port Number: 80
    with default value for Web Application Name configured.
    For SMS_AWEBSVC_CONTROL_MANAGER component, I am getting below error in Component Status:
    Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests.  The http status code and text is 400, Bad Request.
    Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which AWEBSVC is configured to communicate. 
    Solution: Verify that the designated Web Site is configured to use the same ports which AWEBSVC is configured to use.
    Possible cause: The designated Web Site is disabled in IIS. 
    Solution: Verify that the designated Web Site is enabled, and functioning properly.
    For more information, refer to Microsoft Knowledge Base.
    And awebsctl.log has the below error lines:
    Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    AWEBSVCs http check returned hr=0, bFailed=1
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    Health check request failed, status code is 400, 'Bad Request'.
    SMS_AWEBSVC_CONTROL_MANAGER
    12/23/2014 11:04:36 AM 16388 (0x4004)
    STATMSG: ID=8100
    What should I check from IIS side?
    Application Catalog Website is functioning properly.
    Thanks & regards,
    Kedar
    Thanks & Regards, Kedar

  • Internal server error while connecting SAP's customer financial fact sheet with iOS device

    Hi all,
    I am trying to connect SAP's customer financial fact sheet latest ( version 3.7)   with iOS phone/iPAD (version 7.1) but it shows internal server error,
    when trying to connect  Neither "Gateway (direct)" nor "SMP Cloud" enabled with port 80/443.
    On other hand my android devices with this app is working ok.
    Trace Log is below:
    2014-09-11 11:27:58.298 Debug Communication error: Error Domain=HTTPRequestErrorDomain Code=11 "INTERNAL SERVER ERROR" UserInfo=0x15eef620 {NSLocalizedDescription=INTERNAL SERVER ERROR}
    2014-09-11 11:27:58.295 Debug Request http://server:8010/url t finished with error Error Domain=HTTPRequestErrorDomain Code=11 "INTERNAL SERVER ERROR" UserInfo=0x15eef620 {NSLocalizedDescription=INTERNAL SERVER ERROR}
    response <?xml version="1.0" encoding="utf-8"?><error xmlns:xsi="http://www.w3.org/2001/XMLSchema-Instance"><code>HTTP/500/E/Internal Server Error</code><message> Call of service /sap/opu/odata/sap/fincustfactsheet terminated because of an error. The following error text was processed in system NQT : The ASSERT condition was violated.The error occurred on the application server . The termination type was: RABAX_STATE.If the termination type is RABAX_STATE, you will find more information on the cause of termination in system NQT in transaction ST22. If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server  in transaction SM21. If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process in transaction ST11 on the application server . You may also need to analyze the trace files of other work processes. If you do not yet have a user ID, contact your system adminmistrator. </message></error>
    2014-09-11 11:27:58.286 Debug [ERROR] 500:INTERNAL SERVER ERROR/Location:-[ODPRequest startSynchronous] + 1427
    2014-09-11 11:27:56.239 Debug DE:Using SUP Manual User
    2014-09-11 11:27:56.238 Debug DE:Get svcDoc URL http://server:8010/url
    2014-09-11 11:27:56.216 Debug DE:startSAPODataRequest CompanyCodeCollection
    2014-09-11 11:27:56.204 Debug DE:SAPODataAccess dealloc CompanyCodeCollection
    2014-09-11 11:27:56.198 Debug DE:CustomerCardsViewController refresh
    2014-09-11 11:27:52.600 Debug Logging/Tracing on
    2014-09-11 11:27:19.792 Debug Communication error: Error Domain=HTTPRequestErrorDomain Code=11 "INTERNAL SERVER ERROR" UserInfo=0x193f3060 {NSLocalizedDescription=INTERNAL SERVER ERROR}
    2014-09-11 11:27:19.787 Debug Request http://server:8010/url  finished with error Error Domain=HTTPRequestErrorDomain Code=11 "INTERNAL SERVER ERROR" UserInfo=0x193f3060 {NSLocalizedDescription=INTERNAL SERVER ERROR}
    response <?xml version="1.0" encoding="utf-8"?><error xmlns:xsi="http://www.w3.org/2001/XMLSchema-Instance"><code>HTTP/500/E/Internal Server Error</code><message> Call of service /sap/opu/odata/sap/fincustfactsheet terminated because of an error. The following error text was processed in system NQT : The ASSERT condition was violated.The error occurred on the application server. The termination type was: RABAX_STATE.If the termination type is RABAX_STATE, you will find more information on the cause of termination in system NQT in transaction ST22. If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server  in transaction SM21. If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process in transaction ST11 on the application server . You may also need to analyze the trace files of other work processes. If you do not yet have a user ID, contact your system adminmistrator. </message></error>
    2014-09-11 11:27:19.768 Debug [ERROR] 500:INTERNAL SERVER ERROR/Location:-[ODPRequest startSynchronous] + 1427
    2014-09-11 11:27:12.717 Debug timeout
    2014-09-11 11:27:12.681 Debug timeintervalinminutes: 23506917 timeoutInterval: 0
    2014-09-11 11:27:12.679 Debug applicationGoesToForeground
    Can anyone help me how to troubleshoot this error?
    Any help will be highly appreciated.
    Thanks
    Mahesh

    are these LUNs shared or standalone?
    I don't think it's really wise to have more than one DSM on the same server, so you're mixing the EVA and 3par DSMs and on 2003...
    other than ensuring that HBA firmware and drivers are all up to date and DMS drivers are at the latest, not much else you can do from the host side...maybe update the storport.sys driver to the latest for that OS
    are you sure that the HBAs are in fact supported/compatible with both storage back-ends? what about their driver/firmware/DSM versions - some SANs are very picky when it comes to this stuff, check the interop matrixes to find out
    overall, if you don't need SAN connection to one of these storage back-ends, I suggest you get rid of it and its DSM

  • Error sending DAV request. HTTP code 500, status 'Internal Server Error'

    Hi All,
    I am getting the error On SCCM R2 Environment .. on the client machine we are getting the below issue and software center 
    is not showing any information..
    While checking on the client's DatatransferService.log.. i am getting the below issues..
    Successfully sent location services HTTP failure message.
    Error sending DAV request. HTTP code 500, status 'Internal Server Error'
    GetDirectoryList_HTTP('http://MachineName:80/SMS_DP_SMSPKG$/7ea0b105-5592-48cd-8b8e-81777537c34f') failed with code 0x87d0027e.
    i realize it because of Isapi filter issues.. can any one guide me to resolve the issues..
    KJSUBBU

    Hi,
    In addition, I recommend you check whether you have additional Authentication methods (like ASP.NET Impersonation) enabled. 
    Disable the authentication method and try again.
    Also, please review the link below, here is a article about troubleshoot ISAPI filter issue.
    Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 500.0 – Internal Server Error"
    http://support.microsoft.com/kb/942031
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • CONC-SM TNS FAIL Call to PingProcess failed for IEMDPDEV

    Concurrent manager internal log file showing error CONC-SM TNS FAIL Call to PingProcess failed for IEMDPDEV after application startup and showing status "System Hold or Fix Manager" in system administrator> administer. When ICM Fixed from administer Concurrent manager its start works and no error found in manager log file.
    We have a RAC based environment and getting cold backup of application & database everyday after a shutdown of application and database.
    This is our production environment we only face this issue in our production environment and no recent changes made or patch applied on environment.
    Internal manager log file
    Shutting down Internal Concurrent Manager : 13-OCT-2014 01:31:32
    13-OCT-2014 01:31:32
    The ICM has lost its database connection and is shutting down.
    Spawning reviver process to restart the ICM when the database becomes available again.
    Spawned reviver process 30597.
    List of errors encountered:
    _ 1 _
    Routine AFPCMT encountered an ORACLE error. ORA-03114: not connected
    to ORACLE
    Review your error messages for the cause of the error. (=<POINTER>)
    _ 2 _
    Routine AFPSMG encountered an ORACLE error. ORA-03114: not connected
    to ORACLE
    Review your error messages for the cause of the error. (=<POINTER>)
    _ 3 _
    Routine FDPCRQ encountered an ORACLE error. ORA-03113: end-of-file on
    communication channel
    Review your error messages for the cause of the error. (=<POINTER>)
    APP-FND-01388: Cannot read value for profile option FND_MGR_STRTUP_THRES_TIME in routine &ROUTINE.
    List of errors encountered:
    _ 1 _
    Routine AFPCAL received failure code while parsing or running your
    concurrent program CPMGR
    Review your concurrent request log file for more detailed information.
    Make sure you are passing arguments in the correct format.
    The PROD_1004@PROD internal concurrent manager has terminated with status 1 - giving up.
    ========================================================================
    Starting PROD_1004@PROD Internal Concurrent Manager -- shell process ID 8210
              logfile=/u01/oracle/inst/apps/PROD_prodapps/logs/appl/conc/log/PROD_1004.mgr
              PRINTER=noprint
               mailto=oracle
              restart=N
                 diag=N
                sleep=30
                 pmon=4
               quesiz=1
              Reviver is ENABLED
    +---------------------------------------------------------------------------+
    Application Object Library: Concurrent Processing version 11.5
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    Internal Concurrent Manager started : 13-OCT-2014 08:02:25
    +---------------------------------------------------------------------------+
                       Process monitor session started : 13-OCT-2014 08:02:25
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
    13-OCT-2014 08:02:26 - Node:(PRODAPPS), Service Manager:(FNDSM_PRODAPPS_PROD) currently unreachable by TNS
                         Process monitor session ended : 13-OCT-2014 08:02:26
                       Process monitor session started : 13-OCT-2014 08:04:26
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:04:26
                       Process monitor session started : 13-OCT-2014 08:06:26
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:06:26
                       Process monitor session started : 13-OCT-2014 08:08:26
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:08:26
                       Process monitor session started : 13-OCT-2014 08:10:26
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:10:26
                       Process monitor session started : 13-OCT-2014 08:12:26
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:12:26
                       Process monitor session started : 13-OCT-2014 08:14:26
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:14:26
                       Process monitor session started : 13-OCT-2014 08:16:26
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:16:27
                       Process monitor session started : 13-OCT-2014 08:18:27
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:18:27
                       Process monitor session started : 13-OCT-2014 08:20:27
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:20:27
                       Process monitor session started : 13-OCT-2014 08:22:27
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:22:27
                       Process monitor session started : 13-OCT-2014 08:24:27
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:24:27
                       Process monitor session started : 13-OCT-2014 08:26:27
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:26:27
                       Process monitor session started : 13-OCT-2014 08:28:27
    CONC-SM TNS FAIL
    Call to PingProcess failed for IEMDPDEV
                         Process monitor session ended : 13-OCT-2014 08:28:27
                       Process monitor session started : 13-OCT-2014 08:30:27
                         Process monitor session ended : 13-OCT-2014 08:30:28
                       Process monitor session started : 13-OCT-2014 08:32:28
                         Process monitor session ended : 13-OCT-2014 08:32:28
                       Process monitor session started : 13-OCT-2014 08:34:28
                         Process monitor session ended : 13-OCT-2014 08:34:28
                       Process monitor session started : 13-OCT-2014 08:36:28
                         Process monitor session ended : 13-OCT-2014 08:36:28
                       Process monitor session started : 13-OCT-2014 08:38:28
                         Process monitor session ended : 13-OCT-2014 08:38:28
                       Process monitor session started : 13-OCT-2014 08:40:28
                         Process monitor session ended : 13-OCT-2014 08:40:28
                       Process monitor session started : 13-OCT-2014 08:42:28
                         Process monitor session ended : 13-OCT-2014 08:42:28
                       Process monitor session started : 13-OCT-2014 08:44:28
                         Process monitor session ended : 13-OCT-2014 08:44:28
                       Process monitor session started : 13-OCT-2014 08:46:28
                         Process monitor session ended : 13-OCT-2014 08:46:28
                       Process monitor session started : 13-OCT-2014 08:48:28
                         Process monitor session ended : 13-OCT-2014 08:48:29
                       Process monitor session started : 13-OCT-2014 08:50:29
                         Process monitor session ended : 13-OCT-2014 08:50:29
                       Process monitor session started : 13-OCT-2014 08:52:29
                         Process monitor session ended : 13-OCT-2014 08:52:29
                       Process monitor session started : 13-OCT-2014 08:54:29
                         Process monitor session ended : 13-OCT-2014 08:54:29
                       Process monitor session started : 13-OCT-2014 08:56:29
                         Process monitor session ended : 13-OCT-2014 08:56:29
                       Process monitor session started : 13-OCT-2014 08:58:29
                         Process monitor session ended : 13-OCT-2014 08:58:29
                       Process monitor session started : 13-OCT-2014 09:00:29
                         Process monitor session ended : 13-OCT-2014 09:00:29
                       Process monitor session started : 13-OCT-2014 09:02:29
                         Process monitor session ended : 13-OCT-2014 09:02:29
                       Process monitor session started : 13-OCT-2014 09:04:29
                         Process monitor session ended : 13-OCT-2014 09:04:29
                       Process monitor session started : 13-OCT-2014 09:06:29
                         Process monitor session ended : 13-OCT-2014 09:06:30
                       Process monitor session started : 13-OCT-2014 09:08:30
                         Process monitor session ended : 13-OCT-2014 09:08:30
                       Process monitor session started : 13-OCT-2014 09:10:30
                         Process monitor session ended : 13-OCT-2014 09:10:30
                       Process monitor session started : 13-OCT-2014 09:12:30
                         Process monitor session ended : 13-OCT-2014 09:12:30
                       Process monitor session started : 13-OCT-2014 09:14:30
                         Process monitor session ended : 13-OCT-2014 09:14:30
                       Process monitor session started : 13-OCT-2014 09:16:30
                         Process monitor session ended : 13-OCT-2014 09:16:30
                       Process monitor session started : 13-OCT-2014 09:18:30
                         Process monitor session ended : 13-OCT-2014 09:18:30
                       Process monitor session started : 13-OCT-2014 09:20:30
                         Process monitor session ended : 13-OCT-2014 09:20:30
                       Process monitor session started : 13-OCT-2014 09:22:30
                         Process monitor session ended : 13-OCT-2014 09:22:30
                       Process monitor session started : 13-OCT-2014 09:24:30
                         Process monitor session ended : 13-OCT-2014 09:24:30
                       Process monitor session started : 13-OCT-2014 09:26:30
                         Process monitor session ended : 13-OCT-2014 09:26:30
                       Process monitor session started : 13-OCT-2014 09:28:30
                         Process monitor session ended : 13-OCT-2014 09:28:30
                       Process monitor session started : 13-OCT-2014 09:30:30
                         Process monitor session ended : 13-OCT-2014 09:30:31
                       Process monitor session started : 13-OCT-2014 09:32:31
                         Process monitor session ended : 13-OCT-2014 09:32:31
                       Process monitor session started : 13-OCT-2014 09:34:31
                         Process monitor session ended : 13-OCT-2014 09:34:31
                       Process monitor session started : 13-OCT-2014 09:36:31
                         Process monitor session ended : 13-OCT-2014 09:36:31
    13-OCT-2014 09:38:31
    Request  : 1393181
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:31
    Starting FNDCRM Concurrent Manager                 : 13-OCT-2014 09:38:31
                         Process monitor session ended : 13-OCT-2014 09:38:31
    13-OCT-2014 09:38:31
    Request  : 1393182
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:31
    Starting FNDCRM Concurrent Manager                 : 13-OCT-2014 09:38:31
    Starting AMSDMIN Concurrent Manager                : 13-OCT-2014 09:38:31
                         Process monitor session ended : 13-OCT-2014 09:38:31
    13-OCT-2014 09:38:31
    Request  : 1393183
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:31
    Starting C_AQCT_SVC Concurrent Manager             : 13-OCT-2014 09:38:31
                         Process monitor session ended : 13-OCT-2014 09:38:32
    13-OCT-2014 09:38:32
    Request  : 1393184
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:32
    Starting DownloadProcessorMigrationMode Concurrent Manager : 13-OCT-2014 09:38:32
                         Process monitor session ended : 13-OCT-2014 09:38:32
    13-OCT-2014 09:38:32
    Request  : 1393185
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:32
                         Process monitor session ended : 13-OCT-2014 09:38:32
    13-OCT-2014 09:38:32
    Request  : 1393186
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:32
    Found dead process: spid=(10691), cpid=(282513), ORA pid=(39), manager=(0/4)
    Found dead process: spid=(10694), cpid=(282514), ORA pid=(40), manager=(0/4)
    Starting FFTM Concurrent Manager                   : 13-OCT-2014 09:38:32
    Starting FNDCRM Concurrent Manager                 : 13-OCT-2014 09:38:32
                         Process monitor session ended : 13-OCT-2014 09:38:32
    13-OCT-2014 09:38:32
    Request  : 1393187
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:32
    Starting FFTM Concurrent Manager                   : 13-OCT-2014 09:38:32
    Starting FNDCPOPP Concurrent Manager               : 13-OCT-2014 09:38:32
                         Process monitor session ended : 13-OCT-2014 09:38:32
    13-OCT-2014 09:38:32
    Request  : 1393188
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:33
    Starting FTE_TXN_MANAGER Concurrent Manager        : 13-OCT-2014 09:38:33
                         Process monitor session ended : 13-OCT-2014 09:38:33
    13-OCT-2014 09:38:33
    Request  : 1393189
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:33
    Starting IEU_SH_CS Concurrent Manager              : 13-OCT-2014 09:38:33
                         Process monitor session ended : 13-OCT-2014 09:38:33
    13-OCT-2014 09:38:33
    Request  : 1393190
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:33
    Starting IEU_WL_CS Concurrent Manager              : 13-OCT-2014 09:38:33
                         Process monitor session ended : 13-OCT-2014 09:38:33
    13-OCT-2014 09:38:33
    Request  : 1393191
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:33
    Starting INVMGR Concurrent Manager                 : 13-OCT-2014 09:38:33
                         Process monitor session ended : 13-OCT-2014 09:38:33
    13-OCT-2014 09:38:33
    Request  : 1393192
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:33
    Starting INVTMRPM Concurrent Manager               : 13-OCT-2014 09:38:33
    Starting INVMGR Concurrent Manager                 : 13-OCT-2014 09:38:33
                         Process monitor session ended : 13-OCT-2014 09:38:33
    13-OCT-2014 09:38:33
    Request  : 1393193
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:33
    Starting INVTMRPM Concurrent Manager               : 13-OCT-2014 09:38:33
    Starting OAMCOLMGR Concurrent Manager              : 13-OCT-2014 09:38:33
                         Process monitor session ended : 13-OCT-2014 09:38:33
    13-OCT-2014 09:38:33
    Request  : 1393194
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:33
    Starting OAMGCS_PRODAPPS Concurrent Manager        : 13-OCT-2014 09:38:34
                         Process monitor session ended : 13-OCT-2014 09:38:34
    13-OCT-2014 09:38:34
    Request  : 1393195
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:34
    Starting PASMGR Concurrent Manager                 : 13-OCT-2014 09:38:34
                         Process monitor session ended : 13-OCT-2014 09:38:34
    13-OCT-2014 09:38:34
    Request  : 1393196
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:34
    Starting PODAMGR Concurrent Manager                : 13-OCT-2014 09:38:34
    Starting PASMGR Concurrent Manager                 : 13-OCT-2014 09:38:34
                         Process monitor session ended : 13-OCT-2014 09:38:34
    13-OCT-2014 09:38:34
    Request  : 1393197
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:34
    Starting RCVOLTM Concurrent Manager                : 13-OCT-2014 09:38:34
    Starting PODAMGR Concurrent Manager                : 13-OCT-2014 09:38:34
                         Process monitor session ended : 13-OCT-2014 09:38:34
    13-OCT-2014 09:38:34
    Request  : 1393198
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:34
    Starting RCVOLTM Concurrent Manager                : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
                         Process monitor session ended : 13-OCT-2014 09:38:34
    13-OCT-2014 09:38:34
    Request  : 1393199
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:34
    Starting WFALSNRSVC Concurrent Manager             : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
    Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
                         Process monitor session ended : 13-OCT-2014 09:38:35
    13-OCT-2014 09:38:35
    Request  : 1393200
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:35
    Starting WFMLRSVC Concurrent Manager               : 13-OCT-2014 09:38:35
                         Process monitor session ended : 13-OCT-2014 09:38:35
    13-OCT-2014 09:38:35
    Request  : 1393201
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:35
    Starting WFWSSVC Concurrent Manager                : 13-OCT-2014 09:38:35
                         Process monitor session ended : 13-OCT-2014 09:38:35
    13-OCT-2014 09:38:35
    Request  : 1393202
    Priority : 0
    Program  : 0/3
    State    : Q
                       Process monitor session started : 13-OCT-2014 09:38:35
    Starting WMSTAMGR Concurrent Manager               : 13-OCT-2014 09:38:35
                         Process monitor session ended : 13-OCT-2014 09:38:35
                       Process monitor session started : 13-OCT-2014 09:40:05
                         Process monitor session ended : 13-OCT-2014 09:40:05
                       Process monitor session started : 13-OCT-2014 09:42:05
    Regards
    Usman

    Below is the solution provide by the SR Team its works perfectly our enviorment.
    Please perform the following steps:
    1. Stop all middle tier services including the concurrent managers. Make sure no FNDLIBR, FNDSM, or other dead processes are running.
        (restart application and database OS (i have done this step additionally))
    2. Stop and then restart the database.
    3. Connect to SQLPLUS as APPS user and run the following :
    EXEC FND_CONC_CLONE.SETUP_CLEAN;
    COMMIT;
    EXIT;
    4. Reference Note.260887.1 regarding the Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES.
    5.. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and Web tiers to repopulate the required system tables.
    6. Connect to SQLPLUS as APPS user and run the following statement :
    select CONCURRENT_QUEUE_NAME
    from FND_CONCURRENT_QUEUES
    where CONCURRENT_QUEUE_NAME like 'FNDSM%';
    If the above SQL does not return any value please do the following:
    cd $FND_TOP/patch/115/sql
    Connect to SQLPLUS as APPS user and run the following script :
    SQL> @afdcm037.sql;
    Reference Note 218893.1 How to Create The Service Manager 'FNDSM' on Oracle Applications
    to create libraries for FNDSM and create managers for preexisting nodes.
    Check again that FNDSM entries now exist:
    select CONCURRENT_QUEUE_NAME
    from FND_CONCURRENT_QUEUES
    where CONCURRENT_QUEUE_NAME like 'FNDSM%';
    7. Please run the Concurrent Manager Recovery feature to address any Concurrent Manager / Concurrent Processing issues within the Oracle Application Manager.
    8. Start the middle tier services including your concurrent manager.
    9. Retest the issue.
    Regards
    Usman

  • Adalnctl failed to start with status 127

    OS:red hat as4
    ebs: 11.5.9
    now my system can be started,but the adalnctl failed to start with status 127.
    the error message is about lsnrctl which saied that lsnrctl: command not found.
    but when i start the lsnrctl with oracle owner,the lsnrctl was started immediately.
    however,i found that,the lsnrctl was conected to the port 1521,the adalnctl to the port 1626.
    please help me to see it!
    the cdalnctl log was this:
    LSNRCTL for Linux: Version 9.2.0.3.0 - Production on 20-MAY-2009 17:03:27
    Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=TCP)(Host=ebstest)(Port=1626))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
    TNS-00511: No listener
    Linux Error: 111: Connection refused
    Starting listener process APPS_PROD.
    LSNRCTL for Linux: Version 9.2.0.3.0 - Production on 20-MAY-2009 17:03:27
    Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
    Starting /u01/oradata/prodora/8.0.6/bin/tnslsnr: please wait...
    TNS-12545: Connect failed because target host or object does not exist
    TNS-12560: TNS:protocol adapter error
    TNS-00515: Connect failed because target host or object does not exist
    Linux Error: 2: No such file or directory
    adalnctl.sh: exiting with status 1
    Checking status for listener process APPS_PROD.
    adalnctl.sh: exiting with status 1
    ./adalnctl.sh: line 126: lsnrctl: command not found
    Starting listener process APPS_PROD.
    ./adalnctl.sh: line 137: lsnrctl: command not found
    adalnctl.sh: exiting with status 127
    Checking status for listener process APPS_PROD.
    adalnctl.sh: exiting with status 1

    oh maybe i found it
    i have more than one listener.ora
    [root@ebstest /]# find -name listener.ora
    ./u01/oradata/prodora/iAS/hs/admin/listener.ora
    ./u01/oradata/prodora/iAS/network/admin/samples/listener.ora
    ./u01/oradata/prodora/8.0.6/network/admin/samples/listener.ora
    ./u01/oradata/prodora/8.0.6/network/admin/PROD_ebstest/listener.ora
    ./u01/oradata/proddb/9.2.0/network/admin/samples/listener.ora
    ./u01/oradata/proddb/9.2.0/network/admin/PROD_ebstest/listener.ora
    ./u01/oradata/proddb/9.2.0/appsutil/out/PROD_ebstest/01010106/listener.ora
    ./u01/oradata/proddb/9.2.0/appsutil/out/PROD_ebstest/01010108/listener.ora
    ./u01/oradata/proddb/9.2.0/appsutil/out/PROD_ebstest/01010121/listener.ora
    and the other listener.ora was about port 1626
    [root@ebstest /]# cat ./u01/oradata/prodora/8.0.6/network/admin/PROD_ebstest/listener.ora
    # $Header: admk80ln_ux.sql 115.13 2003/04/03 08:05:06 skghosh noship $
    # LISTENER.ORA For Oracle Applications
    # This file is automatically generated
    APPS_PROD =
    (ADDRESS_LIST =
    (ADDRESS= (PROTOCOL= TCP)(Host= ebstest)(Port= 1626))
    SID_LIST_APPS_PROD =
    (SID_LIST =
    ( SID_DESC = ( SID_NAME = FNDSM_PROD )
    ( ORACLE_HOME = /u01/oradata/prodora/8.0.6 )
    ( PROGRAM = /u01/oradata/prodappl/fnd/11.5.0/bin/FNDSM )
    ( envs='MYAPPSORA=/u01/oradata/prodappl/APPSPROD_ebstest.env,PATH=/usr/bin:/usr/ccs/bin:/bin,FNDSM_SCRIPT=/u01/oradata/prodcomn/admin/scripts/PROD_ebstest/gsmstart.sh' )
    ( SID_DESC = ( SID_NAME = FNDFS )
    ( ORACLE_HOME = /u01/oradata/prodora/8.0.6 )
    ( PROGRAM = /u01/oradata/prodappl/fnd/11.5.0/bin/FNDFS )
    ( envs='EPC_DISABLED=TRUE,NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1,LD_LIBRARY_PATH=/usr/dt/lib:/usr/openwin/lib:/u01/oradata/prodora/8.0.6/lib,SHLIB_PATH=/usr/lib:/usr/dt/lib:/usr/openwin/lib:/u01/oradata/prodora/8.0.6/lib,LIBPATH=/usr/dt/lib:/usr/openwin/lib:/u01/oradata/prodora/8.0.6/lib,APPLFSTT=PROD,APPLFSWD=/u01/oradata/prodappl/admin' )
    STARTUP_WAIT_TIME_APPS_PROD = 0
    CONNECT_TIMEOUT_APPS_PROD = 10
    TRACE_LEVEL_APPS_PROD = OFF
    LOG_DIRECTORY_APPS_PROD = /u01/oradata/prodora/8.0.6/network/admin
    LOG_FILE_APPS_PROD = APPS_PROD
    TRACE_DIRECTORY_APPS_PROD = /u01/oradata/prodora/8.0.6/network/admin
    TRACE_FILE_APPS_PROD = APPS_PROD

  • Windows Server 2008 SP2 randomly reboots due to lsass.exe failed with status code 255

    Hello,
    Any help on this issue would be greatly appreciated.  I have an older Windows Server 2008 SP2 (I don't believe it is R2) (running SQL Server 2008 and SSRS 2008 on the machine) that is crashing randomly
    during business hours.  Looking into the event logs, I have found the following:
    Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
    time 0x01d066d9669a3e1c.
    A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255.  The machine must now be restarted.
    The process wininit.exe has initiated the restart of computer RIDEDB02 on behalf of user  for the following reason: No title for this reason could be found
     Reason Code: 0x50006
     Shutdown Type: restart
     Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255.  The system will now shut down and restart.
    I found a Hot Fix for a similar issue (https://support.microsoft.com/en-us/kb/2732595?wa=wsignin1.0), but it appeared to only be applicable to Windows Server 2008 R2 and Windows 7.
    A few hours later, the crash happened again, with a slightly different error:
    The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819.  The system will now shut down and restart.
    Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
    time 0x01d066fa9d74c5d7.
    A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005.  The machine must now be restarted.
    The security package Kerberos generated an exception. The exception information is the data
    I have been unable to find a reason for these exceptions and the server rebooting.  Any thoughts or ideas on how I can correct this error so it doesn't reboot our server again?  .
    Thank you,
    Ben

    Hello,
    Any help on this issue would be greatly appreciated.  I have an older Windows Server 2008 SP2 (I don't believe it is R2) (running SQL Server 2008 and SSRS 2008 on the machine) that is crashing randomly
    during business hours.  Looking into the event logs, I have found the following:
    Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
    time 0x01d066d9669a3e1c.
    A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255.  The machine must now be restarted.
    The process wininit.exe has initiated the restart of computer RIDEDB02 on behalf of user  for the following reason: No title for this reason could be found
     Reason Code: 0x50006
     Shutdown Type: restart
     Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255.  The system will now shut down and restart.
    I found a Hot Fix for a similar issue (https://support.microsoft.com/en-us/kb/2732595?wa=wsignin1.0), but it appeared to only be applicable to Windows Server 2008 R2 and Windows 7.
    A few hours later, the crash happened again, with a slightly different error:
    The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819.  The system will now shut down and restart.
    Faulting application lsass.exe, version 6.0.6002.18541, time stamp 0x4ec3ca01, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8d118, exception code 0xc0000005, fault offset 0x00000000000011ad, process id 0x284, application start
    time 0x01d066fa9d74c5d7.
    A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005.  The machine must now be restarted.
    The security package Kerberos generated an exception. The exception information is the data
    I have been unable to find a reason for these exceptions and the server rebooting.  Any thoughts or ideas on how I can correct this error so it doesn't reboot our server again?  .
    Thank you,
    Ben

  • Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time when trying to set custom property.

    Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time, when trying to set custom property.
    anyone have any idea

    Hi
    Stumbled upon the resolution myself. The Bean Area item needs to be set to Visible=Yes in the property palette for the bean within Forms Builder, and also the implementation class also in the bean's properties must match exactly the package & class name specified in the PJC (my full implementation class string had to be set to oracle.forms.demos.runApplication).
    As this bean has no user interface component, and since the Visible property has to be set to Yes, to avoid having a random square shape for the bean sitting on the form's canvas, I also set the Width and Height properties for the bean to 0.001. This does show a very small dot on the form, but that will be acceptable.
    So in summary there has been a change for PJC / Bean Areas between 6i and 10g Forms, in 6i you could have the Bean Item to be set Visible=No, and the SET_CUSTOM_ PROPERTY built-in would work, however in 10g Forms the Bean Item must be set to Visible=Yes for the SET_CUSTOM_PROPERTY built-in to work.
    Daryl

  • Sometime fail to call servlet ERROR message: java.io.FileNotFoundException: Response: '500: Internal Server Error' for url:.

              Error:
              java.io.FileNotFoundException: Response: '500: Internal Server Error' for url:
              'http://www.xxxx.com//myServlet/anyfile.exml'
              at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:380)
              The URL is correct.
              When it fails, on IE browser, receive the following message,
              ·     The RPC server is unavailable
              ·     The remote procedure call failed.
              Servlet receives xml and set it into session.
              This class set or get session.
              Servlet is called many times.
              Using weblogic 8.1
              

              Error:
              java.io.FileNotFoundException: Response: '500: Internal Server Error' for url:
              'http://www.xxxx.com//myServlet/anyfile.exml'
              at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:380)
              The URL is correct.
              When it fails, on IE browser, receive the following message,
              ·     The RPC server is unavailable
              ·     The remote procedure call failed.
              Servlet receives xml and set it into session.
              This class set or get session.
              Servlet is called many times.
              Using weblogic 8.1
              

  • Cisco Catalyst 6500 version 12.2(33)SXI13 configured as DHCP server for a VLAN responds to Windows 7 client with status code NOA

    Can anyone help figure out why the Catalyst 6509 is not able to assign an IPv6 address? Thank you.
    Cisco Catalyst 6500 version 12.2(33)SXI13 configured as DHCP server for a VLAN responds to Windows 7 client with status code NOADDRS-AVAIL(2). My configuration on the 6500 for the DHCPv6 server is:
    ipv6 dhcp database disk0://DHCPV6-DB
    ipv6 dhcp pool VLAN206IPV6
     prefix-delegation pool VLAN206IPV6-POOL
     dns-server 2620:B700:0:1001::53
     domain-name global.bio.com
    ipv6 local pool VLAN206IPV6-POOL 2620:B700:0:12C7::/65 65
    interface Vlan206
     description *** IPv6 Subnet ***  
     ip address 10.2.104.2 255.255.255.0
     ipv6 address 2620:B700:0:12C7::2/64
     ipv6 nd prefix 2620:B700:0:12C7::/64 14400 14400 no-autoconfig
     ipv6 nd managed-config-flag
     ipv6 dhcp server VLAN206IPV6
     standby version 2
     standby 0 ip 10.2.104.1
     standby 0 preempt
     standby 6 ipv6 2620:B700:0:12C7::1/64
     standby 6 preempt
    I'm getting a result from my debug as follows:
    Apr 10 16:28:02.873 PDT: %LINK-3-UPDOWN: Interface GigabitEthernet2/2, changed state to up
    Apr 10 16:28:02.873 PDT: %LINK-SP-3-UPDOWN: Interface GigabitEthernet2/2, changed state to up
    Apr 10 16:28:02.877 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2, changed state to up
    Apr 10 16:28:03.861 PDT: IPv6 DHCP: Received SOLICIT from FE80::5D5E:7EBD:CDBF:2519 on Vlan206
    Apr 10 16:28:03.861 PDT: IPv6 DHCP: detailed packet contents
    Apr 10 16:28:03.861 PDT:   src FE80::5D5E:7EBD:CDBF:2519 (Vlan206)
    Apr 10 16:28:03.861 PDT:   dst FF02::1:2
    Apr 10 16:28:03.861 PDT:   type SOLICIT(1), xid 8277025
    Apr 10 16:28:03.861 PDT:   option ELAPSED-TIME(8), len 2
    Apr 10 16:28:03.861 PDT:     elapsed-time 101
    Apr 10 16:28:03.861 PDT:   option CLIENTID(1), len 14
    Apr 10 16:28:03.861 PDT:     00010001195FD895F01FAF10689E
    Apr 10 16:28:03.861 PDT:   option IA-NA(3), len 12
    Apr 10 16:28:03.861 PDT:     IAID 0x0FF01FAF, T1 0, T2 0
    Apr 10 16:28:03.861 PDT:   option UNKNOWN(39), len 32
    Apr 10 16:28:03.861 PDT:   option VENDOR-CLASS(16), len 14
    Apr 10 16:28:03.861 PDT:   option ORO(6), len 8
    Apr 10 16:28:03.861 PDT:     DOMAIN-LIST,DNS-SERVERS,VENDOR-OPTS,UNKNOWN
    Apr 10 16:28:03.861 PDT: IPv6 DHCP: Option IA-NA(3) is not supported yet
    Apr 10 16:28:03.861 PDT: IPv6 DHCP: Sending ADVERTISE to FE80::5D5E:7EBD:CDBF:2519 on Vlan206
    Apr 10 16:28:03.861 PDT: IPv6 DHCP: detailed packet contents
    Apr 10 16:28:03.861 PDT:   src FE80::21D:E6FF:FEE4:4400
    Apr 10 16:28:03.861 PDT:   dst FE80::5D5E:7EBD:CDBF:2519 (Vlan206)
    Apr 10 16:28:03.861 PDT:   type ADVERTISE(2), xid 8277025
    Apr 10 16:28:03.861 PDT:   option SERVERID(2), len 10
    Apr 10 16:28:03.865 PDT:     00030001001DE6E44400
    Apr 10 16:28:03.865 PDT:   option CLIENTID(1), len 14
    Apr 10 16:28:03.865 PDT:     00010001195FD895F01FAF10689E
    Apr 10 16:28:03.865 PDT:   option STATUS-CODE(13), len 15
    Apr 10 16:28:03.865 PDT:     status code NOADDRS-AVAIL(2)
    Apr 10 16:28:03.865 PDT:     status message: NOADDRS-AVAIL

    Hello,
    maybe hitting the following bug.
    Pv6 Address Assignment Support for IPv6 DHCP Server
    CSCse81385
    Hope this helps

  • Hostname Verification failed for certificate with CommonName 'gawlsdev02.ss

    Hi All,
    I want to know the meaning and the reason of this exception:
    <Jun 17, 2010 2:05:52 PM EDT> <Warning> <Security> <BEA-090504> <Certificate chain received from gawlsdev02 - 147.141.83.104 failed
    hostname verification check. Certificate contained gawlsdev02.ssga.statestr.com but check expected gawlsdev02>
    <Jun 17, 2010 2:05:52 PM EDT> <Debug> <TLS> <000000> <Hostname Verification failed for certificate with CommonName 'gawlsdev02.ssga.
    statestr.com' against hostname: gawlsdev02>
    thanks in advance.

    When Webloigic Server tries to validate the certificate, it compares te CN of the certificate with the hostname from where the request is coming from.
    If they don't match, hostname verfication fails and SSL connection is not established.
    In your case I see the CN is gawlsdev02.ssga.statestr.com whereas WLS is expecting it to be gawlsdev02.
    U can use this option to ignore host name verification
    -Dweblogic.security.SSL.ignoreHostnameVerification=true
    To know about other SSL issues, u can refer this
    http://weblogic-wonders.com/weblogic/2010/01/28/troubleshooting-ssl-issues/
    -Faisal

  • Lync 2013 Logon Failing (HTTP status code 500) No valid security token

    Hello there,
    I'm in the process of deploying Lync 2013.  I have the pool deployed and everything is at least running.  I can access the control panel and provision users.  However when I try to logon to the Lync Client I get a DNS error.  The DNS
    error appears to be misleading and is a result of the earlier auto-detection methods failing.
    However using the Lync Connectivity Analyzer I get a "No valid security token." error.  This doesnt matter if I use auto-detection or manual pointing the Connectivity Analyzer to the pool servers.
    [3/2/2015 9:34:15 AM] [ERROR] Reason: Internal server error (HTTP status code 500)
    [3/2/2015 9:34:15 AM] [ERROR] Ms-Diagnostics-Fault ErrorId: 28020, Reason: No valid security token.
    [3/2/2015 9:34:15 AM] [CRITICAL] The credentials were not authorized by the server. Please verify your login credentials and try again.
    [3/2/2015 9:34:15 AM] [DEBUG] System.Exception: Exception of type 'System.Exception' was thrown.
    at Microsoft.LyncServer.WebServices.WebTicketManager.WTExceptions(String exText)
    at Microsoft.LyncServer.WebServices.WebTicketManager.<AcquireTicketAsync>d__19.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.WebTicketManager.<AcquireOpaqueTicketAsync>d__14.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<AuthenticationRequired>d__2a.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<ParseResponse>d__16.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    Im a bit stumped where to go next.
    Thanks.

    Manually entering the server also fails and does not provide much to help "We're having trouble connecting to the server. If this continues, please contact your support team."
    I found that each time I try to logon it generates a Schannel Error on the server.  "A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 51.
    The Windows SChannel error state is 1106."
    There seems to be a lot more information on that than the previous "Internal Error" message I was trying to deal with.
    https://social.technet.microsoft.com/Forums/office/en-US/41718327-203f-445f-8657-87b0a8545ead/lync-2013-client-signin-issue-with-lync-2013-server?forum=lyncprofile
    Actually I just found the Lync Server Front-End is stuck "starting" so that would explain why I cannot login.  However I re-issued my certificate to make sure the primary CN matched "lync.domain.tld" and it still wont start.
    https://expertslab.wordpress.com/2014/04/23/lync-server-2013-front-end-service-stuck-on-starting/
    I think my problem is the certificate.  I have been trying to use selfSSL7 to generate the certificate for testing but it does not support creating SAN entries so I have entered all the FQDNs as CN entries.
    Im going to get another method to generate the self-signed certificate for testing.

  • HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 500 with th

    hello friend,
    I have developed a proxy to JDBC synchronous scenario.
    My scenario works like this.
    i run an abap program which calls a client proxy,
    the proxy fetches the data from database table and returns the data in the ABAP program.
    My program is working fine but there is a small problem.
    when i run the report for the first time, it gives me an exception while calling proxy
    HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 500 with the description Timeout
    and when i run the report for the second time with same variant it works fine.
    i can see the exception mostly in the morning when i run the report for the first time
    please help me to find the solution of this problem.
    thanks
    kannu.

    1. Increase the proctimeout in smicm as per note - 824554
    2.   Application threads in the J2EE engine might have got consumed in high load situations.
    Increase the count of application threads in config tool at location Config Tool -> cluster-data ->
    <configuration template> -> <instance-ID> -> managers -> ApplicationThreadManager ->
    MaxThreadCount
    3.    Increase the parameter ServletInputStreamTimeout from 180000 to 1728000000.
    Steps for setting this parameter:
    a.   If you have configured ICM to forward requests to the J2EE dispatcher then apply Note
    1048692. If the problem is not resolved, then apply section b.
    b.   The request bytes are reaching the Engine too slowly
    i.    Start the configtool in <J2EE>/configtool directory
    ii.    Browse the tree in the left pane
    cluster-data -> Global server configuration -> services -> http
    iii.    Press the ServletInputStreamTimeout key in the keylist on the right
    iv.    Change the value of the "Value" field at the bottom of the right pane to the
    preferred one (in milliseconds).
    -1 means there is no timeout - that is unless the full request comes into a single
    chunk, an error will be thrown
    180000 means the Engine would wait for 3 minutes for any byte to be entered in
    the stream.
    1728000000 means the Engine would wait for 20 days for any byte to be entered
    in the stream 
    v.    Press the "Set" button in the top-right corner
    vi.    Select from the menu File -> Apply and confirm all popups.
    vii.    Restart the Engine for changes to take effect

Maybe you are looking for