HotSync Manager 7.0.2 Log not updating

I'm using Windows Vista Business, and am Syncing a Z22 with Microsoft Outlook 2007 (having installed the Outlook 2007 palm conduit) via USB.
The sync is happening fine. However HotSync log stopped updating the day shortly after its installation, and again after its reinstallation. I can still view a limited log on my Z22 and by hovering over the sync icon in the system tray it provides me with the correct time and date of the "Last HotSync" but information is no longer recorded on the HotSync log. Makes it difficult to guess what conflicts have occurred when something goes wrong! Any solutions? I have already tried reinstalling Palm Desktop and the Outlook 2007 Conduit and thankfully didn't lose any data in the process. Any other ideas?
Thanks,
Loz
Post relates to: Palm Z22

when you are using windows vista, the components of the palm software will be separated into different locations.
that's why it's very critical for you to know the location of each components especially the username folder and the palm folder itself.
unlike the previous OS versions, that the after the palm software is installed, you can see the contents of it in one folder and in one location.
if you haven't tried going to those locations and folders when you do the uninstall process, i think you need to do it again.
you don't need to worry about the data that you have since it's your palm as well as it's also inside the username folder aside from the fact that the device is syncing fine.
so there is no need for you to worry about because if there's nothing wrong with the device it should sync again after reinstalling the software.
so if you want to make sure that you have all the copy, you can backup the username folder too.
i have other approach in doing it but there is one process that was posted here that will guide you on how to do clean uninstall.
Here are the "clean" uninstall instructions for Vista.
You should first make a copy of your data to have just in case something
happens. You can find your data files by going to Start --> Documents -->
Palm OS Desktop. Highlight your Palm Desktop username and right click and
copy. Then go to your PC desktop right click on a blank spot and select paste.
Now you want to uninstall Palm Desktop and remove everything that has to do
with Palm Desktop from your computer.
Go to the following locations on the PC and delete the folders listed below.
C:\Program Files\Palm or Palm One
C:\Users\[Vista Login Name]\appdata\local\virtualstore\Program Files\Palm or
PalmOne
C:\Users\[Vista Login Name]\appdata
*Note you may need to view hidden folders to get to appdata. To do that go
into your control panel and open folder options. Go to view tab and uncheck
hide hidden files.
Once this is done you will need to delete some registry keys from your PC Operating System.
Word of warning, going here and deleting the wrong thing can cause your PC
from starting up, crashing and deletion of programs and data. If you feel
you are unsure of yourself, see if you have a friend that can help you or a
PC technician that you can pay to help you. This procedure will show them everything they need to delete. To make sure we have a good copy of the current registry, we need to do a backup of the Registry.
Go to start on the PC, in the search field type "regedit.exe" without quotes.
Highlight COMPUTER, go to File --> Export. Should pop up with a Save As box.
Current location is fine, should be in My Documents or save to a location you will remember. In the file name on the bottom type "backup[todaysdate]" i.e. backup07072008. Next, the hard part.
The easiest way to make sure your working with the correct key, highlight the key i.e. palm quick install, and press delete on your keyboard. It will ask you, are you sure. Say yes. Do the same thing for all keys below.
If you make a mistake, stop what you are doing. And call a PC technician.
BUT do not turn off your computer.
The reg keys are as follows (Note: some of theses reg keys will not be here
but if they are delete them)
* HKEY_CURRENT_USER\Software\U.S. Robotics\Palm Quick Install
* HKEY_CURRENT_USER\Software\U.S. Robotics\PalmOne File Transfer
* HKEY_CURRENT_USER\Software\U.S. Robotics\Pilot Desktop
* HKEY_CURRENT_USER\Software\Palm
* HKEY_CURRENT_USER\Software\Palm, Inc.
* HKEY_CURRENT_USER\Software\PalmDesktopAutorun
* HKEY_CURRENT_USER\Software\palmOne
* HKEY_CURRENT_USER\Software\PalmSource
* HKEY_LOCAL_MACHINE\Software\PalmSource or anything else that says palm
Next reboot your computer.
Then reinstall your palm desktop from the CD and do a hotsync. If it asks
you for a username and you synced your device before, put in 'test" if you
did not sync before create a hotsync name.
Post relates to: Treo 680 (Unlocked GSM)

Similar Messages

  • C:\Program Files\Microsoft Configuration Manager\Logs not updating

    Hi,
    Anybody exprienced the scenario where logfiles in C:\Program Files\Microsoft Configuration Manager\Logs don't update anymore?
    F.e. wsyncmgr.log is of beginning of April, no recent logs there except for 7 items: smsprov.smspxe, smsdpusage  (date from Today).
    Pls advise.
    J.
    Jan Hoedt

    Open ConfigMgr Service Manager and check the logging options (is logging for each component enabled at all? Is it really logging to the directory you examined?) You can also open the logs using notepad. cmtrace.exe sometimes does not display the entire
    content if there are malformated lines.
    Having installed ConfigMgr on the C:\ drive is not the best setup BTW.
    Torsten Meringer | http://www.mssccmfaq.de

  • Despool.log,smsexec,hman,sitectrl,ccm and a bunch of other logs not updating

    Env: SCCM 2007 R3
    Site- Child Primary
    Secondary- None
    Hello Experts, We have a strange situation in one of our's  environment. On  one of our child primaries Reporting to a Central, Despool.log,smsexec,hman,sitectrl,ccm and a bunch of other logs are not updating. The last timestamp on these logs
    dates back to almost 4 years. Attched is a snippet from the
    despool.log 
    SMS_EXECUTIVE started SMS_DESPOOLER as thread ID 4672 (0x1240).
    SMS_DESPOOLER 9/23/2010 4:22:42 PM
    5876 (0x16F4)
    Despooler is starting... SMS_DESPOOLER
    9/23/2010 4:22:42 PM 4672 (0x1240)
    Hman.box\Pubkey Inbox not defined yet. SMS_DESPOOLER
    9/23/2010 4:22:42 PM 4672 (0x1240)
    Waiting for the inbox manager to create the inboxes, retry in 10 seconds.
    SMS_DESPOOLER 9/23/2010 4:22:42 PM
    4672 (0x1240)
    Hman.box\Pubkey Inbox not defined yet. SMS_DESPOOLER
    9/23/2010 4:22:52 PM 4672 (0x1240)
    Waiting for the inbox manager to create the inboxes, retry in 10 seconds.
    SMS_DESPOOLER 9/23/2010 4:22:52 PM
    4672 (0x1240)
    Hman.box\Pubkey Inbox not defined yet. SMS_DESPOOLER
    9/23/2010 4:23:02 PM 4672 (0x1240)
    Waiting for the inbox manager to create the inboxes, retry in 10 seconds.
    SMS_DESPOOLER 9/23/2010 4:23:02 PM
    4672 (0x1240)
    Hman.box\Pubkey Inbox not defined yet. SMS_DESPOOLER
    9/23/2010 4:23:12 PM 4672 (0x1240)
    Waiting for the inbox manager to create the inboxes, retry in 10 seconds.
    SMS_DESPOOLER 9/23/2010 4:23:12 PM
    4672 (0x1240)
    CPublicKeyLookup::Initialize("E:\SMS\inboxes\hman.box\pubkey")
    SMS_DESPOOLER 9/23/2010 4:23:22 PM
    4672 (0x1240)
    CPublicKeyLookup::Initialize()  Initializing the Public Key Store Path to E:\SMS\inboxes\hman.box\pubkey
    SMS_DESPOOLER 9/23/2010 4:23:22 PM
    4672 (0x1240)
    Waiting for the next instruction.... SMS_DESPOOLER
    9/23/2010 4:23:22 PM 4672 (0x1240)
    Waiting for ready instruction file.... SMS_DESPOOLER
    9/23/2010 4:23:22 PM 4672 (0x1240)
    SMS_EXECUTIVE signalled SMS_DESPOOLER to stop.
    SMS_DESPOOLER 9/23/2010 4:25:09 PM
    5876 (0x16F4)
    SMS_EXECUTIVE started SMS_DESPOOLER as thread ID 5992 (0x1768).
    SMS_DESPOOLER 9/23/2010 4:30:06 PM
    4388 (0x1124)
    Despooler is starting... SMS_DESPOOLER
    9/23/2010 4:30:06 PM 5992 (0x1768)
    CPublicKeyLookup::Initialize("E:\SMS\inboxes\hman.box\pubkey")
    SMS_DESPOOLER 9/23/2010 4:30:06 PM
    5992 (0x1768)
    CPublicKeyLookup::Initialize()  Initializing the Public Key Store Path to E:\SMS\inboxes\hman.box\pubkey
    SMS_DESPOOLER 9/23/2010 4:30:06 PM
    5992 (0x1768)
    Waiting for the next instruction.... SMS_DESPOOLER
    9/23/2010 4:30:06 PM 5992 (0x1768)
    Waiting for ready instruction file.... SMS_DESPOOLER
    9/23/2010 4:30:06 PM 5992 (0x1768)
    Waiting for ready instruction file.... SMS_DESPOOLER
    9/23/2010 4:35:06 PM 5992 (0x1768)
    Waiting for ready instruction file.... SMS_DESPOOLER
    9/23/2010 4:40:06 PM 5992 (0x1768)
    hman.log 
    SMS_EXECUTIVE started SMS_HIERARCHY_MANAGER as thread ID 5708 (0x164C).
    SMS_HIERARCHY_MANAGER 9/23/2010 4:22:50 PM
    5876 (0x16F4)
    Hierarchy Manager (build 2726) is starting...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:22:50 PM
    5708 (0x164C)
    Createded inbox def 21, Hierarchy Manager (Site Public Keys)
    SMS_HIERARCHY_MANAGER 9/23/2010 4:22:50 PM
    5708 (0x164C)
    Waiting for the inbox manager to create the inboxes, retry in 10 seconds.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:22:50 PM
    5708 (0x164C)
    Waiting for the inbox manager to create the inboxes, retry in 10 seconds.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:00 PM
    5708 (0x164C)
    Waiting for the inbox manager to create the inboxes, retry in 10 seconds.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:10 PM
    5708 (0x164C)
    Waiting for the inbox manager to create the inboxes, retry in 10 seconds.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:20 PM
    5708 (0x164C)
    CPublicKeyLookup::Initialize("E:\SMS\inboxes\hman.box\pubkey")
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:30 PM
    5708 (0x164C)
    CPublicKeyLookup::Initialize()  Initializing the Public Key Store Path to E:\SMS\inboxes\hman.box\pubkey
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:30 PM
    5708 (0x164C)
    Successfully created the file E:\SMS\inboxes\hman.box\pubkey\WE1.CT4
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:30 PM
    5708 (0x164C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:30 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\1QBDV41P.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:47 PM 5708 (0x164C)
    Added IP subnet boundary XXXXXXXXX for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    Added IP subnet roaming boundary 162.116.108.0 for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    Update Site Boundaries in Active Directory SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:47 PM 5708 (0x164C)
    Active Directory DS Root:DC=europe,DC=companyname,DC=com
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    Searching for the System Management Container.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    System Management container exists. SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:47 PM 5708 (0x164C)
       Searching for SMS-Site-WE1 Site Object.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
       SMS-Site-WE1 exists, updating.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    SMS-Site-WE1 successfully updated. SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:47 PM 5708 (0x164C)
       No Ranged IP boundaries are currently published for this site.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    Checking Site WE1 for legacy clients that should be upgraded.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
      There are 0 Legacy clients that should be upgraded.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
      There are no Legacy clients that need to be upgraded.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:47 PM
    5708 (0x164C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=5932 TID=5708 GMTDATE=Thu Sep 23 15:23:48.018 2010 ISTR0="E:\SMS\inboxes\hman.box\1QBDV41P.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="2" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\57E98FBF.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:48 PM 5708 (0x164C)
    Update Site Boundaries in Active Directory SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:48 PM 5708 (0x164C)
    Active Directory DS Root:DC=europe,DC=Company Name,DC=com
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Searching for the System Management Container.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    System Management container exists. SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:48 PM 5708 (0x164C)
       Searching for SMS-Site-WE1 Site Object.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
       SMS-Site-WE1 exists, updating.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    SMS-Site-WE1 successfully updated. SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:48 PM 5708 (0x164C)
       No Ranged IP boundaries are currently published for this site.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=5932 TID=5708 GMTDATE=Thu Sep 23 15:23:48.253 2010 ISTR0="E:\SMS\inboxes\hman.box\57E98FBF.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="4" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\7A19VJS4.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:48 PM 5708 (0x164C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=5932 TID=5708 GMTDATE=Thu Sep 23 15:23:48.425 2010 ISTR0="E:\SMS\inboxes\hman.box\7A19VJS4.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="5" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\D21RW09M.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    The serial number (3) for the site control file E:\SMS\inboxes\hman.box\D21RW09M.CT2 (site = WE1) is out of date, discard it, the current site serial number is 5
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\EY11UBMU.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    The serial number (1) for the site control file E:\SMS\inboxes\hman.box\EY11UBMU.CT2 (site = WE1) is out of date, discard it, the current site serial number is 5
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\KUG3AFQK.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:48 PM 5708 (0x164C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=5932 TID=5708 GMTDATE=Thu Sep 23 15:23:48.800 2010 ISTR0="E:\SMS\inboxes\hman.box\KUG3AFQK.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="7" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\OEZY8O61.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:48 PM 5708 (0x164C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=5932 TID=5708 GMTDATE=Thu Sep 23 15:23:48.957 2010 ISTR0="E:\SMS\inboxes\hman.box\OEZY8O61.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="8" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:48 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:49 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\QRF7VIJ3.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:49 PM
    5708 (0x164C)
    The serial number (6) for the site control file E:\SMS\inboxes\hman.box\QRF7VIJ3.CT2 (site = WE1) is out of date, discard it, the current site serial number is 8
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:49 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:49 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\X4UWXAF1.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:49 PM
    5708 (0x164C)
    The serial number (0) for the site control file E:\SMS\inboxes\hman.box\X4UWXAF1.CT2 (site = WE1) is out of date, discard it, the current site serial number is 8
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:49 PM
    5708 (0x164C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:49 PM
    5708 (0x164C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:54 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:59 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\DUBF11E6.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:59 PM
    5708 (0x164C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:23:59 PM 5708 (0x164C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:59 PM
    5708 (0x164C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:59 PM
    5708 (0x164C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=5932 TID=5708 GMTDATE=Thu Sep 23 15:23:59.359 2010 ISTR0="E:\SMS\inboxes\hman.box\DUBF11E6.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="9" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:59 PM
    5708 (0x164C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:23:59 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:04 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\5W17YLXW.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:04 PM
    5708 (0x164C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:24:04 PM 5708 (0x164C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:04 PM
    5708 (0x164C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:04 PM
    5708 (0x164C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=5932 TID=5708 GMTDATE=Thu Sep 23 15:24:04.960 2010 ISTR0="E:\SMS\inboxes\hman.box\5W17YLXW.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="12" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:04 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:05 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\BS1DWBNV.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:05 PM
    5708 (0x164C)
    The serial number (10) for the site control file E:\SMS\inboxes\hman.box\BS1DWBNV.CT2 (site = WE1) is out of date, discard it, the current site serial number is 12
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:05 PM
    5708 (0x164C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:05 PM
    5708 (0x164C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\ZOH1WY14.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:05 PM
    5708 (0x164C)
    The serial number (11) for the site control file E:\SMS\inboxes\hman.box\ZOH1WY14.CT2 (site = WE1) is out of date, discard it, the current site serial number is 12
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:05 PM
    5708 (0x164C)
    Did not detect any site control change for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:05 PM
    5708 (0x164C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:05 PM
    5708 (0x164C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:10 PM
    5708 (0x164C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:24:15 PM
    5708 (0x164C)
    SMS_EXECUTIVE signalled SMS_HIERARCHY_MANAGER to stop.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:25:21 PM
    5876 (0x16F4)
    SMS_EXECUTIVE started SMS_HIERARCHY_MANAGER as thread ID 5260 (0x148C).
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:21 PM
    4388 (0x1124)
    Hierarchy Manager (build 4253) is starting...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:21 PM
    5260 (0x148C)
    CPublicKeyLookup::Initialize("E:\SMS\inboxes\hman.box\pubkey")
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:21 PM
    5260 (0x148C)
    CPublicKeyLookup::Initialize()  Initializing the Public Key Store Path to E:\SMS\inboxes\hman.box\pubkey
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:21 PM
    5260 (0x148C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:21 PM
    5260 (0x148C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:50 PM
    5260 (0x148C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\HY5VNP71.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:50 PM
    5260 (0x148C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:30:51 PM 5260 (0x148C)
    Update Site Boundaries in Active Directory SMS_HIERARCHY_MANAGER
    9/23/2010 4:30:51 PM 5260 (0x148C)
    Active Directory DS Root:DC=europe,DC=Companyname,DC=com
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
    Searching for the System Management Container.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
    System Management container exists. SMS_HIERARCHY_MANAGER
    9/23/2010 4:30:51 PM 5260 (0x148C)
       Site objects existing in AD: cn=SMS-Site-WE1.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
       Searching for SMS-Site-WE1 Site Object.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
       SMS-Site-WE1 exists, updating.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
    SMS-Site-WE1 successfully updated. SMS_HIERARCHY_MANAGER
    9/23/2010 4:30:51 PM 5260 (0x148C)
       Removing cn=SMS-Site-WE1 from site deletion-pending list.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
       No Ranged IP boundaries are currently published for this site.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=3952 TID=5260 GMTDATE=Thu Sep 23 15:30:51.397 2010 ISTR0="E:\SMS\inboxes\hman.box\HY5VNP71.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="13" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\KSF6AZ2G.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:51 PM
    5260 (0x148C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:30:51 PM 5260 (0x148C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:53 PM
    5260 (0x148C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:53 PM
    5260 (0x148C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=3952 TID=5260 GMTDATE=Thu Sep 23 15:30:53.210 2010 ISTR0="E:\SMS\inboxes\hman.box\KSF6AZ2G.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="14" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:53 PM
    5260 (0x148C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:53 PM
    5260 (0x148C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\U968WBBI.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:53 PM
    5260 (0x148C)
    The serial number (12) for the site control file E:\SMS\inboxes\hman.box\U968WBBI.CT2 (site = WE1) is out of date, discard it, the current site serial number is 14
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:53 PM
    5260 (0x148C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:53 PM
    5260 (0x148C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:30:58 PM
    5260 (0x148C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:03 PM
    5260 (0x148C)
    Site WE1 in Sites table: Site status = 1, Detailed status = 1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:47 PM
    5260 (0x148C)
    Processing site control file: Site WE1 File E:\SMS\inboxes\hman.box\BM17MXSM.CT2
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:47 PM
    5260 (0x148C)
    Update the Sites table: Site=WE1 Parent= SMS_HIERARCHY_MANAGER
    9/23/2010 4:31:47 PM 5260 (0x148C)
    There is no parent site, no need to forward any site control images.
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:48 PM
    5260 (0x148C)
    Created site control notification for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:48 PM
    5260 (0x148C)
    STATMSG: ID=3306 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_HIERARCHY_MANAGER" SYS=WEAPPS101 SITE=WE1 PID=3952 TID=5260 GMTDATE=Thu Sep 23 15:31:48.356 2010 ISTR0="E:\SMS\inboxes\hman.box\BM17MXSM.CT2" ISTR1="Westport Site
    1" ISTR2="WE1" ISTR3="15" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:48 PM
    5260 (0x148C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:48 PM
    5260 (0x148C)
    Did not detect any site control change for site WE1
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:53 PM
    5260 (0x148C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:53 PM
    5260 (0x148C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:31:58 PM
    5260 (0x148C)
    Wait for site control changes for maximum 3600 seconds...
    SMS_HIERARCHY_MANAGER 9/23/2010 4:32:03 PM
    5260 (0x148C)
    Until last month regular stuff like software distribution (package replication), Patching, processing of state msgs and almost everything else was working fine, it was this month that we came across some issues with replicating of packages and took a look at
    the various logs and found this. Distmgr, Sender, schedule, replmgr.log still moves. We have tried manually exchanging keys, restarted the components, verified that the computer account
    is added to the Site to SiteConnection  group and  Site to Site Server Connection Group and  on the Central server and vice versa. Computer Account has access to the Systems management container and site information is published. Re-doing
    the site is not an ideal option for us. Can someone throw some light on what might be causing this?

    Guys,
    Got the solution to this. It happened to be the value of the key 'Enabled' on the location below for the specific
    components, which had a Value Data '0' " HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Tracing" 
    . On changing the value to 1 and restarting the SMS services. The logs went live!

  • Mail logs not updating

    Hi,
    I have updated amavisd-new, ClamAV, and SpamAssassin as per OSX.TopicDesk's instructions but my logs in Server Admin and Console do not appear to be updating although mail is still working.
    freshclam.log shows;
    Received signal: wake up
    Max retries == 3
    ClamAV update process started at Fri Jul 25 10:02:03 2008
    SECURITY WARNING: NO SUPPORT FOR DIGITAL SIGNATURES
    See the FAQ at http://www.clamav.net/support/faq for an explanation.
    Querying current.cvd.clamav.net
    TTL: 1610
    Software version from DNS: 0.93.3
    WARNING: Your ClamAV installation is OUTDATED!
    WARNING: Local version: 0.92 Recommended version: 0.93.3
    DON'T PANIC! Read http://www.clamav.net/support/faq
    main.cvd version from DNS: 47
    main.inc is up to date (version: 47, sigs: 312304, f-level: 31, builder: sven)
    daily.cvd version from DNS: 7824
    Retrieving http://database.clamav.net/daily-7822.cdiff
    Trying to download http://database.clamav.net/daily-7822.cdiff (IP: 81.91.101.77)
    Downloading daily-7822.cdiff [100%]
    cdiff_apply: Parsed 7 lines and executed 7 commands
    Retrieving http://database.clamav.net/daily-7823.cdiff
    Trying to download http://database.clamav.net/daily-7823.cdiff (IP: 81.91.101.77)
    Downloading daily-7823.cdiff [100%]
    cdiff_apply: Parsed 122 lines and executed 122 commands
    Retrieving http://database.clamav.net/daily-7824.cdiff
    Trying to download http://database.clamav.net/daily-7824.cdiff (IP: 81.91.101.77)
    Downloading daily-7824.cdiff [100%]
    cdiff_apply: Parsed 12 lines and executed 12 commands
    Removing backup directory ./clamav-509787fd7e305c069b24e20ef560c936
    daily.inc updated (version: 7824, sigs: 59418, f-level: 33, builder: ccordes)
    WARNING: Your ClamAV installation is OUTDATED!
    WARNING: Current functionality level = 25, recommended = 33
    DON'T PANIC! Read http://www.clamav.net/support/faq
    Database updated (371722 signatures) from database.clamav.net (IP: 81.91.101.77)
    Yet issuing clamconf tells me my version is 0.94.2;
    /private/etc/spam/clamav/clamd.conf: freshclam directives
    LogFileMaxSize = 0
    LogTime = yes
    LogVerbose = no
    LogSyslog = no
    LogFacility = "LOG_LOCAL6"
    PidFile = "/var/clamav/clamd.pid"
    DatabaseDirectory = "/var/clamav"
    Foreground = yes
    Debug = no
    AllowSupplementaryGroups = yes
    DatabaseOwner = "clamav"
    Checks = 12
    UpdateLogFile not set
    DNSDatabaseInfo = "current.cvd.clamav.net"
    DatabaseMirror not set
    MaxAttempts = 3
    ScriptedUpdates = yes
    CompressLocalDatabase = no
    HTTPProxyServer not set
    HTTPProxyPort not set
    HTTPProxyUsername not set
    HTTPProxyPassword not set
    HTTPUserAgent not set
    NotifyClamd not set
    OnUpdateExecute not set
    OnErrorExecute not set
    OnOutdatedExecute not set
    LocalIPAddress not set
    ConnectTimeout = 30
    ReceiveTimeout = 30
    SubmitDetectionStats not set
    DetectionStatsCountry not set
    /private/etc/spam/clamav/freshclam.conf: freshclam directives
    LogFileMaxSize = 0
    LogTime = no
    LogVerbose = yes
    LogSyslog = no
    LogFacility = "LOG_LOCAL6"
    PidFile = "/var/clamav/freshclam.pid"
    DatabaseDirectory = "/var/clamav"
    Foreground = yes
    Debug = no
    AllowSupplementaryGroups = no
    DatabaseOwner = "clamav"
    Checks = 12
    UpdateLogFile = "/var/log/freshclam.log"
    DNSDatabaseInfo = "current.cvd.clamav.net"
    DatabaseMirror = "database.clamav.net"
    MaxAttempts = 3
    ScriptedUpdates = yes
    CompressLocalDatabase = no
    HTTPProxyServer not set
    HTTPProxyPort not set
    HTTPProxyUsername not set
    HTTPProxyPassword not set
    HTTPUserAgent not set
    NotifyClamd not set
    OnUpdateExecute not set
    OnErrorExecute not set
    OnOutdatedExecute not set
    LocalIPAddress not set
    ConnectTimeout = 30
    ReceiveTimeout = 30
    SubmitDetectionStats not set
    DetectionStatsCountry not set
    Engine and signature databases
    Engine version: 0.94.2
    Database directory: /private/var/clamav
    main db: Format: .cvd, Version: 49, Build time: Wed Oct 22 23:03:26 2008
    daily db: Format: .cvd, Version: 8683, Build time: Wed Nov 26 06:58:25 2008
    The last few entries in clamav.log are;
    Thu Jul 24 09:40:32 2008 -> ERROR: accept() failed: Too many open files
    Log size = 1048632, max = 1048576
    LOGGING DISABLED (Maximal log file size exceeded).
    Log size = 1048717, max = 1048576
    LOGGING DISABLED (Maximal log file size exceeded).
    Log size = 1048802, max = 1048576
    LOGGING DISABLED (Maximal log file size exceeded).
    Log size = 1048887, max = 1048576
    LOGGING DISABLED (Maximal log file size exceeded).
    amavis.log does not appear to have updated since Feb 1st
    I am not that good with command line stuff so please does anybody know what the **** is going on here!!!
    Thanks,
    John
    Message was edited by: Mark Davies
    Message was edited by: Mark Davies (didn't know h e l l was a swear word!!!)

    Hi Alex,
    Thanks for all your help it's just unfortunate where that linebreak fell in the tutorial!
    missing space:
    ... --mandir=/usr/share/man--sysconfdir=/private/etc/spam/clamav/new ...
    should be:
    ... --mandir=/usr/share/man --sysconfdir=/private/etc/spam/clamav/new ...
    Issuing the previously mentioned commands now gives;
    sudo ps U clamav
    PID TT STAT TIME COMMAND
    49 ?? SNs 0:12.46 clamd
    50 ?? SNs 0:00.07 freshclam -d -p /var/clamav/freshclam.pid -c 3
    51 ?? Ss 0:04.25 amavisd (master)
    9805 ?? S 0:02.98 amavisd (ch7-avail)
    10183 ?? S 0:01.33 amavisd (ch4-avail)
    sudo /usr/local/bin/freshclam -V
    ClamAV 0.94.2/9002/Wed Feb 18 11:16:50 2009
    sudo /usr/bin/amavisd -V
    amavisd-new-2.6.2 (20081215)
    sudo launchctl list | grep clam
    net.clamav.clamd
    net.clamav.freshclam
    Freshclam.log is now showing the correct version but clamav.log and amavis.log still haven't changed.
    You mentioned something about amavisd.conf is this why they logs are not updating and if so how do amavisd to log in the right place?
    Thanks,
    John

  • Firewall log not updating

    Logging of denied packets is enabled on our 10.4 Server and it used to display the log just fine. However the current log file is now empty and is not updating at all. I've tried deleting the log and new log file is created but nothing is written to it even if I enable logging of allowed packets.
    Anyone know what would be causing this problem or how to fix it?

    I'm now having some other problems on the server so I ran repair permissions and this has fixed the firewall log problem. I don't know how the permissions became corrupted.

  • Class attribute in technical workflow log not updated

    Hi Gurus,
    I built a workflow analogous to the famous demo workflow "demoformabs" but with the demo class: CL_SWF_FORMABSENC instead of the BOR: FORMABSENC.
    In the BOR Formabsenc there is also an attribute for the "Approver" (USR01) in addition to "Creator" (USR01).
    This attribute "Approver" is missing in the class "CL_SWF_FORMABSENC".
    So I added this attribute "Approver" also in the class "CL_SWF_FORMABSENC":
    data APPROVER type SIBFLPORB value CL_SWF_BOR_TYPES=>MC_USR01.
    Finally in the method "approve" I set the value for the attribute "APPROVER".
    me->approver-instid = me->APPROVBY.
    I can see that the value has been successfully set by setting a binding from this class attribute to a workflow container element.
    BUT, in the technical workflow log (container) I can not see the class attribute "Approver" populated.
    Here it´s still displayed as < no instance >.
    What do I need to do, to make this value appear also in this class attribute in the technical workflow log?
    Albeit I know, that it´s working, I am getting confused, that it´s still displayed as empty.
    Cheers,
    Dominik

    Hi Dominik,
    You should not populate attributes in this manner, for the very reason you're experiencing. Attributes are transient and behave like variables, i.e. when the class stops existing they disappear. During binding only the key is transferred, and - if needed - the class is re-instantiated at the other end. If you have implemented some kind of buffering/instance management (not a bad idea), then you may be lucky to have attributes survive if everything happens within the same program context. However once your WF session stops executing, this is lost.
    This is why when you look at the log later, it is re-instantiating a completely new instance - where would it know the approver from?
    The attribute value must be written to the DB somewhere, so that any later object instantiation (e.g. when you look at the log) will read the value and populate the attributes correctly.
    Incidentally this is why OO theory discourages the use of public attributes and suggests GET_ and SET_ methods instead....
    Regards,
    Mike

  • Amavis.log not updating..

    I just noticed that since I updated my amavisd-new, clamav, and spamassassin back in October of last year, my amavis.log file hasn't been getting updated. Am I looking in the wrong place or is there a switch somewhere I need to flip?
    My Junk Mail/Virus log detail level is set to DEBUG.
    Any help or guidance would be appreciated.
    Thanks
    Mike

    Newer versions are set to log into mail.log. You can change this in amavisd.conf if you prefer.

  • ChaRM Transaction Data Log Not Updating in 7.1

    Upgraded to 7.1 and still using 7.0 CRM_DNO_MONITOR and CRMD_ORDER to completed change requests in flight in existing projects.  The Transaction Data tab's Object and the Fast Entry tab's Overview show entries for action taken prior to upgrade.  However there are no new entries for actions used or transports created after we started using 7.1.  Is this still supported?  Where can I see updates the the CR/CD for audit and reference purposes?

    It depends a bit on your final intention. Bascially you have a shared state that you want to access asynchronously from different places. If you know that the actual object is only created once (terminilogie here is a bit shaky as every wire split would create a copy of the LVOOP object but I hope you know what I mean), you could use a global or Action Engine to store the state. Using a DVR for this state and adding the DVR to your object class data is however a more scalable approach as it will allow you to instantiate more than one object of that class and each one will contain its own DVR that will reference the same value for the specific object instance even if you split the object wire, creating actually two copies of that object (but for the purpose of this discussion they would be still the same object instance).
    Queues could work if you create a single element queue but you would always need to use Preview Queue rather than Dequeue in order to maintain the value in there.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Managed servers cache not updated when we deploy a new EAR....

    Hi All,
    I have the following query :
    Perform the following steps :
    1. Stop the managed servers
    2. Delete and create jms servers
    3. Undeploy existing EARs
    4. Deploy new EARs
    5. Start the managed servers
    If we perform these steps we see that the managed server cache normally get a copy of the new EARs from the admin server.
    However if we modify the above steps as :
    1. Stop the managed servers
    2. Delete and create jms servers
    3. Undeploy existing EARs
    4. Deploy new EARs
    5. Re-do step #2, i.e. delete and create jms servers
    6. Start the managed servers
    This time the managed server's cache is not updated with the new EAR file when it starts up.
    Any idea as to why this behaviour....also the EAR could be a small sample MDB application from weblogic.
    We deploy these app via java weblogic.Deployer command.
    Any thoughts ..would be highly appreciated ....
    Regards,
    Stacey.
    Edited by: stacey on Jun 22, 2010 8:35 PM

    Hi Stacey,
    Did you check the EAR copy cached before doing Setp 5
    ("5. Re-do step #2, i.e. delete and create jms servers")
    Can you confirm once.
    Regards,
    Kal.

  • Connector Status not updating

    As a result of a dramatic failure of communication the SCSM workflow AD account was deleted and recreated, after some muching about everything in SCSM is now working normally again except the config manager and AD connectors are not updating their status.
    I initially thought they were not running at all but I have confirmed that they are in fact synchronizing data from their respective sources and its just the display of the status that is not updating.  I tried deleting them and recreating them and
    now they display no status i.e. the start time, finish time, status, and Percentage columns are all blank.
    I have done a bit of research and believe that the problem is that the relationships between the Connectors and their respective SyncStatus objects is missing/broken, and for some reason creating new Connectors either does not establish a corresponding
    SyncStatus object or does but does not relate it to the connector.
    I have a couple of reasons for this hypothesis first is when I run this powershell*:
    $connectorDispName="Your Connector Name Here"
    #Following will return in instance of Microsoft.EnterpriseManagement.ServiceManager.Sdk.Connectors.ADConnector
    $myConnector=Get-SCSMConnector -DisplayName $connectorDispName
    #Get the EMO object for relationship lookup
    $emoConnObj=$myConnector.ConnectorObject
    #Relationship id can be retrieved with following:
    #Get-SCRelationship -Name 'Microsoft.SystemCenter.LinkingFramework.DataSourceHostSyncStatus'|select id
    $relationshipId='1548950d-6cea-d9c1-11ec-53701fbcbbec'
    #Find the matching relationship object (with the above relationshipId)
    $relationshipObject=Get-SCRelationshipInstance -sourceInstance $emoConnObj|?{$_.RelationshipId -eq $relationshipId}
    #$relationshipObject.TargetObject contains an EMO.
    #Grab the id and use Get-SCClassInstance to return a type of Microsoft.SystemCenter.LinkingFramework.SyncStatus
    $syncStatusObj=Get-SCClassInstance -Id $relationshipObject.TargetObject.Id
    The following error is returned:
    Get-SCClassInstance : Cannot validate argument on Parameter 'Id'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
    At D:\tools\scripts\ConnectorSyncStatus.ps1:14 char:40
    + $syncStatusObj=Get-SCClassInstance -Id $relationshipObject.TargetObject.Id
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidData: (:) [Get-SCClassInstance], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.SystemCenter.Core.Commands.GetSCClassInstanceCommand
    Possibly the Powershell is incorrect but this result implies to me that the Get-SCRelationshipInstance call is returning a null value for the syncstatus object which is being fed into the Get-SCClassinstance call.
    My second reason for this hypothesis is the following SQL results:
    select RelationshipTypeId from dbo.RelationshipType
    where dbo.relationshiptype.RelationshipTypeName = 'Microsoft.SystemCenter.LinkingFramework.DataSourceHostSyncStatus';
    1548950D-6CEA-D9C1-11EC-53701FBCBBEC
    select * from dbo.relationship
    where RelationshipTypeId = '1548950D-6CEA-D9C1-11EC-53701FBCBBEC';
    Returns no results.
    This implies to me that there are no instances of the relationship linking a Connector to its corresponding SyncStatus object.
    I am not an SQL or Powershell expert but I know enough to be dangerous, so does my reasoning seem correct? And if so how could I fix this?
    Thanks In advance
    * this Powershell is not of my own devising, I cribbed it from
    Steve IAnson in this question:
    Query Connector Status

    Yes there is every 1 minute there is a squence of entires as follows:
    Source: Lfx Service
    Event: ID 3334
    Data:
    Error setting status for property &. Error:The relationship source specified in the discovery data item is not valid.
    Relationship source ID: ae5465d3-2565-c7d3-0de2-acc994c1e928
    Rule ID: eb496966-4fb7-45bd-bdda-b689af383733
    Instance:
    <?xml version="1.0" encoding="utf-16"?>
    <RelationshipInstance TypeId="{1548950d-6cea-d9c1-11ec-53701fbcbbec}" SourceTypeId="{71f6cfcd-99b3-3a07-471d-bb9c4bf5ba76}" TargetTypeId="{2d4afd51-d2ff-92c6-266f-2b6060000dae}">
    <Settings />
    <SourceRole>
    <Settings>
    <Setting>
    <Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
    <Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
    </Setting>
    </Settings>
    </SourceRole>
    <TargetRole>
    <Settings>
    <Setting>
    <Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
    <Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
    </Setting>
    </Settings>
    </TargetRole>
    </RelationshipInstance>
    Status data:ConnectorId:ec4a037e-e0f0-47a2-b7e7-7932eba2a0ac;
    BaseManagementEntityId:e22fffb2-9b85-de47-fe3d-875914b21797;
    LastRunStartTime:25/11/2014 2:00:44 AM;
    LastRunFinishTime:25/11/2014 2:02:57 AM;
    NextSyncTime:27/11/2014 2:00:00 AM;
    Status:FinishedSuccess;
    SyncPercent:100;
    MaxValue:100;
    MinValue:0;.
    Source:OpsMgr SDK Service
    Event ID: 26319
    Data:
    An exception was thrown while processing ProcessDiscoveryData for session ID uuid:e47c3453-2524-44af-a9d9-2475e3a204a6;id=3.
    Exception message: The relationship source specified in the discovery data item is not valid.
    Relationship source ID: ae5465d3-2565-c7d3-0de2-acc994c1e928
    Rule ID: eb496966-4fb7-45bd-bdda-b689af383733
    Instance:
    <?xml version="1.0" encoding="utf-16"?>
    <RelationshipInstance TypeId="{1548950d-6cea-d9c1-11ec-53701fbcbbec}" SourceTypeId="{71f6cfcd-99b3-3a07-471d-bb9c4bf5ba76}" TargetTypeId="{2d4afd51-d2ff-92c6-266f-2b6060000dae}">
    <Settings />
    <SourceRole>
    <Settings>
    <Setting>
    <Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
    <Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
    </Setting>
    </Settings>
    </SourceRole>
    <TargetRole>
    <Settings>
    <Setting>
    <Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
    <Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
    </Setting>
    </Settings>
    </TargetRole>
    </RelationshipInstance>
    Full Exception: Microsoft.EnterpriseManagement.Common.DiscoveryDataInvalidRelationshipSourceException: The relationship source specified in the discovery data item is not valid.
    Relationship source ID: ae5465d3-2565-c7d3-0de2-acc994c1e928
    Rule ID: eb496966-4fb7-45bd-bdda-b689af383733
    Instance:
    <?xml version="1.0" encoding="utf-16"?><RelationshipInstance TypeId="{1548950d-6cea-d9c1-11ec-53701fbcbbec}" SourceTypeId="{71f6cfcd-99b3-3a07-471d-bb9c4bf5ba76}" TargetTypeId="{2d4afd51-d2ff-92c6-266f-2b6060000dae}">
    <Settings />
    <SourceRole>
    <Settings>
    <Setting>
    <Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
    <Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
    </Setting>
    </Settings>
    </SourceRole>
    <TargetRole>
    <Settings>
    <Setting>
    <Name>29906075-e9fc-7bc4-487b-f964f91d6532</Name>
    <Value>1e6592a2-96c3-4b99-a50a-c04ee2a793e6</Value>
    </Setting>
    </Settings>
    </TargetRole>
    </RelationshipInstance>
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.BulkUpsertRelationshipInstances(DiscoveryDatabaseApi dbApi, DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData)
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.BulkAddUpdate(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.ManagementStoreWriter.Write(DiscoveryDataInstance discoveryDataInstance, Boolean isCalledByWorkflow, TypeSpaceData typeSpaceData, DiscoveryDatabaseApi dbApi)
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithNoRetryUnauthorized(DiscoveryDatabaseApi dbApi, Boolean useProcessContext)
    at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.ProcessIncrementalDiscoveryData(DatabaseConnection databaseConnection)
    at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.DiscoveryPackageIncrementalProcessingHandler.Process()
    at Microsoft.EnterpriseManagement.Mom.DiscoveryDatabaseAccess.DiscoveryPackageProcessor.ProcessWithRetry(HandleProcessing handleProcessing, RetryPolicy retryPolicy)
    at Microsoft.EnterpriseManagement.ServiceDataLayer.DiscoveryDataManager.ProcessDiscoveryDataWithRetry(DatabaseConnection dbconnection, Guid discoverySourceId, IList`1 sdkEntityInstances, IDictionary`2 streams, IContext context)
    at Microsoft.EnterpriseManagement.ServiceDataLayer.ConnectorFrameworkConfigurationService.ProcessDiscoveryData(Guid discoverySourceId, IList`1 entityInstances, IDictionary`2 streams, ObjectChangelist`1 extensions)
    Source:DataAccessLayer
    Event ID: 33333
    Data:
    Data Access Layer rejected retry on SqlError:
    Request: ProcessRelationshipStagingForUpsert -- (TransactionId=732419), (DiscoverySourceId=eb496966-4fb7-45bd-bdda-b689af383733), (TimeGenerated=26/11/2014 9:31:53 PM), (PerformHealthServiceCheck=False), (HealthServiceId=), (RETURN_VALUE=1)
    Class: 16
    Number: 777980002
    Message: The specified relationship doesn't have a valid source.

  • Why can I not disable the guest user in the 10.8.2 update? I have never enabled the guest user, but after the update, it was automatically enabled with a "managed" tag. It is not selectable even after entering my admin password to unlock the options.

    Why can I not disable the guest user in the 10.8.2 update? I have never enabled the guest user, but after the update, it was automatically enabled with a "managed" tag. It is not selectable even after entering my admin password to unlock the options. I was able to select the account under "parental controls", but again, could not delete it. Why Apple? Why?!!????

    SOLVED Ok. I actually was able to disable it. I had to actually log in as the guest user to make it accessible in the preference window. Then I disabled it and logged out. Apologies if this was obvious for some people, but I have had some sort of issue with something every update since Snow Leopard.

  • Exclaimer manager signature does not update sent items for outlook 2013 clients when using cached mode

    Hi
    I have Signature Manager Exchange Edition 2.0.3.0 installed on the hub servers.
    I have enabled  Sent Items update.
    some clients are not getting signature update in the sent items of outlook while using cached mode.
    from OWA, and MS Outlook when connected online, the signature is updated in the sent items.
    I have two CAS servers and two mailbox servers. all with Exchange 2013 SP1
    I tested each CAS server for the URLs of Autodiscover and EWS, with no errors or warnings.
    I also test Autodiscover through
    https://testconnectivity.microsoft.com . I go successful result.
    Outlook clients are updated to the latest version 15.0.4701.1000
    for outlook clients; I deleted outlook profile, deleted outlook folder in the user profile, re-created the  outlook profile, with no luck.
    from Exclaimer event logs on the Hub servers. the sent items update is successfully updating clients. below is the screenshot of an event for one email message which is successfully updated from exclaimer but it did not update on the client outlook while
    using cached mode.
    Since the issue is with multiple users, I am searching for a centralized solution 
    Mashhour Faraj

    Dear Mashhour
    Here you go 
    Employees can see their email signatures and disclaimers
    With Exchange 2013, a Microsoft Outlook user can’t see any added email signatures or disclaimers as they are added to an email when it passes through the Exchange server.
    Signature Manager Exchange Edition lets email users see their email signature and corporate disclaimer within the Sent Items of their inbox, giving them visual confirmation of the processed email
    Source - 
    http://blog.exclaimer.com/exclaimer-signature-manager-vs-microsoft-exchange-2013/
    Updating to the latest version of signature manager exchange edition will help you to resolve this problem for sure 
    Or you need to contact them to find a solution on this .
    I'm pretty much sure that this problem is related with some version mismatch on their s/w on exchange 2013 which is causing this issue.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
    (MVP)

  • Activity stream in CC desktop manager is not updated

    Hello, the activity stream on the Home panel of the Adobe CC desktop manager is not updated. I'm logged, I sync, I reinstalled the Adobe CC manager. I use the same Adobe CC account on another MacBookPro OS X 10.10 and the activity stream in the Home panel is fine.
    MacBookAir OSX 10.10.1, Adobe CC (2014), no firewall

    I'm having the opposite problem.  All those listed in the screen shot as "Install" have been installed.
    Deleting OPM.db and downloading and installing CreativeCloudInstaller.dmg did not fix the issue.
    Do I really need to delete all of my installed apps and starting from scratch?
    david
    Apps are listed as "Install" when they've already been installed

  • Pfirewall.log file not updating

    Hi,
    I configured Windows Firewall to allow logging in my DC Firewall GPO.  settings are
    Log dropped Packets -enabled
    Log successfull connections -enabled
    Log file path and Name:
    %systemroot%\system32\logfiles\firewall\pfirewall.log
    size limit  32767
    The Pfirewall.log file is located in this area but is not updating itslef.   Is there something I need to do to enable the file to have an updated time stamp and overrwite itself after it reaches a certian size.   I changed the size limit from
    1024 to 32767 today but still does not seem to update itself. 
    My 2003 Domain's pfirewall.log IS updating and it is pointing to c:\windows directory.  Is there a service that needs NFTS permissions on the folder where the log file resides?  or a different GPO setting that handles this?
    Thanks,
    Kevin C.

    Hello Kevin,
    Please check this link.
    http://www.grouppolicy.biz/2010/07/how-to-manage-windows-firewall-settings-using-group-policy/
    Before exporting, go to the properties (check the last part of the link), where you see the logging option and configure your logging settings. Then import these settings in your GPO.

  • Fabric Manager SA not updating 3.3(1c)

    Fabric Manager SA not updating 3.3(1c). When I make zone changes or when a port goes down it won't update even after doing a rediscover or resync. Is this a bug in FM 3.3(1c)?

    When FM was installed, was the option to continuously monitor the fabric after is was discovered? Not sure if this is your issue.
    If you exit and then log back into FM after the change occurs, and is not observed, does the change show up? If the change is still not seen then I would suspect a bug and ask you to open a case with your MDS service provider. If the change is seen upon the new log in, then I would look into the option to 'monitor continuously'.
    Hope this helps,
    Mike

Maybe you are looking for