10.1.0.4.1 patch breaks agent upload

Has anyone had a issue when they upgraded there linux agent nodes from 10.1.0.3 to 10.1.0.4.1 that the uploads to management server stop. I have reinstalled the agent three times and every time I upgrade to the 10.1.0.4.1 patch the uploads stop. I can do a force upload successfully, it just stops happening automatically.

I dont have a problem ..
dbp29ykf: TPMS> . ./oem.sh
dbp29ykf: TPMS> emctl status agent
TZ set to US/Eastern
Oracle Enterprise Manager 10g Release 10.1.0.4.1
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Agent Version : 10.1.0.4.1
OMS Version : 10.1.0.3.0
Protocol Version : 10.1.0.2.0
Agent Home : /opt/app/oracle/product/oem_agent
Agent binaries : /opt/app/oracle/product/oem_agent
Agent Process ID : 25834
Parent Process ID : 25831
Agent URL : http://dbp29ykf:1830/emd/main/
Started at : 2005-07-15 09:40:39
Started by user : oracle
Last Reload : 2005-07-15 09:40:54
Last successful upload : 2005-07-28 09:05:50
Total Megabytes of XML files uploaded so far : 812.63
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 76.74%
Agent is Running and Ready
dbp29ykf: TPMS> uname -a
Linux dbp29ykf 2.4.21-20.ELsmp #1 SMP Wed Aug 18 20:46:40 EDT 2004 i686 i686 i386 GNU/Linux
dbp29ykf: TPMS>
dbp29ykf: TPMS>
dbp29ykf: TPMS> more oem.sh
umask 022
export JDKHome=/opt/app/oracle/product/9.2.0/jdk
ORACLE_HOME=/opt/app/oracle/product/oem_agent
export ORACLE_HOME
PATH=$ORACLE_HOME/bin:$JDKHome/bin:/usr/ccs/bin:$PATH
export PATH

Similar Messages

  • Cloud Control can't patch an agent

    This week I have successfully upgraded our Cloud Control 12.1.0.2 to 12.1.0.3. Since this was my first experience with Cloud Control configuration, it went pretty good. I have noticed now in Patch recommendations that it's possible to patch an agent which is working on Windows Server 2008.
    This is the available patch:
    Patch 14335896: BUG FOR PATCH OF PERFORMANCE BUNDLE 2 ON EM 12C BP1 (AGENT)
    So i have downloaded it, uploaded in "Saved patches", created a plan, configured it, and during the plan analysing i get a status Failed. First few checks go without problems, but then I get this:
    ========================================================
    Performing check for CheckPatchShipHome
    Is the Patch Shiphome correct?
    Result: [E:\ded_agent\p14335896_9800371121011_2000_0\Administrator\com\trend\etc\config path does not exist or is not a directory]
    I have checked the path on target, it exists until E:\ded_agent\p14335896_9800371121011_2000_0\Administrator\com\trend\
    There I can find only a folder with iwss name. Etc is not there...
    Any known issues about this Problem?

    I think you forgot one step: you must first download the latest agent software for Windows, see Prerequisites in Upgrading Oracle Management Agents
    The new management agent software (for Windows in this case) must be available in the software library before you can upgrade an agent.
    Eric

  • Target down, Agent Upload/OMS refresh rate

    Using 10.1.0.4.0 Grid Control,. OMS and all agents running on MS platforms.
    Currently testing agents, and in particular metrics and alert rates...
    The example I need to ask about is this...
    We have an agent running on a server, on which several targets exist. We shutdown an Oracle Listener on the server, and after a few mins (this duration varies) we receive an 'Target Down' alert in OMS, and the associated email....
    So far, so good...
    However, how can the 'alert rate' be changed so that an alert is created immediately following the shutdown of the listener? Also, the alert remains several mins after the listener has been restarted...
    The way EM currently works with alerts isn't very useful if users say the application is unavailable, but to DBAs using EM - (for several mins) everything looks okay!
    Any help, appreciated :-)

    Check uploadinterval in emd.properties:
    Here is a description of this parameter
    uploadInterval - Number of minutes to wait before the Agent uploads the XML files to the OMS. Default value is 30 (minutes).
    You can change this to something lower but be careful about flooding the network if you've decreased it. May be something like 15 minutes will work for you.

  • What does Grid Control agent upload?

    We recently shut down the agent for Grid Control and yet I still see data on the "top activity" page, both current and historical. If the agent isn't uploading this data what is? And what does the agent upload if not this data?

    If my memory serves me correctly, the agent uploads monitoring metrics for long term. When you are viewing the target it connects directly to the database, hence why grid has to have connect descriptors for the databases beyond just the agent using them.

  • 118872-03 ksh patch breaks set construct wildcard

    Not sure where to report solaris 10 bug, anyone know? So I will post it here.... Solaris 10 sparc patch 118872-03 breaks set construct wildcard. For example:
    % ls [A-Z]*
    will return filename of both upper and lowercase..
    back out 118872-03 fix the problem. 118872-02 works..
    -- Frogdeep

    OK... not so sure the problem is with 118872-03 now. I look carefully even with the 118872-02 patch I still have the problem. So it is some other patch that is causing the problem. Let's say my system is fully patched.
    On system we only have recommendated cluster patched:
    % touch A aa B C D ee
    % ls [a-z]
    [a-z]: No such file or directory
    On fully patched box:
    % touch A aa B C D ee
    % ls [a-z]
    A B C D
    Doh! Help! Something is not right :*(
    -- Frogdeep

  • Patching HA Agents of an Application

    Gurus,
    So far we've been delivering a HA Agent package for our application. There was no need for us to modify the RTR file (ORCL.scocs) that comes with the package, until now. Recently we revamped the way we implemented our agents, this resulted in us modifying our RTR file ORCL.scocs
    So far we've been fixing bugs and delivering patches for our HA Agents. The customer used to apply this patch, and every things perfectly fine. But with the changed RTR file, in our next release; how do we deal with this ?.
    Question 1) Does the customer has to reregister this RTR file ?.
    Questions 2 ) If there are any changes to the RTR file, do we need to modify any field in the RTR file ? say version ?? etc...
    Question 3 ) Are there any alternatives for the Customer, to not unregister and re-register the current RTR file ?
    How do most customers implement in such a scenario ?
    _Thanks in Advance
    D

    Hi Durga,
    Check out the procedure for "How to Migrate Existing Resources to a New Version of the Resource Type" at http://docs.sun.com/app/docs/doc/819-2974/6n57pdjtl?a=view
    That is the procedure the customers of the RT would use to migrate to the new version of
    RT. Note that whether that can be done without a downtime depends upon exactly how
    the developer (that is you!) provides for compatibility (more on that below). Typically, you would want the resources to be in "Unmonitored" state (that is, the fault monitor is not
    running) before upgrade. A downtime is typically not required, unless the upgrade is somehow not backward compatible.
    So much for how to USE rt upgrade. For developers, check out the procedure for
    "Modifying a Resource Type" at http://docs.sun.com/app/docs/doc/819-0581/6n30f91s3?a=view
    Here are the key things to keep in mind.
    1) Make sure your new code (the method implementations for the new version) can work with resources of old types. One way i have seen that to go wrong is if the new version of the RT introduces a new property and the new method implmentation FAILs if it does not find that new property. The right way to deal with that is to look for error code SCHA_ERR_PROP from scha_resource_get() calls and if you get that error, take the course of action which your implementation did in earlier implementation instead of erroring out.
    2) Make sure there is a #$upgrade_from directive in your new RTR file. You would want it to be WHEN_UNMONITORED. Read the documentation for details.
    Take a close read of the documentation, you would find that it is pretty thourough. But
    ABOVE ALL, "Please do test!!". :-)
    Post here if you have any specific questions even after reading the documentation, or run into any specific issues. Or even if you succeed at first try and don't actually have any questions, just want to report your success.
    Best of Luck!
    -ashu

  • Patching ccms agent

    Hi,
    Could you please help on this issue.
    We are planning to patch the ccms agent . Latest version we have downloded from service market place. i.e ccmagent_33-20001044.sar
    Our platform is Sun Solaris 10 on SPARC 64bit. Kernel release 700. SAP ECC server. (NW 2004).
    Could you please provide the procedure how to apply the patch.
    Thanks & Regards.

    Hi,
    Please find the documentation relatd to the installation of the  CCMS agents at the following location:                                                                               
    service.sap.com/monitoring    > Media Library    > Documentation.
    Br,
    Javier

  • Diagnostics - How to patch SMD Agent

    Dear SAP Colleague,
    I will have to install the SMD Agent on all managed system of my SAP landscape.
    Do you know how this agent is patched ?
    I know that both Wily IS Agent (Introscope Java Agent) and Host-level Introscope Agent) are updated from SAP Solution Manager and deployed to all managed systems.
    But how do we patch the SMD Agent (Java instance) ?
    Thanks
    Best regards
    P.C.

    Hello folks,
    Was wondering too if any way to update / patch SMD Host Agentu2019s executable.
    I could not find any SAP document on that.
    Checking our own AIX kernel  that  came with the install e.g. u201Cjstart u2013Vu201D, I saw that the patch # was 37, in the context of kernel 7.11_REL UNICODE, compile time Jun 6 2009.  It to be noticed that in the exe directory there are just some of the u201Cfullu201D kernel folders present (it makes sense, because it is just a Java env.).. In my case there are 79 u201Cfoldersu201D in the exe dir. Please note that one of it, u201Cservicehttpu201D is a directory.
    Thus, my thoughts on a potential way to patch the SMD Host Agent SAP Kernel is to apply that pool of kernel components that matches the SMD Agentu2019s executables.
    Thus, first  download the kernel 7.11 latest patches e.g. from (Entry by Application Group -> Additional Components -> SAP Kernel -> SAP Kernel 64 BIT UNICODE -> SAP Kernel 7.11 64 BIT UNICODE , then uncar these  and rm a script that will copy only the folders  that are present in the installed exe SMD Host Agent exe dir as well. Also, is should be checked to that all the files in the SMD Agent should be part of the updated kernel. If not, then I will not recommend to do it, since SAP may have something special for the SMD SAP Kernel.
    Have not tried yet to perform this procedure, but is very tempting, since for 7.11 AIX the default install is at patch level 37 while today the corresponding 7.11 patch level is 92.
    Please, note that this is just a personal look at this issue and absolute not a SAP recommendation. Maybe the fist question should be u201Cwhatu2019s the need for the SAP SMD Agent u201CSAP Kernel Upgradeu201D?  The more correct and recommended way will be to open a customer message with SAP, e.g. asking to u201Cblessu201D the SMD Agent Kernel upgrade procedure described above.
    Kind regards,
    C.P.

  • ZCM 11.2.4 - 11.3.1FRU1 Patch Management Agent Update 1

    Tried the "updated" exe files, patch management now says all of our win7 machines with Office 2007 are missing SP3 (KB2526086) which is completely wrong.
    https://download.novell.com/Download...d=G072RdrX4b0~

    dtemple-sgi,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://www.novell.com/support and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Forums Team
    http://forums.novell.com

  • Poodle Patch breaks Webdav in Filr 1.1?

    Hi
    We upgraded Filr 1.1 (small install) with the poodle patch (filr-1.1.0.655).
    After the update, none of the clients can connect to Filr via Webdav. I get the error "Error message 0x80070043 - the network name cannot be found".
    Tried to install all patches available on the download Center, but no success.
    Access via Webinterface is fine, but we Need webdav.
    Enviroment:
    Filr 1.1 small Installation
    Webdav Authentication: Digest
    Client: Windows 7 64bit with all patches, IE10
    Webdav-Clint: native Client from Windows
    Tried "IISCrypto40" from https://social.technet.microsoft.com...w7itprogeneral with no success
    Can anybody give mi a hint?
    Thank you

    On Thu, 12 Feb 2015 18:06:02 GMT, chfritsche
    <[email protected]> wrote:
    Hi,
    Enable fips on the client
    >
    > Hi
    >
    > We upgraded Filr 1.1 (small install) with the poodle patch
    > (filr-1.1.0.655).
    > After the update, none of the clients can connect to Filr via Webdav. I
    > get the error "Error message 0x80070043 - the network name cannot be
    > found".
    > Tried to install all patches available on the download Center, but no
    > success.
    >
    > Access via Webinterface is fine, but we Need webdav.
    >
    > Enviroment:
    > Filr 1.1 small Installation
    > Webdav Authentication: Digest
    > Client: Windows 7 64bit with all patches, IE10
    > Webdav-Clint: native Client from Windows
    >
    > Tried "IISCrypto40" from
    > https://social.technet.microsoft.com...w7itprogeneral
    > with no success
    >
    > Can anybody give mi a hint?
    >
    > Thank you

  • Autogroup patch 'breaks' "nice" command.

    Hi all,
    I just had a look how the nice command works together with the autogroup patch. (See i.e. this discussion: https://bbs.archlinux.org/viewtopic.php?id=108516, or the links at the end of the post).
    While the default behaviour is consistent, it is rather annoying:
    Nice works only inside a group, while my processes (i.e. compilation + some foreground task) run typically in different groups.
    I hope someone can explain to me, what I am doing wrong. Processes are grouped by Session ID, and I get the following behaviour:
    For me process priorities work now as follows:
    - run several commands with different niceness levels from the same terminal: CPU time is divided according to niceness.
    - run several commands with different niceness levels from different terminals:  Every command gets the same amount of CPU.
    - run several commands with different niceness levels in the same terminal, and run more processes with different niceness levels in different terminals: CPU time is first divided between the terminals evenly, and then subdivided according to niceness.
    Running several commands from the GUI works the same as running from different terminals, i.e. the SID is different, and niceness is therefore ignored.
    I start X and login using inittab and lxdm.
    An easy 'fix' for this is disabling autogroup support:
    echo 0 > /proc/sys/kernel/sched_autogroup_enabled
    Links on autogroup patch/cgroups:
    https://wiki.archlinux.org/index.php/Cgroups
    http://lwn.net/Articles/418884/

    I can no longer duplicate the problem. The patch 125285-04 has been applied. Here are the cases. For one V210 host, the command "updatemanager" was aborting in real time on Friday. I had not removed the patch 125285-04 from it. Today, I tried it Tuesday and it worked. I cannot explain why unless the reboot on Monday cleared up something.
    For the host where I had unapplied patch 125285-04, I re-applied it and manually ran the command "/usr/bin/fc-cache -f". Now running the "updatemanager" works. I cannot duplicate this problem today.
    I only use updatemanager on these hosts for patching. I have not tried other commands that used GUI fonts/JAVA/etc.

  • Upgrade of agent from IR3 or earlier to IR4 or IR4hp1 breaks agent

    Well this is new.. I've tried it on several machines now with the exact
    same results.
    Previously when a new agent was released, I would make a new response
    transform for it with zenworks package management and just deploy it.
    No problems at all.
    What happens in this case is that when it reboots, the agent will be
    stuck in an offline state. You can't right click on it and pull up a
    menu either.
    Remove the agent via add/remove programs and reinstall the new agent and
    it works fine. Not a great option to upgrade multiple sites.
    Anyone else seen this?

    Perhaps open an SR?
    I'm not aware of this being a known issue and certainly nothing I have
    tested my personally.
    So most likely issues I have had to deal with in the past may be different
    than now.
    I would suggest Checking the "%program files%\novell\zenworks folder on a
    "Bad" vs a "Good" machine to see if there is a byte size difference.
    Perchance there is a wrong DLL version that is causing a file to not get
    updated, perhaps MSIEXEC is not properly handing "in use" files.
    I've had an issue where I could see in the logs where MSIEXEC flagged a file
    in use but only ended up removing the locked file on reboot w/o putting in
    the proper file.
    And details about What is broken in the agent may help?
    WM Service? NALNT Service? NAL Window? etc.. etc...
    Craig Wilson - MCNE, MCSE, CCNA
    Novell Knowledge Partner
    Novell does not officially monitor these forums.
    Suggestions/Opinions/Statements made by me are solely my own.
    These thoughts may not be shared by either Novell or any rational human.
    "Patrick Farrell" <[email protected]> wrote in message
    news:[email protected]. ..
    > Patrick Farrell wrote:
    >> Craig Wilson wrote:
    >>> Well Definitely NALWIN/NALDESK/NALEXPLD or whatever is running.
    >>> That seems to be a key one. But it would not hurt to shut down the
    >>> services such as WM and NALNTSRV
    >>>
    >>> This is based more on historical observations than this specific
    >>> upgrade, so this may not help in the least if this is a new issue.
    >>>
    >> Well I guess that means I can't deploy it using zenworks calling the MSI
    >> specifically... That kinda stinks :P
    >>
    >> I guess the question is, which services can you kill once an application
    >> starts to deploy and still have it go? If I have an MSI based object
    >> pointed at the agent and it's mst, what still has to run for it to be
    >> able to deploy?
    >>
    >
    > FYI update, so far NOTHING seems to fix this other than
    > uninstall/reinstall.
    >
    > net stop "Remote Management Agent"
    > net stop "Novell ZENworks Remote Management Agent"
    > net stop "Novell ZFD Remote Management"
    > net stop "Workstation Manager"
    > net stop "Novell Application Launcher"
    > pskill.exe -t zenrem32.exe
    > pskill.exe -t nalntsrv.exe
    > pskill.exe -t NalView.exe
    > pskill.exe -t NALWIN32.EXE
    > pskill.exe -t NalWin.exe
    > pskill.exe -t NalDiag.exe
    > pskill.exe -t NALDESK.EXE
    > pskill.exe -t NalAgent.exe
    >
    > Along with Reinstall all and vamus settings had no effect.
    >
    > I can do an msiexec /x in the script to remove zen and fix, but only if
    > the version on the workstation is the same as what I'm trying to install,
    > and it could be one of several agent versions. Joy.
    > ]

  • New patches break Swing?

    I had previously posted this message in a thread in the 'Administration' forum, but it looks like it's more Java-specific, so they forum admin suggested I try asking over here.
    I have a Sun Ultra 20 with the latest Solaris 10 (6/06). A week or so ago, I downloaded and installed the latest Solaris patches using the Sun Update Connection utility. Everything went all right, and I thought things were OK, until I tried to install the latest version of NetBeans. The installed died with a ULE for getCreatedFontHandle:
    Exception in thread "main" java.lang.UnsatisfiedLinkError: getCreatedFontHandle
    at sun.font.FontManager.getCreatedFontHandle(Native Method)
    at sun.font.FontManager.setSameHandle(FontManager.java:429)
    at javax.swing.plaf.FontUIResource.<init>(FontUIResource.java:42)
    at javax.swing.plaf.metal.DefaultMetalTheme$FontDelegate.getFont(DefaultMetalTheme .java:230)
    at javax.swing.plaf.metal.DefaultMetalTheme.getFont(DefaultMetalTheme.java:184)
    at javax.swing.plaf.metal.DefaultMetalTheme.getMenuTextFont(DefaultMetalTheme.java :172)
    at javax.swing.plaf.metal.MetalLookAndFeel$FontActiveValue.createValue(MetalLookAn dFeel.java:1687)
    at javax.swing.UIDefaults.getFromHashtable(UIDefaults.java:200)
    at javax.swing.UIDefaults.get(UIDefaults.java:130)
    at javax.swing.MultiUIDefaults.get(MultiUIDefaults.java:44)
    at javax.swing.UIDefaults.getFont(UIDefaults.java:350)
    at javax.swing.UIManager.getFont(UIManager.java:567)
    at javax.swing.LookAndFeel.installColorsAndFont(LookAndFeel.java:89)
    at javax.swing.plaf.basic.BasicMenuBarUI.installDefaults(BasicMenuBarUI.java:70)
    at javax.swing.plaf.basic.BasicMenuBarUI.installUI(BasicMenuBarUI.java:56)
    at javax.swing.plaf.metal.MetalMenuBarUI.installUI(MetalMenuBarUI.java:48)
    at javax.swing.JComponent.setUI(JComponent.java:652)
    at javax.swing.JMenuBar.setUI(JMenuBar.java:113)
    at javax.swing.JMenuBar.updateUI(JMenuBar.java:122)
    at javax.swing.JMenuBar.<init>(JMenuBar.java:90)
    at com.sun.swup.client.ui.foundation.swing.GenericMenuBar.<init>(GenericMenu Bar.java:22)
    at com.sun.swup.client.ui.MenuBarBuilder.createMenuBar(MenuBarBuilder.java:40)
    at com.sun.swup.client.ui.UpdateFrame.<init>(UpdateFrame.java:52)
    at com.sun.swup.client.ui.Application.getUpdateFrame(Application.java:208)
    at com.sun.swup.client.ui.Application.<init>(Application.java:188)
    at com.sun.swup.client.ui.Application.main(Application.java:108)
    The docs claim the ULE is due to the JVM's failure to find a native-language definition of the method. My locale is set to "C" (LC_ALL='C'),
    Can anyone think of a reason why this would fail? Incidentally, the Sun Update Connection utlity also fails to launch now, presumably due to the same error. Would installing a new version of Java fix this? I'm currently on 1.5.0_04, which hasn't given me any problems before.

    Dear Dips,
    1) You will have to upgrade to SP level 38. as mentioned in the response above.
    2) You will have to apply the note 1361644 this includes both Source and non source code changes.
    3) you will have to change atleast 5 Cross client table configs.
    4) Apply the note and takle both the Transport requests to QA client for testing
    Alternatively since the budget has not been passd by the Govt of India (Parliament) SAp is cautious in saying that please ask business to check with thier legal counsel for the same, that also means that we can wait for applying the same. and the same can be done when SP 46 will be released (in Mid August) you can directly upgrade to SP 46 and all the changes should be incorporated.
    Try doing the same i am sure you will be able to successfully get the results in either case. In case of any problem do write back so we can help you with more details regarding the same.
    regards
    Ankush

  • Latest patches break Java Desktop on Dell 2800

    I have solaris 10 x86 installed on a Desll Poweredge 2800. I have just loaded all the latest patches via updatemanager. Now if I try to log into any account to the gnome Sun Java Desktop the machine logs in ... then hangs before any of the toolbars etc are loaded ... it hangs so badly I have to reboot via the powerswitch
    If I login using CDE it works perfectly. The Java Desktop did work until the latest batch of patches was installed. Does anyone have any Idea on how to fix this?

    <table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>hellhathnofury wrote on Fri, 30 September 2005 21:17</b></td></tr><tr><td class="quote">
    I am using an ATI Radeon ... built onto the Motherboard. Now to find where solaris hides the xorg.conf file ...
    </td></tr></table>
    In a default configuration, there is no xorg.conf file. When xorg.conf is
    missing, all the settings are auto-probed.
    You can use "/usr/X11R6/bin/Xorg -configure" or /usr/X11R6/bin/xorgconfig
    to create an initial xorg.conf file.
    Install the customized xorg.conf file as /etc/X11/xorg.conf

  • Did RH 9.02 patch break something...???

    Yesterday we upgraded to Version 9.0.2. Today my stylesheets don't work.
    I rely very heavily on stylesheets because my company has two divisions with two separate brandings. Every day I have to import the same document to two separate projects, and apply the appropriate stylesheet so it publishes in the right colors for that division.
    I tested multiple Word documents, multiple projects and multiple stylesheets. As soon as you apply ANY stylesheet, the topic loses all formatting. That means I have to manually apply the styles to every line of text.
    Is there a quick fix to this that will get me through today? I have topics I need to publish.
    Thanks

    Thanks for replying. I was just now reporting it as a bug.
    In Word, apply custom styles to a document.
    Create two stylesheets for Robohelp that replicate those Word styles, but have different colors for the heading styles. Place them in each applicable Robohelp project folder.
    Import the document.
    Right click the topic name in the Topic List, and click Appearance.
    Select the appropriate stylesheet and click OK.
    Usually it's Voila! and everything formats perfectly. Today there is NO style to ANY text - even the font reverts to no margins, Times New Roman 10pt. It keeps character formatting, so things I bolded in Word stayed bolded. But that's it. I have used the same stylesheets for months, and made no changes to it yesterday, when it was working.
    The loss of styles persists after you compile. However, they display correctly in the Styles and Formatting pod. When I highlight text in the window and apply the styles from the Styles pod, they update as they should, but the process is 100% manual.
    I have no topics that don't originate in Word.
    Here's one of the stylesheets:
    /*Created with Adobe RoboHelp 9.*/
    p.WD_Normal {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: .5in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    span.WD_Hyperlink {
    color: #0000ff;
    text-underline: single;
    text-decoration: underline;
    span.WD_HyperlinkFollowed {
    color: #800080;
    text-underline: single;
    text-decoration: underline;
    p.WD_DocumentMap {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: .0001pt;
    margin-left: .5in;
    font-size: 8.0pt;
    font-family: Tahoma, sans-serif;
    color: #262626;
    p.WD_Acetate {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: .0001pt;
    margin-left: .5in;
    font-size: 8.0pt;
    font-family: Tahoma, sans-serif;
    color: #262626;
    p.WD_Bullet1 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    text-indent: -.25in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    margin-left: 0.75in;
    p.WD_Bullet2 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    text-indent: -0.23in;
    margin-left: 0.98in;
    p.WD_Bullet3 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    text-indent: -12px;
    margin-left: 108px;
    p.WD_Subtopic {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: .5in;
    font-size: 14.0pt;
    font-family: Calibri, sans-serif;
    font-weight: bold;
    font-style: italic;
    color: #00003f;
    p.WD_ChangeDate {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: .5in;
    font-size: 9.0pt;
    font-family: Calibri, sans-serif;
    font-weight: bold;
    font-style: italic;
    color: #00003f;
    p.WD_Note {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 6.0pt;
    margin-left: 27.0pt;
    text-indent: -27.0pt;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    p.WD_Note1 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: 45.0pt;
    text-indent: -27.0pt;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    font-weight: bold;
    p.WD_Note2 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: 1.25in;
    text-indent: -.5in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    p.WD_Note3 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: 1.5in;
    text-indent: -.5in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    p.WD_Number1 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    text-indent: -.25in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    margin-left: 0.75in;
    p.WD_Number2 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: 1.0in;
    text-indent: -.25in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    p.WD_Number3 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    margin-left: 120px;
    text-indent: -24px;
    p.WD_para1 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 6.0pt;
    margin-left: .75in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    p.WD_Paragraph {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 12.0pt;
    margin-left: .5in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #000000;
    p.WD_ParaIntro {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 6.0pt;
    margin-left: .5in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #000000;
    p.WD_Process {
    margin-top: 0in;
    margin-bottom: 3.0pt;
    margin-left: .5in;
    font-size: 16.0pt;
    font-family: Calibri, sans-serif;
    font-weight: bold;
    margin-right: 58px;
    text-align: justify;
    color: #4c89bc;
    p.WD_Subtopic1 {
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: .5in;
    background: #C9C9C9;
    font-size: 12.0pt;
    font-family: Calibri, sans-serif;
    font-weight: bold;
    color: #00003f;
    margin-top: .1in;
    p.WD_Subtopic2 {
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: .5in;
    background: #ffffff;
    font-size: 12.0pt;
    font-family: Calibri, sans-serif;
    font-weight: bold;
    color: #4c89bc;
    margin-top: 0.1in;
    p.WD_Topic {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 3.0pt;
    margin-left: .5in;
    border: none;
    padding: 0in;
    font-size: 18.0pt;
    font-family: Calibri, sans-serif;
    font-weight: bold;
    color: #000000;
    span.WD_NoteChar {
    font-family: Calibri, sans-serif;
    color: #262626;
    p.WD_Important {
    margin-top: 6.0pt;
    margin-right: 0in;
    margin-bottom: 6.0pt;
    margin-left: .5in;
    border: none;
    padding: 0in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #262626;
    p.WD_NoFormatting {
    margin: 0in;
    margin-bottom: .0001pt;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #000000;
    margin-left: 0.5pt;
    p.WD_Para2 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 6.0pt;
    margin-left: 1.0in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #000000;
    p.WD_Para3 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 6.0pt;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #000000;
    margin-left: 108px;
    span.WD_BalloonTextChar {
    font-family: Tahoma, sans-serif;
    color: #262626;
    span.WD_HTMLPreformattedChar {
    font-family: "Courier New";
    p.WD_Image {
    margin-top: 6.0pt;
    margin-right: 0in;
    margin-bottom: 6.0pt;
    margin-left: .75in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #000000;
    span.WD_DocumentMapChar {
    font-family: Tahoma, sans-serif;
    color: #262626;
    p.WD_Normal1 {
    margin-top: 0in;
    margin-right: 0in;
    margin-bottom: 6.0pt;
    margin-left: .5in;
    border: none;
    padding: 0in;
    font-size: 11.0pt;
    font-family: Calibri, sans-serif;
    color: #000000;
    span.WD_TopicChar {
    font-family: Calibri, sans-serif;
    color: #000000;
    font-weight: bold;
    span.WD_ParagraphChar {
    font-family: Calibri, sans-serif;
    color: #000000;
    span.WD_Number1Char {
    font-family: Calibri, sans-serif;
    color: #262626;
    span.WD_ProcessChar {
    font-family: Calibri, sans-serif;
    font-weight: bold;
    font-style: italic;
    color: #4c89bc;
    span.WD_ChangeDateChar {
    font-family: Calibri, sans-serif;
    color: #595959;
    font-weight: bold;
    font-style: italic;
    span.WD_para1Char {
    font-family: Calibri, sans-serif;
    color: #262626;
    OL {
    margin-top: 0px;
    margin-bottom: 0px;
    UL {
    margin-top: 0px;
    margin-bottom: 0px;
    rh-list.MSWordList2 {
    x-level-count: 3;
    x-lvl-1-text-indent: -24px;
    x-lvl-1-type: bullet001;
    x-lvl-1-format: "<x>";
    x-lvl-2-format: "<x>";
    x-lvl-2-text-indent: -24px;
    x-lvl-2-type: bullet002;
    x-lvl-3-format: "<x>";
    x-lvl-3-text-indent: -24px;
    x-lvl-3-type: bullet003;
    rh-list.MSWordList1 {
    x-level-count: 2;
    x-lvl-1-text-indent: -24px;
    x-lvl-1-margin: 24px;
    x-lvl-1-type: decimal;
    x-lvl-1-format: "<x>.";
    x-lvl-2-format: "<x>";
    x-lvl-2-text-indent: -24px;
    x-lvl-2-type: bullet004;
    x-lvl-2-margin: 72px;
    rh-list.MSWordList0 {
    x-level-count: 3;
    x-lvl-1-text-indent: -24px;
    x-lvl-1-type: decimal;
    x-lvl-1-format: "<x>.";
    x-lvl-2-format: "<x>.";
    x-lvl-2-text-indent: -24px;
    x-lvl-2-type: lower-alpha;
    x-lvl-2-margin: 120px;
    x-lvl-3-format: "<x>.";
    x-lvl-3-text-indent: -12px;
    x-lvl-3-type: lower-roman;
    rh-seq.bullet002 {
    x-count: 1;
    x-1: o;
    x-font: Courier New;
    rh-seq.bullet003 {
    x-count: 1;
    x-1: ;
    x-font: Wingdings;
    rh-seq.bullet004 {
    x-count: 1;
    x-1: ;
    x-font: Wingdings;
    rh-seq.bullet001 {
    x-count: 1;
    x-1: ;
    x-font: Symbol;
    p.Paragraph {

Maybe you are looking for