Sharepoint connector not starting

Hi,
I have just started to play with the connector and when i create new connector it allows me to create even though the creation bombs out
and when i start it manually via the web admin console it bombs out with the error:
Please verify that the connector manager is running and that the connectors.xml is correctly configured
the connector manager is running well with the groupwise connector and the mobility connector though
below is my xml file but i am not sure what to do to make this work
would anyone have any suggestions?
many thanks in advance
Maarten
<config>
<connectors>
<id>default</id>
<log>
<output>/var/log/datasync/syncengine/connectorManager.log</output>
<level>debug</level>
</log>
<manageAutomatically>yes</manageAutomatically>
<defaults>
<connector>
<syncengine>
<host>127.0.0.1</host>
<port>8124</port>
</syncengine>
<log>
<level>debug</level>
<output>/var/log/datasync/connectors/%(id)s-AppInterface.log</output>
</log>
</connector>
</defaults>
<installedConnectors>
<connector>
<type>mobility</type>
<id>default.pipeline1.mobility</id>
</connector>
<connector>
<type>groupwise</type>
<id>default.pipeline1.groupwise</id>
</connector>
<connector>
<type>sharepoint</type>
<id>default.pipeline1.Sharepoint</id>
</connector>
<connector>
<type>sharepoint</type>
<id>default.pipeline1.Sharepoint_test</id>
</connector>
</installedConnectors>
</connectors>
</config>

Was NTLM installed on the server already and you had to re install it? Or was it not installed at all.

Similar Messages

  • Sharepoint Lotus Notes Connector Not Starting

    We are trying to install the Lotus Notes Connector on our SharePoint 2013 Farm. We are currently running a multi-tier farm. 
    We are running on Windows server 2012, SharePoint 2013 and Lotus Notes 8.0.2. As we provision the Lotus Notes connector with our Crawl account (which has local administration on all of the servers) it seems to create the application pool but then the service
    goes from a “starting” to a “stopped” state within a minute.
    From the ULS logs I can see this error occur
    04/29/2014 10:33:17.00 OWSTIMER.EXE (0x2190) 0x0FBC SharePoint Server Search Connectors:Notes dj8t High Exception caught in Search Notes Provisioning. Notes web service instance NOT PROVISIONEDSystem.ComponentModel.Win32Exception (0x80004005): Access is
    denied at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited) at System.Diagnostics.Process.Kill() at Microsoft.Office.Server.Search.Administration.NotesWebServiceInstance.Provision() 11d88b9c-f791-90a7-3cae-b4dabbc1b734
    04/29/2014 10:33:17.08 OWSTIMER.EXE (0x2190) 0x0FBC SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject NotesWebServiceInstance. Version: 1291875 Ensure: False, HashCode: 18663991, Id: 24190eed-b9c6-4749-aa44-c7432897c0a3, Stack: at Microsoft.Office.Server.Search.Administration.NotesWebServiceInstance.Provision()
    at Microsoft.SharePoint.Administration.SPServiceInstanceJobDefinition.Execute(Guid targetInstanceId) at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition.ExecuteAdminJob(Guid targetInstanceId) at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition
    jd, Guid targetInstanceId, Boolean isTimerService, Int32& result) at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result) 11d88b9c-f791-90a7-3cae-b4dabbc1b734
    Any feedback/assistance would be greatly appreciated.

    Hi  ,
    According to your error message, it says that when provisioning  NotesWebServiceInstance, access is denied at getting process handle.
    For your issue, you can refer to the similar thread:
    http://social.technet.microsoft.com/Forums/en-US/cd4bdf09-f17d-4885-9a81-7fedbbb0984d/sharepoint-2010-lotus-notes-connector-not-working-for-ln-v65?forum=sharepointadminprevious
    http://www.ericharlan.com/Moss_SharePoint_2007_Blog/sharepoint-2010-lotus-notes-connector-service-a197.html
    Thanks,
    Eric
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
    contact [email protected]
    Eric Tao
    TechNet Community Support

  • SharePoint connector does not start up

    Hello,
    I just have installed a new DataSync server with the SharePoint connector.
    The NTLM rpm is installed
    Using the FireFox browser on the DataSync server, I can go to the SharePoint server and be authenticated.
    The DataSync server does not have a proxy...
    But I got an error when I am starting the connector :
    The error is
    2012-07-24 13:58:58.321 DEBUG_VERBOSE [CP WSGIServer Thread-3] [WebsHandler:56] [userID:] [eventID:] [objectID:] [] <urlopen error [Errno 110] Connection timed out>
    Any idea ....?
    Tx for your help ...
    Stephan

    ---Solved---
    Be sure your DataSync server where the SharePoint connector is running does have an Internet connection....
    The Connector has to find and download some info from there ...
    Stephan
    ---Solved---

  • SharePoint Online workflow not starting

    Hi All,
    I am an administrator for a company and I have been asked to create a workflow for them.
    I created 2 workflows using SharePoint designer 2013. The 2010 workflow works as expected.
    I created the 2013 workflow because I can use loops. However the 2013 workflow doesn't automatically start when an item is created. but works if I start it manually. I have checked and made sure that the check box is ticked for the workflow to start automatically.
    The workflows go like this.
    Step: Query Type
     If Current Item:Query_Type equals Phone
      Set Status to Opportunity
     Else
     If Current Item:Query_Type equals Email
      Email Current Item:Sales_Rep2
      Pause for 0 days, 0 hours, 15 minutes
      If Current Item:Follow_Up equals No
       Email Current Item:Sales_Rep2
    Step: Rental or Not
     If Current Item:Rental equals Yes
      Email Current Item:Sales_Rep2
      Pause for 0 days, 1 hours, 0 minutes
      If Current Item:Quote_Sent equals No
       Email Current Item:Sales_Rep2
      Else
      If Current Item:Rental equals No
       Email Current Item:Sales_Rep2
       Pause until Current Item:Date to Send Quote
       Email Current Item:Sales_Rep2
    And the 2013 one goes like this
    Stage:Follow Up
     Loop: Email to manager
      The contents of this loop will run repeatedly while: Current Item:Follow_Up equals No
       Pause for 0 days, 1 hours, 0 minutes
       If Current Item:Follow_Up equals No
        Email Current Item:Manager
     If Current Item:Follow_Up equals Yes
      Set Status to Opportunity
    Transition to stage
     Go to Rental or Not
    Stage:Rental or Not
     Loop: Escalation
      The contents of this loop will run repeatedly while: Current Item:Quote_Sent equals No
       Pause for 2 days, 0 hours, 0 minutes
       If Current Item:Quote_Sent equals No
        Email Current Item:Manager
     Loop: Escalation
      The contents of this loop will run repeatedly while: Current Item:Quote_Sent equals No
       Pause for 7 days, 0 hours, 0 minutes
       If Current Item:Quote_Sent equals No
       and Current Item:Date to Send Quote is greater than Current Item:Date to Send Quote
        Email Current Item:Manager
    Transition to stage
     Go to End of Workflow
    If this makes sense? If not can anybody give me advice on how to get this working the way it is expected to work?

    Hi,
    From your description, After you modified the workflow and added "App Step" to it and "Pause" actions apart from few other modifications, you got the issue that
    SharePoint 2013 Workflow not starting when a new item is crated.
    Whether you got the issue Before you modified the workflow.
    I have done a test in my SharePoint 2013 and it works fine.
    I suggest you update SharePoint to the latest CU.
    Here is an blog similar with your issue, you can use as a reference:
    http://blogs.msdn.com/b/sridhara/archive/2014/08/19/fix-sharepoint-2013-workflow-recursion-prevention-part-1.aspx
    Best Regards,
    Lisa Chen
    Lisa Chen
    TechNet Community Support

  • PowerPivot for SharePoint 2013 Configuration not starting

    Dear,
    I have
    Windows 2008 R2 SP1 (up to date version)
    SQL Server 2012 SP1  PowerPivot For SharePoint (11.1.3000.0 -> the number is from the control Panel)
    But I try to run the command PowerPivot for SharePoint 2013 Configuration, the wizard is not starting : it closed with an error
    If someone has idea, he is welcomed
    Regards
    Bohor

    hi Muhammad,
    thanks a lot for your help but what is "Powershare"?
    About running Powerpivot configuration Tools with administrator rights , I have tried without success :-(
    I have found the error log in the Windows event viewer, maybe it'll be helpful
    Application : PowerPivotSPAddinConfiguration.exe
    Version du Framework : v4.0.30319
    Description : le processus a été arrêté en raison d'une exception non gérée.
    Informations sur l'exception : System.TypeInitializationException
    Pile :
    à Microsoft.AnalysisServices.SPAddin.Configuration.Tool.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
    à System.Windows.Application.<.ctor>b__1(System.Object)
    à System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    à MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    à System.Windows.Threading.DispatcherOperation.InvokeImpl()
    à System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    à System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    à System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    à System.Windows.Threading.DispatcherOperation.Invoke()
    à System.Windows.Threading.Dispatcher.ProcessQueue()
    à System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    à MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    à MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
    à System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    à MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    à System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
    à MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
    à MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
    à MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
    à System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
    à System.Windows.Application.RunDispatcher(System.Object)
    à System.Windows.Application.RunInternal(System.Windows.Window)
    à Microsoft.AnalysisServices.SPAddin.Configuration.Tool.App.Main()
    and there is another message just after that said that the faulting module is
    C:\Windows\system32\KERNELBASE.dll
    regards
    Bohor

  • SharePoint Retention Policy workflow does not start

    Hi,
    Using Nintex workflows I have created a workflow and attached it to a content type and tested that it runs manually ok.  I want it to run according to a retention policy, and so I created a policy based on one of the content type's date fields to start
    my workflow automatically.  When I manually run the timer jobs I see the following error in ULS logs and the workflow does not start.  Interestingly if I amend the policy to do something simple like move the item to the recycle bin, that works fine.
    Can anyone suggest what is wrong and where I can go from here to find the issue?
    Thanks
    Error running the expiration action on item <document url> .  Error:  System.InvalidOperationException:
    The workflow with id=<workflow id > is no longer available.    
     at Microsoft.Office.RecordsManagement.PolicyFeatures.WorkflowExpirationAction.RunExpirationWithPostActions(SPListItem
    item, XmlNode parametersData, DateTime expireDate)    
     at Microsoft.Office.RecordsManagement.PolicyFeatures.BaseExpirationAction.Microsoft.Office.RecordsManagement.PolicyFeatures.IExpirationActionWithPostActions.OnExpirationWithPostActions(SPListItem
    item, XmlNode parametersData, DateTime expireDate)    
     at Microsoft.Office.RecordsManagement.PolicyFeatures.ExpirationTask.ExpirationActionData.RunExpirationAction(SPListItem
    item, DateTime expireDate)    
     at Microsoft.Office.RecordsManagement.PolicyFeatures.ExpirationTask.<>c__DisplayClass19.<ProcessExpiredItems>b__17(SPListItem
    item)    
     at Microsoft.Office.Server.Utilities.MonitoredScopeWrapper.RunWithMonitoredScope(Action code)  
     at Microsoft.Office.Server.Utilities.ContentIterator.ProcessItem(SPListItem item, Boolean fIncludeFolderItems,
    MonitoredScopeWrapper monitoredScopeWrapper, ItemProcessor itemProcessor, ItemProcessorErrorCallout errorCallout)

    Hi,
    Based on your description, my understanding is that the Retention Policy cannot start the Nintex workflow.
    To narrow the issue scope, I recommend to check the things below:
    Create a SharePoint 2010 Reusable workflow for the same content type or 2013 list workflow and modify the Retention Policy to start this workflow, and then check how it works.
    Create Retention Policy with the Nintex workflow in another list and then compare the results.
    Thanks,
    Victoria
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Victoria Xia
    TechNet Community Support

  • Sharepoint 2013 workflow does not start when item is created by another workflow

    Hi I am having the next problem, I have a workflow on list B that starts when a new item is created. If I created the item manually the workflow works. Now I have a list A that has a workflow that creates a new item in List B. The problem is that when
    de workflow in list A creates the list item in list B the workflow does not start.
    I've used an account that is collection owner, an account that only has contribute permision and nothing works.
    Any ideas?
    0down
    votefavorite
    Hi I am having the next problem, I have a workflow on list B that starts when a new item is created. If I created the item manually the workflow works. Now I have a list A that has a workflow that creates a new item in List B. The problem is that when de workflow
    in list A creates the list item in list B the workflow does not start.
    I've used an account that is collection owner, an account that only has contribute permision and nothing works.
    Any ideas?
    0down
    votefavorite
    Hi I am having the next problem, I have a workflow on list B that starts when a new item is created. If I created the item manually the workflow works. Now I have a list A that has a workflow that
    creates a new item in List B. The problem is that when de workflow in list A creates the list item in list B the workflow does not start.
    I've used an account that is collection owner, an account that only has contribute permision and nothing works.
    Any ideas?

    Hi Courfeyrak,
    Here is another similar post with a workaround, you can try using the event receiver on listB item to start the workflow, when the listB item is created or updated by the workflow associated with listA.
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/19f71e38-7c04-430e-aa6b-764cbbf18c1c/2013-workflow-does-not-start-on-item-created-by-a-different-worklow?forum=sharepointcustomization
    Thanks,
    Daniel Yang
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Daniel Yang
    TechNet Community Support

  • SCOM Alert Connector - not updating the start time and finish time

    When I am monitoring the status of connectors in service manager console, I found that for SCOM Alert Connector the Start Time and Finish Time are not updating. Previously it was updated daily. As of now, service manager is working fine but would like
    to check will it create any issues? Even I have cliked on Synchronize Now, but there is no update. Please guide me on this to trouble shoot further? Thanks.

    Hi,
    Based on my research, the Start Time and Finish Time values are not updated when an alert connector is synchronized. These values are only updated when alert data is transferred between Operations Manager 2007 and Service
    Manager.
    More details, please refer to the link below:
    http://technet.microsoft.com/en-us/library/hh495609.aspx
    In addition, here is a blog about troubleshooting for SCSM and SCOM alert connector:
    http://blogs.technet.com/b/servicemanager/archive/2010/04/14/troubleshooting-tips-for-your-scsm-scom-alert-connector.aspx
    Regards,
    Yan Li
    Regards, Yan Li

  • Windows sharepoint admin service not starting

    Hi,
    I found my SharePoint admin service is not started. when tried to start manually, it is throwing an error saying that it couldn't start.
    Tried troubleshooting : IISRESET, stsadm -o execadmsvcjobs, run configuration wizards, PS config, service sharepoint web services start & stop.
    not able to start to SharePoint admin services.
    Could someone please give me suggestion on this to start the admin service.
    Not tried rebooting the server, as i need prior approvals from my superiors for doing the same.
    Thanks
    Badri

    Hey there
    Well Microsoft patch kb2677070 automatically updates revoked security certificates. It lets  Windows Server go out to the internet. But if your server is firewalled away in a DMZ and does not have unfettered internet access, this call to the find the updated
    revocation list will fail. When it does, the SharePoint 2010 Administration service will not start.
    Open Group Policy Editor. From start->search box, type in gpedit.msc and hit return.
    Navigate to Computer Configuration->Windows Settings->Public Key Policies-> Certificate Path Validation Settings.
    Click on the “Network Retrieval” tab.
    Check the “Define these policy settings” and uncheck the “Automatically update certificates in the Microsoft Root Certificate Program”
    Click OK
    For further details visit http://sharepointlark.wordpress.com/2013/05/29/sharepoint-2010-administration-service-wont-start/ 
    Thanks
    ~Dex

  • Sharepoint Designer - Two step List Workflow task item is not changing the status from not started to Complete

    Hi 
    Using SPD i am creating list workflow.
    Scenario: Employee submits a request . Task assign to manager. Manager can either approve/ reject. If approve then change the state column to "done". If rejected the state column to "Rejected".
    Problem is "Assign a to do item" is assigning the task to manager. But after manager approves the status in the task list not changed to "Completed". Still it is showing "Not started". I dont want to manually complete the task.
    Please help me for automatic process. 
    What i should do to change the status to "Complete" automatically after manager approval
    Regards
    Jhanani
    Janani.R

    Hi Janani,
    From your description, you would like to create an approval workflow for a list. When an employee submit a request to the list, an approval task should be assigned to manager, then manager could approve or reject the request. From the request list,
    we should be able to see the Approval task’s status.
    Not understand the reason of designing the workflow to two steps, an approval action should be enough from my understanding. For producing, I create a list named Request list, then customize it in InfoPath form to add a Request field for stating request
    content. Then add a workflow to list named Approval task, add the action of Start an approval process with administrator and make the workflow automatically start when item is added.
    The image below shows the status of Adding items, Approving and Rejecting. Please check if it could meet your requirement.
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • Sharepoint Designer workflow not starting or listing.

    I have some designer workflows running on my list. One of them is a workflow that runs on
    item creation. Sometimes this workflow is skipped when an item is created in the list. This workflow does not get listed for the item. This happens just once in a while but it affects the application a lot. Sometimes none of the workflows are
    listed for the particular item when i check the workflow settings.
    P.S:- All items created using user accounts only

    if the Item is created using System Account, the workflow will not start automatically. check whether there is any difference between the items created withno workflow and the working ones.
    Qiao Wei <br/> My blog:http://blog.goobol.com

  • SharePoint Connector Error

    Someone can helpme, when a use the configuration manager for install the sharepoint connector, throw this warning. .
    I tried to start component in Adobe Workbench 10, but i had this error .
    Note: the service Connector for Microsoft SharePoint is not present in Adminui.
    How i can resolve it?
    Thanks.

    The server.log shows the below error many times :-
    2012-02-02 09:12:10,090 INFO  [com.adobe.monitor.stats.SystemStatistic] (Thread-25) cannot get LFS_Foundation.properties file
    2012-02-02 09:12:10,091 ERROR [STDERR] (Thread-25) java.lang.NullPointerException
    2012-02-02 09:12:10,091 ERROR [STDERR] (Thread-25)     at java.util.Hashtable.put(Hashtable.java:394)
    2012-02-02 09:12:10,091 ERROR [STDERR] (Thread-25)     at java.util.Properties.setProperty(Properties.java:143)
    2012-02-02 09:12:10,091 ERROR [STDERR] (Thread-25)     at com.adobe.monitor.stats.PropertiesMappingUtil.setValueToProperties(PropertiesMappingUtil. java:49)
    2012-02-02 09:12:10,091 ERROR [STDERR] (Thread-25)     at com.adobe.monitor.stats.SystemCacheManager.addAndUpdateStatisticsCache(SystemCacheManager .java:43)
    2012-02-02 09:12:10,091 ERROR [STDERR] (Thread-25)     at com.adobe.monitor.stats.SystemInfoRetrievalThread.retrieveInfo(SystemInfoRetrievalThread. java:110)
    2012-02-02 09:12:10,091 ERROR [STDERR] (Thread-25)     at com.adobe.monitor.stats.SystemInfoRetrievalThread.run(SystemInfoRetrievalThread.java:70)
    The default location of this file is <ADEP_Install_Directory>\configurationManager\config\solcomp. I think you might have deleted this file by mistake. I would recommend a clean install of the ADEP server.

  • Does the SharePoint connector support SharePoint 2010?

    Does the LiveCycle SharePoint connector support SharePoint 2010?
    If not, are there plans to add support for SharePoint 2010 in the future?
    Cheers,
    -Richard Gregg

    Hey N Santosh,
    is there a more firm timeline for SP2013 support in ES4 now?
    We're also on ES2 and SP2010 (without integration), looking to upgrade to ES4 and SP2013 (with integration) in the next couple of months and it would be handy to know if we're going to be able to do the integration from the start or if it's something we'll have to come back to later.
    Thanks
    Craig

  • Message bean does not start automatically during application server startup

    I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
    Thanks,
    Bill
    #1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
    #1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
    #1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
    #1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
    #1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
    #1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
    #1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
    #1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
    #1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    ... 12 more
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
    Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
    #1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
    #1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
    java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                    at java.lang.Class.getDeclaredConstructors0(Native Method)
                    at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                    at java.lang.Class.getConstructor0(Class.java:1930)
                    at java.lang.Class.newInstance0(Class.java:278)
                    at java.lang.Class.newInstance(Class.java:261)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                    at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                    at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at javax.security.auth.Subject.doAs(Subject.java:379)
                    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
    I've could change that yes, but the startup script doesn't seemed to have this mind.
    Regards,
    Sve

  • Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists.

    Hi
    I just now updated dec 2013 c.u to sharepoint server 2010 sp2
     I get this error in event viewer when I browse  web applications  , they not open even
    Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker' from assembly 'Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.
    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
    Process Name: OWSTIMER
    Process ID: 3836
    AppDomain Name: DefaultDomain
    AppDomain ID: 1
    Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:548f72e6a39f401e95e92711aea13c45#authority=urn:uuid:9aebe976322541d280e4bd3799fa283f&authority=https://spfwf01:32844/Topology/topology.svc
    Active Endpoints: 2
    Failed Endpoints:1
    Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists.
    adil

    This messge I get initially I get two times (1)
    SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
    Process Name: w3wp
    Process ID: 4600
    AppDomain Name: /LM/W3SVC/2141356646/ROOT-1-130405218187772398
    AppDomain ID: 2
    Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:548f72e6a39f401e95e92711aea13c45#authority=urn:uuid:9aebe976322541d280e4bd3799fa283f&authority=https://spfwf01:32844/Topology/topology.svc
    Active Endpoints: 2
    Failed Endpoints:1
    Affected Endpoint: http://spfapp02:32843/548f72e6a39f401e95e92711aea13c45/MetadataWebService.svc
    aftert this message three times  (2)
    The Managed Metadata Service 'Managed Metadata Service' is inaccessible.
    and after (3)
    The health service has removed some items from the send queue for management group "MOJOmanagement" since it exceeded the maximum allowed size of 15 megabytes.
    after (4)
    Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists.
    and this time   I seen I am unable to browse web applications
    and
    Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker' from assembly 'Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.
    adil

Maybe you are looking for