Cisco CM services restart spontaneously

Hi All,
Please can anyone advise what can be the cause the Cisco CallManager services restart spontaneously?
We are running cucm version 7.0.2. Yesterday we noticed the Cisco CallManager services stopped on the puplisher, so we restarted the services. Since that time the services restarted several times spontaneously. We also have one a subscriber in the claster which is working fine.
Any ideas?
Many thanks
Marian

Hi Mateusz,
Thanks for suggestion. I have run the command and it looks very much like this bug 
"CSCte50152 : Memory leak in CCM due to Transient SIP Connections"
However, I don't see the line "operate new" which results in memory leak as suggested in "Trouble shooting core dump " section of CISCO FORUM.
Could you please have a look at this backtrace and further advise ?   Thanks in advance.
 backtrace
 ===================================
 #0  0x001db7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x00fc67a5 in raise () from /lib/tls/libc.so.6
#2  0x00fc8209 in abort () from /lib/tls/libc.so.6
#3  0x0042e53b in __gnu_cxx::__verbose_terminate_handler () from /usr/local/cm/lib/libstlport.so.5.1
#4  0x0042c251 in __cxxabiv1::__terminate () from /usr/local/cm/lib/libstlport.so.5.1
#5  0x0042c286 in std::terminate () from /usr/local/cm/lib/libstlport.so.5.1
#6  0x0042c3cf in __cxa_throw () from /usr/local/cm/lib/libstlport.so.5.1
#7  0x00a30860 in xercesc_2_7::XMLString::parseInt () from /usr/local/cm/lib/libxerces-c.so.27
#8  0x09be13ae in XMLDoc::extractElement (node=0xb3d16460, elementName=0xa872d5c, targetVal=@0x6, required=true) at XMLDocHelper.cpp:458
#9  0x09be3b8d in RemoteCCDataPassthroughRequest::decode (node=0xb3d16460) at XMLDocHelper.cpp:1582
#10 0x09be5bdc in RemoteCCRequest::decode (node=0xb3d16380) at XMLDocHelper.cpp:731
#11 0x09be60bf in XMLDoc::decode (buf=) at XMLDocHelper.cpp:322
#12 0x0959b016 in SIPStationD::processRemoteCcRequest (this=0xb3a18aa8, signal=@0xb3926b60, addr=@0x2a33d20, msg=@0x2a33e70) at ProcessSIPStationD.cpp:13531
#13 0x0959c2b3 in SIPStationD::wait_SIPReferInd (this=0xb3a18aa8, s=@0xb3926b60) at ProcessSIPStationD.cpp:4098
#14 0x095b548c in SIPStationD::fireSignal (this=0xb3a18aa8, sdlSignal=@0xb3926b60) at /vob/ccm/Common/Include/Sdl/SdlProcessBase.hpp:174
#15 0x09e4a050 in SdlProcessBase::inputSignal (this=0xb3a18aa8, rSignal=0xb3926b60, traceType=SdlSystemLog::SignalRouterThread, highPriority=0, normalPriority=0, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:396
#16 0x09e51e12 in SdlRouter::callProcess (this=0xde568e0, _sdlSignal=0xb3926b60, _deleteSignal=@0x2a34d97, _traceType=SdlSystemLog::SignalRouterThread, _hp=0, _np=0, _lp=0, _vlp=0, _lzp=0, _dbp=0) at SdlRouter.cpp:372
#17 0x09e51837 in SdlRouter::scheduler (sdlRouter=0xde568e0) at SdlRouter.cpp:282
#18 0x006b1ef3 in ACE_OS_Thread_Adapter::invoke (this=0xeec3e00) at OS_Thread_Adapter.cpp:94
#19 0x00672abf in ace_thread_adapter (args=0x0) at Base_Thread_Adapter.cpp:137
#20 0x004ae371 in start_thread () from /lib/tls/libpthread.so.0
#21 0x01066ffe in clone () from /lib/tls/libc.so.6

Similar Messages

  • Call Manager Cisco SOAP - CDRonDemand Service restarts every 8-10 minutes

    Hello there,
    I just upgraded a customer to 10.5.1.10000-7 of call manager.  Now the Call Manager Cisco SOAP - CDRonDemand Service restarts every 8-10 minutes.
    I tried:
    -rebooting the cluster (pub and sub)
    -restarting the CDR and Soap related servers
    -turning off CDR under service parameters and restarting services.
    Any other thoughts? all replication reports look good
    thanks

    Hi,
    you have probably only two options. Let a TAC person look into it if you really want to know whats wrong. 
    The other option would be to deactivate "Cisco SOAP - CDRonDemand Service" since no appplication is using CDR on demand. That service is only used when an application is pulling CDR records derectly out of the database which seems not be the case.
    Eike

  • CallManager Service Restarts

    Greetings,
    We have a CallManager running 4.1.3(sr3a). About 1-2 times a week the CallManager Service restarts. At first I thought this was occurring at the same time as backups, but I have since discovered that is not the case.
    We have noticed this for more than one customer running different versions of CallManager. It is usually occurs after hours, and most of the time it is not occuring at the same time as backups.
    The last time this occurred there were a lot of transient connections events in the app log, and then the last entry before restaring in the event log is SDL error for connectivity to the sub. (also this appears to happen on the pubs).
    Any ideas?

    Which server model?
    Available memory?
    Please check the following:
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801d2577.shtml#topic1
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801df0ed.shtml
    I widely recommend you to open a TAC case.

  • Cisco Tomcat service hung on CUCM publisher

    Hi,
    I have CUCM v7.1.5.32900-2.
    The web interface became unreachable, restarted Cisco Tomcat service fixed it.
    Does anyone know why it happened and what can be done to mitigate future occurrence.
    CUCM Cisco Tomcat Security log:
    ==============================
    2014-06-02 08:09:42,819 ERROR [http-8443-9] impl.DatabaseAccessor - updateLastSuccessfulLoginTime: Failed to execute execute procedure ImsUpdateSuccessfulLoginTime
    2014-06-02 08:09:45,691 DEBUG [DefaultQuartzScheduler_Worker-7] impl.AuthenticationDB - Constructor: 
    2014-06-02 08:09:51,808 ERROR [http-8443-9] impl.DatabaseAccessor - updateLastSuccessfulLoginTime: Exception Can't load driver java.lang.reflect.InvocationTargetException
    2014-06-02 08:09:57,947 ERROR [http-8443-9] impl.AuthenticationDB - authenticateUser: Failed to execute reset last login timeCan't load driver java.lang.reflect.InvocationTargetException
    2014-06-02 08:10:43,980 ERROR [http-8443-9] authentication.AuthenticationImpl - loginUtil: SQLException occured. Throwing IMSexception.
    java.sql.SQLException: Can't load driver java.lang.reflect.InvocationTargetException
    at com.informix.util.IfxErrMsg.getLocSQLException(IfxErrMsg.java:494)
    at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:271)
    at java.sql.DriverManager.getConnection(DriverManager.java:582)
    at java.sql.DriverManager.getConnection(DriverManager.java:207)
    at com.cisco.ccm.dbl.Connector.getConn(Connector.java:671)
    at com.cisco.ccm.dbl.Connector.connect(Connector.java:588)
    at com.cisco.ccm.dbl.Connector.connect(Connector.java:530)
    at com.cisco.ccm.dbl.Connector.createTemporaryStatement(Connector.java:851)
    at com.cisco.ccm.dbl.Connector.execute(Connector.java:953)
    at com.cisco.security.ims.impl.DatabaseAccessor.updateLastLoginTime(DatabaseAccessor.java:943)
    at com.cisco.security.ims.impl.AuthenticationDB.authenticateUser(AuthenticationDB.java:253)
    at com.cisco.security.ims.authentication.AuthenticationImpl.loginUtil(AuthenticationImpl.java:146)
    at com.cisco.security.ims.authentication.AuthenticationImpl.login(AuthenticationImpl.java:74)
    at com.cisco.platform.realm.Realm.authenticate(Realm.java:109)
    at com.cisco.platform.valve.BasicAuthenticationValve.authenticate(BasicAuthenticationValve.java:219)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:528)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
    at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:394)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:254)
    ... 24 more
    Caused by: java.lang.OutOfMemoryError: Java heap space
    =============================================
    Checked Cisco Tomcat Service logs from RTMT, noticed following in Tomcat Manager Logs:
    ========================================================
    Jun 2, 2014 8:00:24 AM org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet Manager threw exception
    java.lang.OutOfMemoryError: Java heap space
    Jun 2, 2014 8:00:27 AM org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet Manager threw exception
    java.lang.OutOfMemoryError: Java heap space
    ======================================

    Thank you Sreekanth
    Did not find anything interesting about memory in System and Application logs.
    admin:utils core active list
          Size         Date            Core File Name
    =================================================================
     299252 KB   2014-04-18 19:39:50   core.28338.11.cef.1397864390
     118156 KB   2012-11-17 02:00:36   core.13997.6.cimlistener.1353135636
     118284 KB   2011-10-29 03:04:30   core.14005.11.cimlistener.1319871870
     603908 KB   2013-09-07 02:07:57   core.18107.11.cef.1378534077
     368192 KB   2014-02-03 05:14:23   core.25216.11.cef.1391422462

  • Ask the Expert: Overview of Cisco Prime Service Catalog and Process Orchestrator Solutions

    Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about the Cisco Prime Service Catalog and Process Orchestrator solutions.
    Cisco expert Jason Davis will discuss Cisco’s network management products offered under the Cisco Prime framework. If you have questions about Cisco Prime infrastructure or data center automation with our Cisco Prime Service Catalog and Process Orchestrator solutions, join us on the Cisco Support Community.
    Jason Davis is a distinguished services engineer in the Intelligent Infrastructure Practice team of Cisco Advanced Services. His role is to provide strategic and tactical consulting for hundreds of Advanced Services customers, lead service innovation, and assess new services and technologies. Jason's primary expertise areas are in network management systems, intelligent automation, virtualization, data center operations, software-defined networking, and network programmability.
    Based out of the Research Triangle Park (RTP) campus, Jason is also responsible for administering the Research Triangle Park Network Management Lab, Cisco's largest network management lab.
    Since joining Cisco in 1998, Jason has been a frequent speaker at Cisco's Networkers and CiscoLive conferences in the United States and Europe. In the past five years he has also been involved in the conference network setup and monitoring. He is a much sought-after resource by the field sales teams to assist with presales solutions and executive briefings. He has provided strategic and tactical network management consulting for several hundred customers.
    Jason is a subject matter expert with the following products and features:
    Cisco Prime LAN management solution
    Cisco Prime infrastructure
    CiscoSecure ACS
    Cisco Prime Network Registrar
    Cisco Process Orchestrator
    Cisco Prime Service Catalog
    Cisco IP SLA
    Embedded Event Manager
    SNMPv3
    onePK and OpenFlow
    Cisco UCS
    Device instrumentation
    VMware ESX, ESXi, and vCenter
    ITIL
    Jason received his bachelor of science degree in electrical engineering from the University of Miami (FL). He has been married for 20 years and has 4 children. His interests include providing audiovisual technical support for churches and conference venues, camping and biking with his family, remote-control helicopter piloting, paintball, and recreational shooting.
    Remember to use the rating system to let Jason know if you have received an adequate response.
    Because of the volume expected during this event, Jason might not be able to answer every question. Remember that you can continue the conversation in Data Center > Intelligent Automation under the subcommunity Cisco Prime Service Catalog shortly after the event. This event lasts through September 12, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Hello Jason,
    Thank you very much for welcoming me to your expert discussion :) I feel to be in the right place, at the right time. Thank you also for answering question beyond your scope here, much appreciated. The information received will help me to go further as such I have submitted a 5 start rating for your first reply.
    That sounds promising about the LMS part so yes, I stay tuned and wait patiently.
    Ok, now let’s revert to the actual topic discussed here. Cisco Prime Service Catalog and Process Orchestrator solutions I have briefly read up on this on CCO (where elseJ) and picked out the following quote
    ---- Quote from the Cisco Prime Service Catalog Data Sheet
     Today’s end users want self-service and easy access to IT tools and services.
    Simultaneously, organizations are seeking ways to extend their cloud management
    platforms beyond self-service delivery of virtual machines and infrastructure resources
    while increasing their use of cloud-based solutions to enhance business agility and effectiveness.
    Cisco Prime™ Service Catalog offers tremendous benefits to organizations that want to unify the ways in
    which all types of IT services are ordered and fulfilled, not just infrastructure requests
    ---- un quote ---
    I try to understand what (at high level of course) happens in the back ground when an order is raised and which vendor solution your product can interact with.
    As mentioned in the quoted text, this service catalogue goes beyond the standard infrastructure.
    Let’s say, a user wants to deploy a new email services, or in your example,  extends or create a new web-portal (i.e. for HR to view and manage holiday, staff absence and benefits).
    Your solution will need to interact somehow with the 3rd party vendor application that is capable building such portal I believe.
    Without disclosing to many information, I assume the portal is linked to backend VM,s that spin up requested resources (and more magic of course). Perhaps I am mixing this up with another cisco product where a user can go on the portal and spin up virtual Firewalls, virtual Routers can be provisioned in now time.
    Out if interest; Is this product also known as Mozart? (project code within Cisco?)
    I hope query is ok.
    Best wishes
    Markus

  • Ask the Expert: Integrating Cisco Identity Service Engine (ISE) 1.2 for BYOD

    With Eric Yu and Todd Pula 
    Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions  about integrating Cisco ISE 1.2 for BYOD with experts Eric Yu and Todd Pula.
    Cisco Bring Your Own Device (BYOD) is an end-to-end architecture that orchestrates the integration of Cisco's mobile and security architectures to various third-party components. The session takes a deep dive into the available tools and methodologies for troubleshooting the Cisco BYOD solution to identify root causes for problems that stem from mobile device manager integration, Microsoft Active Directory and certificate authority services, and Cisco Enterprise Mobility integration to the Cisco Identity Services Engine (ISE). 
    Todd and Eric recently delivered a technical workshop that helps network designers and network engineers understand integration of the various Cisco BYOD components by taking a deep dive to analyze best practice configurations and time-saving troubleshooting methodologies. The content consisted of common troubleshooting scenarios in which TAC engineers help customers address operational challenges as seen in real Cisco BYOD deployments.
    Eric Yu is a technical leader at Cisco responsible for supporting our leading-edge borderless network solutions. He has 10 years of experience in the telecommunications industry designing data and voice networks. Previous to his current role, he worked as a network consulting engineer for Cisco Advance Services, responsible for designing and implementing Cisco Unified Communications for Fortune 500 enterprises. Before joining Cisco, he worked at Verizon Business as an integration engineer responsible for developing a managed services solution for Cisco Unified Communications. Eric holds CCIE certification in routing and switching no. 14590 and has two patents pending related to Cisco's medianet.   
    Todd Pula is a member of the TAC Security and NMS Technical Leadership team supporting the ISE and intrusion prevention system (IPS) product lines. Todd has 15 years of experience in the networking and information security industries, with 6 years of experience working in Cisco's TAC organization. Previous to his current role, Todd was a TAC team lead providing focused technical support on Cisco's wide array of VPN products. Before joining Cisco, he worked at Stanley Black & Decker as a network engineer responsible for the design, configuration, and support of an expansive global network infrastructure. Todd holds his CCIE in routing and switching no. 19383 and an MS degree in IT from Capella University.
    Remember to use the rating system to let Eric and Todd know if you have received an adequate response.
    Because of the volume expected during this event, Eric and Todd might not be able to answer every question. Remember that you can continue the conversation in the Security community, subcommunity AAA, Identity and NAC, shortly after the event. This event lasts through November 15, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Hi Antonio,
    Many great questions to start this series.  For the situation that you are observing with your FlexConnect configuration, is the problem 100% reproducible or is it intermittent?  Does the problem happen for one WLAN but not another?  As it stands today, the CoA-Ack needs to be initiated by the management interface.  This limitation is documented in bug CSCuj42870.  I have provided a link for your reference below.  If the problem happens 100% of the time, the two configuration areas that I would check first include:
    On the WLC, navigate to Security > RADIUS > Authentication.  Click on the server index number for the associated ISE node.  On the edit screen, verify that the Support for RFC 3576 option is enabled.
    On the WLC, navigate to the WLANs tab and click on the WLAN ID for the WLAN in question.  On the edit screen, navigate to Security > AAA and make sure the Radius Server Overwrite interface is unchecked.  When this option is checked, the WLC will attemp to send client authentication requests and the CoA-Ack/Nak via the dynamic interface assigned to the WLAN vs. the management interface.  Because of the below referenced bug, all RADIUS packets except the CoA-Ack/Nak will actually be transmitted via the dynamic interface.  As a general rule of thumb, if using the Radius NAC option on a WLAN, you should not configure the Radius Server Overwrite interface feature.
    Bug Info:  https://tools.cisco.com/bugsearch/bug/CSCuj42870
    For your second question, you raise a very valid point which I am going to turn into a documentation enhancement request.  We don't currently have a document that lists the possible supplicant provisioning wizard errors that may be encountered.  Please feel free to post specific errors that you have questions about in this chat and we will try to get you answers.  For most Android devices, the wizard log file can be found at /sdcards/downloads/spw.log.
    As for product roadmap questions, we won't be able to discuss this here due to NDA.  Both are popular asks from the field so it will be interesting to see what the product marketing team comes up with for the next iterration of ISE.
    Related Info:
    Wireless BYOD for FlexConnect Deployment Guide

  • Cisco Identity Services Engine (ISE) Version 1.2: What's New in Features and Troubleshooting Options

    With Ali Mohammed
    Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about what’s new in Cisco Identity Services Engine (ISE) Version 1.2 and to understand the new features and enhanced troubleshooting options with Cisco expert Ali Mohammed.
    Cisco ISE can be deployed as an appliance or virtual machine to enforce security policy on all devices that attempt to gain access to network infrastructure. ISE 1.2 provides feature enrichment in terms of mobile device management, BYOD enhancements, and so on. It also performs noise suppression in log collection so customers have greater ability to store and analyze logs for a longer period.
    Ali Mohammed is an escalation engineer with the Security Access and Mobility Product Group (SAMPG), providing support to all Cisco NAC and Cisco ISE installed base. Ali works on complicated recreations of customer issues and helps customers in resolving configuration, deployment, setup, and integration issues involving Cisco NAC and Cisco ISE products. Ali works on enhancing tools available in ISE/NAC that are required to help troubleshoot the product setup in customer environments. Ali has six and a half years of experience at Cisco and is CCIE certified in security (number 24130).
    Remember to use the rating system to let Ali know if you have received an adequate response.
    Because of the volume expected during this event, Ali might not be able to answer each question. Remember that you can continue the conversation on the Security community, sub-community shortly after the event. This event lasts through September 6, 2013. Visit this forum often to view responses to your questions and the questions of other community members.

    Hi Ali,
    We currently have a two-node deployment running 1.1.3.124, as depicted in diagram:
    http://www.cisco.com/en/US/docs/security/ise/1.2/upgrade_guide/b_ise_upgrade_guide_chapter_010.html#ID89
    Question 1:
    After step 1 is done, node B becomes the new primary node.
    What's the license impact at that stage, when the license is mainly tied to node A, the previous primary PAN?
    Step 3 says to obtain a new license that's tied to both node A & node B, as if it's implying an issue would arise, if we leave node B as the primary PAN, instead of reverting back to node A.
    =========
    Question 2:
    When step 1 is completed, node B runs 1.2, while node A runs 1.1.3.124.
    Do both nodes still function as PSN nodes, and can service end users at that point? (before we proceed to step 2)
    Both nodes are behind our ACE load balancer, and I'm trying to confirm the behavior during the upgrade, to determine when to take each node out of the load balancing serverfarm, to keep the service up and avoid an outage.
    ===========
    Question 3:
    According to the upgrade guide, we're supposed to perform a config backup from PAN & MnT nodes.
    Is the config backup used only when we need to rollback from 1.2 to 1.1.3, or can it be used to restore config on 1.2?
    It also says to record customizations & alert settings because after  the upgrade to 1.2, these settings would change, and we would need to  re-configure them.
    Is this correct? That's a lot of screen shots we'll need to take; is there any way to avoid this?
    It says: "
    Disable services such as Guest, Profiler, Device Onboarding, and so on before upgrade and enable them after upgrade. Otherwise, you must add the guest users who are lost, and devices must be profiled and onboarded again."
    Exactly how do you disable services? Disable all the authorization policies?
    http://www.cisco.com/en/US/docs/security/ise/1.2/upgrade_guide/b_ise_upgrade_guide_chapter_01.html#reference_4EFE5E15B9854A648C9EF18D492B9105
    ==================
    Question 4:
    The 1.1 user guide says the maximum number of nodes in a node group was 4.
    The 1.2 guide now says the maximum is 10.
    Is there a hard limit on how many nodes can be in a node group?
    We currently don't use node group, due to the lack of multicast support on the ACE-20.
    Is it a big deal not to have one?
    http://www.cisco.com/en/US/customer/docs/security/ise/1.2/user_guide/ise_dis_deploy.html#wp1230118
    thanks,
    Kevin

  • Error during presentation services restart

    I get the following error during presentation services restart, Are there any compatibility issues with-in our product ?  Here is our set-up : OBIEE 11.1.1.6.7 Linux 6.3 DB - Oracle 11g R2
    sawlog0.log:[2013-08-12T15:27:56.000-06:00] [OBIPS] [ERROR:1] [] [saw.webextensionbase.init] [ecid: ] [tid: ] ODBC driver preload failed. ODBC library name: 'libnqsodbc64.so'[[
    sawlog0.log:[2013-08-12T15:27:56.000-06:00] [OBIPS] [ERROR:1] [] [saw.webextensionbase.init] [ecid: ] [tid: ] libnqshttpclientwrapper64.so: ELF load command past end of file[[
    sawlog0.log:[2013-08-12T15:28:02.000-06:00] [OBIPS] [ERROR:1] [] [saw.webextensionbase.init] [ecid: ] [tid: ] ODBC driver preload failed. ODBC library name: 'libnqsodbc64.so'[[
    sawlog0.log:[2013-08-12T15:28:02.000-06:00] [OBIPS] [ERROR:1] [] [saw.webextensionbase.init] [ecid: ] [tid: ] /u01/app/oracle/product/11.1.1.6/mwhome1/Oracle_BI1/bifoundation/server/bin/libnqutilityclient64.so: undefined symbol: _ZN13DynamicLoader11makeLibNameERKN7_SASSTL4ropeIwNS0_9allocatorIwEEEEbS6_[[
    Thanks for your help

    you need to add these below variables
    ORACLE_HOME=/opt/oracle/shared/product/11.2.0
    export ORACLE_HOME
    TNS_ADMIN=/var/opt/oracle
    export TNS_ADMIN
    PATH=$ORACLE_HOME/bin:$PATH
    export PATH
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
    export LD_LIBRARY_PATH
    not the same as above as your DB client may have a different path
    and then restart the services

  • EPM services restart schedule

    Hi
    We have a new implementation of Hyperion Planning and I was wondering if there's any recommendations on how often a services restart ought to be performed as part of general system health?
    Cheers

    Hi,
    Please use the below order to start and stop the services, if you are not using epma means, ignore the EPMA servers
    The first six services should be started in below order
    1) Databases for Repositories
    2) Corporate User Directories
    3) Foundation Services Managed Server Application Server
    4) Hyperion Reporting and Analysis Framework - Agent Service
    5) Reporting and Analysis Framework Application Server
    6) Web Server
    The remaining services and processes can be started in any order:
    7) Performance Management Architect Server Services
    8) Performance Management Architect Application Server
    9)Performance Management Architect Data Synchronizer Application Server
    10) Essbase Server
    11) Administration Services Server
    12) Integration Services Server
    13) Essbase Studio Server
    14) Provider Services Application Server
    15) Financial Reporting Services
    16) Financial Reporting Application Server
    17) Web Analysis Application Server
    18) Calculation Manager Application Server
    19) Planning Application Server
    Predefined scripts by Oracle Itself
    Start.bat/sh - To start all services
    Folder Location : EPM_ORACLE_INSTANCE/bin
    Note: Some of the services are clubbed into one services, for details level, pls refer epm_install_11121.pdf - Pages from 284
    Thanks

  • Timer Services restart every minute

    Hi,
    I have a SharePoint 2010 Standard Server with SP1. I find that the Timer Services start and stop every minute. The below log appears every time the timer service restart. Would anyone help to solve this? Thanks.
    The timer service is starting
    06/18/2014 16:07:34.23 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Topology 2myf Medium Disabling the configuration filesystem and memory caches.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Waiting for mutex to initialize type dictionary
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Obtained mutex
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering assemlies and sequences
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Using assembly manifest Microsoft.SharePoint.UpgradeAssemblyManifest.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 0, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 1, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 0, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 1, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence2] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 1, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceSequence] for [Microsoft.SharePoint.Administration.SPService], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceInstanceSequence] for [Microsoft.SharePoint.Administration.SPServiceInstance], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence] for [Microsoft.SharePoint.SPSite], Phase: 0, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence2] for [Microsoft.SharePoint.SPSite], Phase: 1, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSubscriptionSettingsServiceApplicationSequence] for [Microsoft.SharePoint.SPSubscriptionSettingsServiceApplication], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSubscriptionSettingsDatabaseSequence] for [Microsoft.SharePoint.SPSubscriptionSettingsDatabase], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPUsageApplicationSequence] for [Microsoft.SharePoint.Administration.SPUsageApplication], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPUsageDatabaseSequence] for [Microsoft.SharePoint.Administration.SPUsageDatabase], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServerSequence] for [Microsoft.SharePoint.Administration.SPWebServiceInstance], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServiceSequence] for [Microsoft.SharePoint.Administration.SPWebService], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebTemplateSequence] for [Microsoft.SharePoint.SPWebTemplate], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWssWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWssWebApplicationSequence2] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 1, Order: 0.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Reading xml configuration files from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade
    06/18/2014 16:07:34.26 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\dlcupgradeb2b.xml.
    06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\ExcelMobileViewerUpgradeConfig.xml.
    06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\ExcelServicesUpgradeConfig.xml.
    06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\GbwUpgrade.xml.
    06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\GbwUpgradeB2B.xml.
    06/18/2014 16:07:34.30 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\IpfsUpgrade.xml.
    06/18/2014 16:07:34.30 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\MpsUpgrade.xml.
    06/18/2014 16:07:34.30 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\MpsUpgradeB2B.xml.
    06/18/2014 16:07:34.31 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\OsrvUpgrade.xml.
    06/18/2014 16:07:34.33 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\OsrvUserProfilesUpgrade.xml.
    06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\OSSSearchUpgrade.xml.
    06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\PPSUpgrade.xml.
    06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SecureStoreServiceUpgradeConfiguration.xml.
    06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SiteUpgraderConfigSPS.xml.
    06/18/2014 16:07:34.45 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SPSUpgrade.xml.
    06/18/2014 16:07:34.47 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SPSUpgradeB2B.xml.
    06/18/2014 16:07:34.47 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\Wdsrv_Upgrade.xml.
    06/18/2014 16:07:34.47 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WebAnalyticsUpgradeConfiguration.xml.
    06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WSSSearchUpgrade.xml.
    06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WssUpgrade.xml.
    06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WssUpgradeB2B.xml.
    06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Policy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
    06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 7.
    06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 7.
    06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 7.
    06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcIisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 7.
    06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Policy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Excel.WebUI.Mobile, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
    06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Excel.WebUI.Mobile.Upgrade.ExcelMobileViewerSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 11.
    06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Excel.WebUI.Mobile, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Excel.Server.MossHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
    06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Excel.Server.MossHost.Upgrade.ExcelServicesSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 11.
    06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Excel.Server.MossHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
    06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 15.
    06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.FarmUpgradeSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 15.
    06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.ServiceUpgradeSequence] for [Microsoft.Office.InfoPath.Server.Administration.FormsService], Phase: 2147483647, Order: 15.
    06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.SiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 15.
    06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.FarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 0, Order: 3.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.OsrvPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 3.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 3.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.SessionStateServiceSequence] for [Microsoft.Office.Server.Administration.SessionStateService], Phase: 2147483647, Order: 3.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.StateDatabaseSequence] for [Microsoft.Office.Server.Administration.StateDatabase], Phase: 2147483647, Order: 3.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.SessionStateSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 3.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.StateServiceSequence] for [Microsoft.Office.Server.Administration.StateService], Phase: 2147483647, Order: 3.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
    06/18/2014 16:07:35.05 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 0, Order: 17.
    06/18/2014 16:07:35.05 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.ProfileDatabaseSequence] for [Microsoft.Office.Server.Administration.ProfileDatabase], Phase: 2147483647, Order: 17.
    06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 17.
    06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.SocialDatabaseSequence] for [Microsoft.Office.Server.Administration.SocialDatabase], Phase: 2147483647, Order: 17.
    06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileApplicationSequence] for [Microsoft.Office.Server.Administration.UserProfileApplication], Phase: 2147483647, Order: 17.
    06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 17.
    06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.ServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 10.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchServiceSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 10.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchServiceSequence2] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 10.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 10.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 10.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchServiceApplicationSequence] for [Microsoft.Office.Server.Search.Administration.SearchServiceApplication], Phase: 2147483647, Order: 10.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence] for [Microsoft.Office.Server.Search.Administration.SearchAdminDatabase], Phase: 0, Order: 10.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchMetadataDatabaseSequence] for [Microsoft.Office.Server.Search.Administration.SearchPropertyStoreDatabase], Phase: 2147483647, Order: 10.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchGathererDatabaseSequence] for [Microsoft.Office.Server.Search.Administration.SearchGathererDatabase], Phase: 2147483647, Order: 10.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.PerformancePoint.Scorecards.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
    06/18/2014 16:07:35.66 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.PPSDatabaseSequence] for [Microsoft.PerformancePoint.Scorecards.BIMonitoringServiceDatabase], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.66 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.PPSFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Upgrade.BIMonitoringServiceApplicationSequence] for [Microsoft.PerformancePoint.Scorecards.BIMonitoringServiceApplication], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.PPSSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.PerformancePoint.Scorecards.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.SecureStoreService, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
    06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.SecureStoreService.Server.Upgrade.SecureStoreDatabaseSequence] for [Microsoft.Office.SecureStoreService.Server.SecureStoreServiceDatabase], Phase: 2147483647, Order: 17.
    06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.SecureStoreService.Server.Upgrade.SecureStoreServiceApplicationSequence] for [Microsoft.Office.SecureStoreService.Server.SecureStoreServiceApplication], Phase: 2147483647, Order: 17.
    06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.SecureStoreService, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.SharePoint.Portal.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
    06/18/2014 16:07:35.73 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.ApplicationRegistry.Upgrade.BdcO14SharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.73 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.FarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.73 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Taxonomy.Upgrade.MetadataDatabaseSequence] for [Microsoft.SharePoint.Taxonomy.MetadataWebServiceDatabase], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Taxonomy.Upgrade.MetadataApplicationSequence] for [Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplication], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.PrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.MossSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.WebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 5.
    06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.SharePoint.Portal.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.Word.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
    06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Word.Server.Service.Upgrade.QueueDatabaseSequence] for [Microsoft.Office.Word.Server.Service.QueueDatabase], Phase: 2147483647, Order: 11.
    06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Word.Server.Service.Upgrade.ServiceAppSequence] for [Microsoft.Office.Word.Server.Service.WordServiceApplication], Phase: 2147483647, Order: 11.
    06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Word.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.Server.WebAnalytics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.StagerDatabaseSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsStagerDatabase], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WarehouseDatabaseSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsWarehouseDatabase], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsWebServiceSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsWebService], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsServiceApplicationSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsServiceApplication], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Upgrade.WebAnalyticsSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Upgrade.WebAnalyticsWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Server.WebAnalytics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.SharePoint.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Search.Upgrade.SPSearchDatabaseSequence] for [Microsoft.SharePoint.Search.Administration.SPSearchDatabase], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Search.Upgrade.SPServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Search.Upgrade.SPSearchServiceSequence2] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 4.
    06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.SharePoint.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    06/18/2014 16:07:35.83 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Ready to initialize the type dictionary
    06/18/2014 16:07:35.83 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Type dictionary initialized.
    06/18/2014 16:07:35.83 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Mutex released.
    06/18/2014 16:07:35.84 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypassInternal = 0
    06/18/2014 16:07:35.84 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypass = 0
    06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence2] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypassInternal = 0
    06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence2] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypass = 0
    06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPUpgradeSession] [DEBUG] [6/18/2014 4:07:35 PM]: CanUpgrade [SPConfigurationDatabase] returned: True.
    06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPUpgradeSession] [DEBUG] [6/18/2014 4:07:35 PM]: NeedsUpgrade [SPConfigurationDatabase] returned: True.
    06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPUpgradeSession] [DEBUG] [6/18/2014 4:07:35 PM]: IsBackwardsCompatible [SPConfigurationDatabase] returned: True.

    I have the following finding from the Event Viewer.
    Event 7022
    The Forefront Identity Manager Synchronization Service service hung on starting.
    Event 7024
    The Forefront Identity Manager Synchronization Service service terminated with service-specific error %%-2146234334.
    Event 7031
    The SharePoint 2010 Timer service terminated unexpectedly.  It has done this 4007 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service.
    Event 11016
    The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {000C101C-0000-0000-C000-000000000046}
     and APPID 
    {000C101C-0000-0000-C000-000000000046}
     to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
    I found this
    post talking about the solution of this problem. Can anyone help to explain the solution to me?
    Also, I try to stop the user profile service and user profile sync service and restart both. The timer service restart problem has gone!! However, new error in the event viewer.
    Event ID 3
    Microsoft.ResourceManagement: System.InvalidOperationException: This Forefront Identity Manager system resource cannot be deleted.
       at Microsoft.ResourceManagement.Utilities.ExceptionManager.ThrowException(Exception exception)
       at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Delete(Message request)

  • Error message when run the Cisco CRS Serviceability Utility on UCCX 4.5 server

    Hi,
       Everytime i run the Cisco CRS Serviceability Utility from the UCCX server, this message always appear "Error reading System Parameters" before the interface appear.
       After that, when i click the "System Parameters" tab and there were no any information displayed.
      So, i would like to know if there were any way could fix this problem.
      Thanks for any suggestion.
    B.rgds,
    Tong

    Tong,
    The description that you are ginving us sounds preaty much like this bug : CSCsi25913
    This is the link with the informatio:
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?caller=pluginredirector&method=fetchBugDetails&bugId=CSCsi25913
    HTH
    Please rate this post if was helpful
    Walter Solano
    CCNA Voice
    Cisco UCCX Specialist

  • NAC-L2-802.1x (EAP-FAST) and Cisco Secure Services Client 5.0 in wired net

    Hi!
    (Sorry, if this is a wrong forum.)
    Does anybody have any success with Cisco SSC and EAP-FAST in the wired network?
    I'm going to use NAC, so I'm trying to set up EAP-FAST. I see the pop-up window on the client to enter user credentials and I see a lot of "debug radius" messages on my 3750 12.2(44)SE switch:
    Access-Requests with User-Name="anonymous"
    Access-Challenges (I see certificate is sent from ACS)
    Access-Reject
    CS ACS Failed Attempts Report shows "ACS user unknown" failure for "anonymous".
    So far as I understood, EAP-FAST is a tunneled method and it uses "anonymous" to protect user's identity during phase 0 / phase 1 transactions. The actual username is sent in phase 2 transaction.
    The following is excerpt from the CS ACS documentation:
    "EAP-FAST can protect the username in all EAP-FAST transactions. ACS does not perform user authentication based on a username that is presented in phase one; however, whether the username is protected during phase one depends on the end-user client. If the end-user client does not send the real username in phase one, the username is protected. The Cisco Aironet EAP-FAST client protects the username in phase one by sending FAST_MAC address in place of the username. After phase one of EAP-FAST, all data is encrypted, including username information that is usually sent in clear text."
    SSC 5.0 is indeed set up with "Unprotected Identity Pattern"=anonymous and "Protected Identity Pattern"=[username] using sscManagementUtility.exe
    So, the question is: Why is ACS 4.1 trying to authenticate username "anonymous" if it knows that the user is fake? Does anybody have working configuaration for EAP-FAST in a wired network?
    Any help is greatly appreciated.

    Correct, ACS database wasn't selected on the NAP Authentication page. It works now, but I constantly get the following message in the Windows event log: "The Cisco Secure Services Client service hung on starting". This is Windows 2000 Advanced Server system with SP4. SSC was set up with no domain authentication, no machine authentication, single sign-on. After some time the SSC service starts, but at that time my PC is already put into the guest VLAN by the switch (the tx-period is 10 seconds):
    POD1-SW#sh run int fa1/0/1
    Building configuration...
    Current configuration : 378 bytes
    interface FastEthernet1/0/1
    switchport access vlan 999
    switchport mode access
    dot1x mac-auth-bypass
    dot1x pae authenticator
    dot1x port-control auto
    dot1x timeout reauth-period server
    dot1x timeout tx-period 10
    dot1x reauthentication
    dot1x critical
    dot1x critical recovery action reinitialize
    dot1x guest-vlan 91
    dot1x critical vlan 11
    spanning-tree portfast
    end
    After all the VLAN is reassigned by the switch, but the delay is too high. How can I troubleshoot this?
    Thx.

  • Help, error connection Cisco Identity Services Engine with AD, global catalog port status error

    Dear all,
    I have Cisco Indentity Services Engine, that  connected to Active Directory. When I test connection detailed,
    the result is error, said:
    Test Connection Results
    This dialog shows the detailed logs for the operation for: idsv0018.
    Status: FAILED: Global Catalog port status error.
    Can anyone help?
    I believe,  because this error, I can't search group of AD, at Cisco ISE.
    FYI: the connection from Cisco ISE to AD, joined with successful result.
    Thanks,
    Jerri

    It's clears that when ISE tries to  find the GC using the _gc._tcp. DNS query. It doesn't find that  information on the Domain controller. The GC information is missing on  the DC.
    gc._tcp.DnsForestName
    Allows a client to locate a Global Catalog (gc) server for this domain.
    Jatin Katyal
    - Do rate helpful posts -

  • Cisco Identity Service Engine (ISE) (CSCup22534)--bug information

    I can see this bug information, can you please help?
    Cisco Identity Service Engine (ISE) (CSCup22534)

    Backup Data Type
    Cisco ISE allows you to back up data from the primary or standalone Administration node and from the Monitoring node. Backup can be done from the CLI or user interface.
    Cisco ISE allows you to back up the following type of data:
    Configuration data—Contains both application-specific and Cisco ADE operating system configuration data.
    Operational Data—Contains monitoring and troubleshooting data.
    Restore operation, can be performed with the backup files of previous versions of Cisco ISE and restored on a later version. For example, if you have a backup from an ISE node from Cisco ISE, Release 1.2, you can restore it on Cisco ISE, Release 1.3.
    http://www.cisco.com/c/en/us/td/docs/security/ise/1-3/admin_guide/b_ise_admin_guide_13/b_ise_admin_guide_sample_chapter_01100.html#reference_4F69987D3294499E95C1B652C4D1E73D

  •  Cisco Identity Services Engine VM (eDelivery) - Part # L-ISE-VM-K9=

    Hello,
    I would like to know, if the following will run on Microsoft Hyper V. (Windows 2008 R2)
    Cisco Identity Services Engine VM (eDelivery) - Part # L-ISE-VM-K9=
    Thank you and best regards

    Hello,
    I would like to know, if the following will run on Microsoft Hyper V. (Windows 2008 R2)
    Cisco Identity Services Engine VM (eDelivery) - Part # L-ISE-VM-K9=
    Thank you and best regards

Maybe you are looking for

  • Migrating data from 10.3.9 to Leopard

    I want to buy a new imac with Leopard but want to be sure that I can migrate data (iTunes, folders, software, etc) over from the old imac 1Ghz PowerPC G4 to the new. I've read that this is no problem from Tiger to Leopard using Migration Assistant bu

  • Export mide files

    I have a session whith Au instruments. I want export midi file. When I import again exported midi file logic place each regions which stand in one track to many tracks. I have many many tracks thith one region on them. I shood to glue all regions on

  • Three issues with slideshows...

    Issue 1: I can select 1 song to play as the music for a slideshow or 1 playlist, but I cannot select (like shift-click in normal applications) multiple songs or playlists. Why is this??? Issue 2: I would like to chain together multiple slide shows in

  • Problem with remembering FTP details

    For some reason dreamweaver does not remember my ftp username or password on any of my sites. I click on the "remember" tick on the options menu, but whenever i close, then re-open dreamweaver i have to go in and manually type in the username and pas

  • Import error: File is not a valid HTML DB export file

    Hi, This is driving me a bit nuts: I have made a change to a page and want to move it to another HTMLDB environment. I have 3 environments, DEV, TEST and PROD, they are all version 1.6.0.00.87. I export the page from DEV, then when I try and import i