Distribution Failure

Why does my PDF form fail to distribute? PDF form loads
on-line at Acrobat.com, tracking displays my group list of email
addressees, however, forms are not being sent. I made the group
email batch in the only application that seems to to read by
acrobat professional: Apple Address Book. The list has 65 address
and are clearly displayed, but personal name information is not
display in the tracking window. Is this problem a result of glitch
on Acrobat.com, or is it a problem with the email input? too many
address? Thank you for anyone's help.

Can you please list the exact steps you are taking to e-mail
the form to your list of recipients?

Similar Messages

  • LMS 4.1 Patch Distribution Failure

    I didn't have this problem in 4.0, and I've tried to upgrade 2 different model routers (891 and 2811) with the same error, anyone know what this means? Google was no help.
    SWIM0151: The device is not running IOS Modular image in Install mode. Hence patch images cannot be distributed.
    Thanks,
    Craig

    It sounds like you're trying to use the Pathc Distribution workflow for non-modular devices.  Do not select Patch Distribution.  Instead, select Software Distribution, and then follow the specific flow you want from there.

  • Cache Distribution failure

    Hi all,
    What is the optimization features available in the Distribution Cache Mechanism.
    Currently Im running two clusters in 2 nodes and observed the performance is degrading when the clusters (from different nodes) are added.
    Can any one help me on this?

    Hi,
    Can you elaborate more on the issue? If you are adding more clusters to the same node, it is obvious that you are trying to squeeze more juice from the same hardware so it is expected.
    Cheers,
    _NJ                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Failure of a single article prevents the distribution of all articles in a publication to a subscriber

    We have a SQL Server 2012 R2 SP2 environment and Transactional Replication configured with 1 instance publishing all tables in a database via a single publication (circa 150 articles in the one publication). We have a separate distribution instance,
    and a third subscription instance. All articles in the publication are configured to copy all data, with no advanced filtering configured. It is also noted that Alerts were not configured in Replication Monitor.
    We had an issue whereby, inexplicably, a table on the subscriber vanished (I use this term because I could not find any record in the log file of a DELETE statement being issued against that table - regrettably I wasn't in the position to query the distribution
    database for any such commands either).
    In Replication monitor we saw that the article for the table in question was failing, but no others.
    The issue was that no other articles were being replicated to the subscriber, and this was evident via stalled rowcounts on the subscriber database, but increasing rowcounts on the publishing database.
    When we removed the offending article from the publication, all other articles started getting applied to the subscriber database - and we could observe both publication and subscription rowcounts increasing in lockstep.
    My questions are:
    1) in a single publication with many articles, are the articles applied to the subscription in a single batch - meaning that if a discreet transaction for one article fails, that all other articles will be rolled back with this transaction until it
    is cleared.
    2) Why would Replication Monitor not start showing widespread warnings for every other table (article) that was not successfully being replicated to the subscriber?
    3) Aside from configuring alerts in Replication Monitor (which has happened already) and a bespoke rowcount checking 'monitor', how could Transactional Replication be configured so that the failure of the publication of an obscure article doesn't fail all
    articles --> I note that creating multiple publications with smaller number of articles would limit the exposure, but from what I've observed, this would only limit the exposure to those articles in the same publication.
    Many thnaks

    1) they could be - it all depends on the batch size.
    2) I suspect because the distribution agent applies the changes serially, ie one article after another in the order the changes occurred on the publisher. So if it fails on one table it will not continue until this error is leared.
    3) use the continue on data consistency error profile, or put your problem article in its own publication.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Viewer Builder signing failure for distribution viewer

    I'm having the following problem:
    I"m able to download the developer ipa from Viewer Builder with no problems, but when I try to download the distribution build, I get a VB error, "signing failure."
    this indicates to me that there is a problem perhaps with my p12 and mobile provisioning profile, but I've done all that correctly, as far as I know, and tried multiple times to reproduce from Apple's provisioning portal, but nothing works.
    is anyone else having this problem?

    Yes, I've been having this issue since last Friday. But, my ipa isn't working either....

  • SRM 7.0 Central Contract- Distribution to backend failure

    Hello experts,
    We are implementing SRM 7.0 Central contracts scenario with PI.
    The Contracts get created and Released but the problem is that the Distribution to backend fails. The Status in BBP_PD shows 'Distribution Incorrect' and the RZ20 gives an error 'Backend data cannot be read'.
    We checked all the configuration settings (including the PI settings) and everything seems to be in order.
    Would appreciate if someone could throw some light on the potential cause of the problem.
    Thanks
    Raman.

    Message must have created . check all SRM outbound transactions .but PI could not catch them.
    Note 1284369 - User attributes check in Contract distribution via services - what is your SP level in SRM 700.
    The sap stratergy in earlier version
    table in ECC BBPD_CTR_IDOCREF with message 019-This will result in setting the GOA status to 'Distribution Incorrect'.
    so SAP might have tried the same way in CCTR as well, Once message are created and this message number like IDOC number updated in ECC table for the further refrence .so like wise SRM trying to communicate the same to ECC but it would have failed.
    do you remeber when GOA idoc fails this table we will have reference number and reprocessing idoc.
    like any reference of your input must register in one ECC table but there may have this table or some other reference table.
    /SAPSRM/CL_CH_SOA_MAP_CTR_OUT  CLASS DO SOME trick and see what is happening here
    Muthu

  • Distribution Status Failure

    When I open the SCCM 2012 R2 Admin Console and browse to
    Monitoring | Overview | Distribution Status | Distribution Configuration Status
    , all the DPs are banged.  The MP is fine.
    When I look at the associated asset messages, each of them says...
    Upon review of that DP's smsdpmon.log file, the only thing I see wrong is...
    I log onto the MP server and launch Powershell.  I then run the following query.
    Get-WmiObject -ComputerName SRVCRPNAME -Namespace root\sccmdp -Query "select * from SMS_PackagesInContLib" | select PackageID
    Sure enough, TEI007C is in WMI but when I look in the DP’s SCCMContentLib\PkgLib folder, the matching INI file is nowhere to be found.
    I can’t find TEI0007C anywhere in SCCM so there’s no way I can redistribute that package to resolve this issue.  It looks to me like it’s just stuck in WMI but isn’t supposed to be.
    Any ideas on what I should do next?
    BTW, we’ve performed the following upgrades about a month ago.  I’m only now becoming aware of this problem as I just found this view in SCCM Console.  I might have been this way for a while I wouldn’t have known it because I'm very new to System
    Center as a whole.
    SCCM 2012 SP1 upgraded to R2
    MDT upgraded to MDT 2013
    AEK upgraded to 8.1
    Thank you for any assistance you can offer.
    Geoff Crookshanks

    Have a look Pls
    http://blogs.technet.com/b/configmgrteam/archive/2012/05/07/troubleshooting-content-mismatch-warnings-on-a-distribution-point-in-system-center-2012-configuration-manager.aspx
    http://scug.be/sccm/2013/12/12/system-center-2012-configuration-manager-troubleshooting-and-resolving-content-mismatch-warnings-on-a-distribution-point-with-powershell/
    Thanks, Prabha G

  • SCCM Distribution Point Failures

    I have 16 DP's in Config manager all were working last week. Now only 2 are allowing content. The error message states:
    Possible cause: Distribution Manager does not have sufficient rights to the computer.
    Solution: Verify that the site server computer account is an admin on the distribution point computer.
    I have done all this. As I stated they were all working last week No permission changes have been made. I am stumped.
    J. Mink

    Please add details about the issue. Are you talking about distributing content to DPs? Or that clients cannot download content? 
    Also the log above does not look like it's distmgr.log. "DISM" in distmgr.log does not look familiar to me. Please add some more lines. 
    Torsten Meringer | http://www.mssccmfaq.de

  • Failure when adding recipients to distribution list in so23

    Hi,
    I am using so23 for adding recipients in distribution lists.
    I am editing the distribution list in transaction so23, "Change Shared Distribution List".
    Than, in the tab Distr. list content I am adding the recipient.
    For example I am adding new recipient:
    In the column recipient I am typing the mail address and choosing
    in recip. type U Internet Address.
    When I am saving the list the recipt. type is changing to "via Internet"
    and then I have problems in my code because the Recip. type is not U.
    In addition, when typing logon name like johns and choosing B. SAP Logon
    Name the recipient is changed to "John Smith" and the recip. type is deleted.
    I searched a few notes and read that maybe the mail address is wrong, but the mail address is fine (as I wrote before).
    Thanks,
    Ofir

    Hi,
    This is not expected behaviour.
    My questions :
    1) Are any of users successfully login to OBIEE. If so caputure their roles and groups from " My account " and  paste it here.
    2) Make sure you give following privilages to your groups and application roles [from the point 1]
    User Population - Can List Users
    javascript:void(null)
    User Population - Can List Groups
    javascript:void(null)       
    User Population - Can List Application Roles
    Seeing all the  LDAP users in the Weblogic admin console is Ok. But you have to see under what group and applicaiton role they are logging into OBIEE.
    Thanks
    Venkat
    http://obieedeveloper.blogspot.com/

  • Distribution Point install failure

    Hi all,
    In all our company uses 8 distribution point and the majority are 2008 R2 domain controllers.
    About two days ago I have done an inplace upgrade on one server to 2012 R2.
    The upgrade went mostly without a hitch except for the SCCM DP.
    The error that I was getting was "access denied" or something along those lines when the site server was attempting to distribute content.
    So I have tried a lot of things so far to the point where I decided to remove the distribution point and start over. No Joy...
    I am getting an error on the distribution point in the SCCM console stating "Failed to verify the disk drive". when looking further into the distmgr.log, nothing makes sense to me. please see the below log.
    ~Sleep 60 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:35.310-600><thread=5576 (0x15C8)>
    ~Sleep 60 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:44.178-600><thread=5576 (0x15C8)>
    Upgrading DP with ID 18. Thread 0x1e1c. Used 1 threads out of 5.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.248-600><thread=5868 (0x16EC)>
    ~Processing 18.INS  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.253-600><thread=7708 (0x1E1C)>
    ~DPID 18 - NAL Path ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ , ServerName = [SERVER NAME HERE], DPDrive = E:, IsMulticast = 0, PXE = 0, RemoveWDS = 0  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014
    22:20:59.263-600><thread=7708 (0x1E1C)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.255-600><thread=5868 (0x16EC)>
    ~Created policy provider trigger for ID 18  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.308-600><thread=5860 (0x16E4)>
    DPConnection::Connect: For [SERVER NAME HERE], logged-on as rondo\sccmpush~  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:02.712-600><thread=7708 (0x1E1C)>
    Found notification for package 'RDO00002'  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.263-600><thread=5576 (0x15C8)>
    Found notification for package 'RDO00003'  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.268-600><thread=5576 (0x15C8)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.302-600><thread=5868 (0x16EC)>
    ~Package Thread Limit: 3  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.310-600><thread=5576 (0x15C8)>
    ~Per package Thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.315-600><thread=5576 (0x15C8)>
    ~Retry interval: 30  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.320-600><thread=5576 (0x15C8)>
    ~DP upgrade thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.325-600><thread=5576 (0x15C8)>
    ~DP upgrade retry interval: 20  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.330-600><thread=5576 (0x15C8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.360-600><thread=5576 (0x15C8)>
    Failed to find a valid drive on the distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.541-600><thread=7708 (0x1E1C)>
    ~Starting package processing thread, thread ID = 0x88 (136)  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.919-600><thread=5576 (0x15C8)>
    DPConnection::Disconnect: For [SERVER NAME HERE], reverted to SYSTEM context~  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.131-600><thread=7708 (0x1E1C)>
    user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine ([SITE SERVER NAME HERE]) is submitting SDK changes from site(RDO)  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.348-600><thread=7708 (0x1E1C)>
    ~Starting package processing thread, thread ID = 0x2B78 (11128)  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.426-600><thread=5576 (0x15C8)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.434-600><thread=5576 (0x15C8)>
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=11128
    (0x2B78)>
    ~Retrying package RDO00003  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.450-600><thread=11128 (0x2B78)>
    No action specified for the package RDO00003.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=11128 (0x2B78)>
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00002" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=136
    (0x88)>
    ~Retrying package RDO00002  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.469-600><thread=136 (0x88)>
    No action specified for the package RDO00002.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.476-600><thread=136 (0x88)>
    Start adding package to server ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.494-600><thread=136 (0x88)>
    Will wait for 1 threads to end.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=136 (0x88)>
    Thread Handle = 00000000000035C0  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.507-600><thread=136 (0x88)>
    Start adding package to server ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.473-600><thread=11128 (0x2B78)>
    Attempting to add or update a package on a distribution point.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=9852 (0x267C)>
    The distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ is not installed or upgraded yet.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.538-600><thread=9852 (0x267C)>
    Error occurred. Performing error cleanup prior to returning.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.546-600><thread=9852 (0x267C)>
    ~Failed to install DP files on the remote DP. Error code = 15  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=7708 (0x1E1C)>
    ~Drive E: is not valid. Error = 15  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.566-600><thread=7708 (0x1E1C)>
    STATMSG: ID=2360 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=7708 GMTDATE=Thu May 01 12:21:05.573 2014 ISTR0="["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER
    NAME HERE]\" ISTR1="[SERVER NAME HERE]" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\[SERVER
    NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.573-600><thread=7708 (0x1E1C)>
    ~Will try again after 20 mins ...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.582-600><thread=7708 (0x1E1C)>
    Will wait for 1 threads to end.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=11128 (0x2B78)>
    Thread Handle = 00000000000029C8  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.612-600><thread=11128 (0x2B78)>
    Attempting to add or update a package on a distribution point.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=10028 (0x272C)>
    DP thread with array index 0 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.124-600><thread=136 (0x88)>
    DP thread with thread handle 00000000000035C0 and thread ID 9852 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.131-600><thread=136 (0x88)>
    The distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ is not installed or upgraded yet.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.136-600><thread=10028 (0x272C)>
    Error occurred. Performing error cleanup prior to returning.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.164-600><thread=10028 (0x272C)>
    DP thread with array index 0 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.198-600><thread=11128 (0x2B78)>
    DP thread with thread handle 00000000000029C8 and thread ID 10028 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.205-600><thread=11128 (0x2B78)>
    ~Package RDO00002 does not have a preferred sender.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.645-600><thread=136 (0x88)>
    The package and/or program properties for package RDO00002 have not changed,  need to determine which site(s) need updated package info.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.653-600><thread=136 (0x88)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00002, Version=3, Status=2301  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.659-600><thread=136 (0x88)>
    ~StoredPkgVersion (3) of package RDO00002. StoredPkgVersion in database is 3.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.687-600><thread=136 (0x88)>
    ~SourceVersion (3) of package RDO00002. SourceVersion in database is 3.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.694-600><thread=136 (0x88)>
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:06.700 2014 ISTR0="Configuration Manager Client Package" ISTR1="RDO00002"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.700-600><thread=136
    (0x88)>
    ~Failed to process package RDO00002 after 33 retries, will retry 67 more times  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.711-600><thread=136 (0x88)>
    ~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.720-600><thread=136 (0x88)>
    ~Package RDO00003 does not have a preferred sender.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.721-600><thread=11128 (0x2B78)>
    The package and/or program properties for package RDO00003 have not changed,  need to determine which site(s) need updated package info.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.749-600><thread=11128 (0x2B78)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00003, Version=1, Status=2301  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.757-600><thread=11128 (0x2B78)>
    ~StoredPkgVersion (1) of package RDO00003. StoredPkgVersion in database is 1.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.784-600><thread=11128 (0x2B78)>
    ~SourceVersion (1) of package RDO00003. SourceVersion in database is 1.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.790-600><thread=11128 (0x2B78)>
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:06.797 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="RDO00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014
    22:21:06.797-600><thread=11128 (0x2B78)>
    ~Failed to process package RDO00003 after 33 retries, will retry 67 more times  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.806-600><thread=11128 (0x2B78)>
    ~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.814-600><thread=11128 (0x2B78)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:09.311-600><thread=5868 (0x16EC)>
    ~Package Thread Limit: 3  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.463-600><thread=5576 (0x15C8)>
    ~Per package Thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.469-600><thread=5576 (0x15C8)>
    ~Retry interval: 30  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.476-600><thread=5576 (0x15C8)>
    ~DP upgrade thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.482-600><thread=5576 (0x15C8)>
    ~DP upgrade retry interval: 20  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.488-600><thread=5576 (0x15C8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.509-600><thread=5576 (0x15C8)>
    ~Sleep 1826 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.517-600><thread=5576 (0x15C8)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:14.320-600><thread=5868 (0x16EC)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.544-600><thread=5576 (0x15C8)>
    ~Sleep 1821 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.553-600><thread=5576 (0x15C8)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:19.332-600><thread=5868 (0x16EC)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.581-600><thread=5576 (0x15C8)>
    ~Sleep 1816 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.589-600><thread=5576 (0x15C8)>
    ~Sleep 1816 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.732-600><thread=5576 (0x15C8)>
    ~Sleep 1816 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.872-600><thread=5576 (0x15C8)>
    So I have two questions,
    How can I fix this and how do I prevent it from happening to the remainder?
    Thank you all in advance.
    Daniel.

    The server does not appear at all
    You really need to give more information so we can help you.
    What about the logs, are you getting the same errors after making all the changes? please upload the full log to SkyDrive or any other place. 
    Did you reboot this DP\DC?
    Can you successfully ping from the primary to DP and back?
    Do you have access from primary to C$ on that DP?
    What account did you choose for installation?
    Did you choose to install IIS?
    If IIS was installed, try to remove it and let DP installation install it automatically.
    Confirm that PowerShell 3.0 is installed.
    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.
    Hi Idan,
    I will go through and reply to each of the suggestions you have made below;
    1. The log that was attached was the full log. I cleared the log prior to setting up the DP and copied the contents into this forum after it has stopped.
    2. Yes I had rebooted, Many times.
    3. Yes I can successfully ping either way.
    4. Yes I can access the C$ share on the DP from the Primary
    5. I have tried both the PC account and a service account that is part of the domain admins group and also added to the local admins via a net command
    6. Yes I did choose to install IIS and I had already tried uninstalling IIS and running the install again.
    7. as above
    8. Yes Powershell 3.0 is installed
    PS C:\Users\admindg> $PSVersionTable
    Name                           Value
    PSVersion                      4.0
    WSManStackVersion              3.0
    SerializationVersion           1.1.0.1
    CLRVersion                     4.0.30319.34014
    BuildVersion                   6.3.9600.16394
    PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}
    PSRemotingProtocolVersion      2.2
    Thank you for all your suggestions and I hope that the information that I have provided is sufficient to draw a better picture of our environment.
    Regards,
    Daniel

  • Changing the automatic Distribution Rule from Per to Full

    Hello SAPians,
    I have a scenario where the Customer is maintaining the Moving Average Price (I know this is not SAP suggested, I am in the process of convincing to move from moving avg to Std) for the Semi-finished goods and finished goods.
    It is Product Cost by Order scenario where Process Orders are using and the settlement rule to the Material and distribution rule is "Per" (Periodic). The main reason Customer had this Per was they would not be able to settle the Order once they settle it in full.
    But due to increased issues in month end atctivities due to thie 'Per' settlement (settlement of Process Orders not settling properly in the last month due to the failure of Batch jobs and other reasons). I want to suggest them to use Distribution Rule 'Full' instead of 'Per' because of the following advantages considering the above scenario.
    1. The 'Full' settlement can be settled if the Order is not in Teco or closed status any number of times as long as there is the Variance sitting on the Order.
    2. The 'Full' Distribution rule will not create issue if the variance is sitting on the Order in the closed period because when you do the settlement in the next period, system will allocate the variances from the last period to the Material Receiver in the current Period(I have not yet tested this scenario) and has not been. (Yeah I know there will be issue if the Material has been moved out of inventory before the settlement happens, they have another set up to update the Material prices manually by keeping the track of cost of Material).
    3. So the config change will be the Product cost by Order -> Manufacturing Order-> Define Cost-Accounting-Relevant Default Values for Order Typ --> change the Default rule from PP1 to PP2 'Process orders (periodic settlement)'
    Please let me know if what I am thinking is wrong based on this sceanrio and also please give me some more insight if I am missing any points.
    Thank you very much for your time!
    -Harter.

    Hi Balaji/Ajay,
    Could you please help me in understanding the effect of Variances if I change the Order type to FULL in this scenario (Moving Average price for Finished good Material)?
    I checked the configuration and the Variance is only Total Variance that is settling to FI and COPA.
    Also client is more concentrated on Variance accumulated per year and not per month.
    Let's say I have Order in Period 9 where the actual debits on the Order are $1000 and actual credits are $1200 where balance (variance) is $200 and suppose I missed the Period 9 settlement and I want to settle this Order in Period 10 where I had $100 variance in that Period 10
    Period         Variance on Order                Status
    9              $200                   missed
    10              $100                   not yet
    So now when I settle the Order in period 10 (with FULL as settlement type), it settles $300 instead of $100 variance. So if this is the case, if I look at the Variance data, yes the variance data is wrong but if I look at yearly perspective, it looks right but I think I am missing something here, right?
    Also what happens if the Order is open more than one year and the same scenario happens, the Variance will be posted to new year which is again issue, right?
    Am I in the right direction?
    Please advice.
    Thank you,
    -Harter.

  • Error during distribution for compiled code generation-Reply

    Hi,
    Looking at your error messages, it looks as though your build is failing during the code generation phase of an autocompilation. To determine why the code generator crashed, either look in the $FORTE_ROOT/log/forte_ex*.log files or don't use autocompilation and use fcompile.
    There are many reasons why the code generator could crash. Some of the things I've come across are running out of memory and trying to find invalid classes.
    If its the invalid class problem you'll find a message like:
    Generating code for partition BLTCustomWindow_cl0_Part1.
    ERROR: Exiting due to following exception:
    SYSTEM ERROR: Client partition FTCompile_cl0_Client was terminated by escaped
    exception. See the remainder of the error stack for more information.
    Class: qqsp_ResourceException
    Error #: [1001, 3]
    Detected at: qqrt_ForteExecAgent::LoadPartition at 1
    Error Time: Tue Aug 18 17:52:44
    Exception occurred (locally) on partition "Forte_Executor", (partitionId =
    9EA25A00-36FE-11D2-87C4-502F15BEAA77:0x1, taskId =
    [9EA25A00-36FE-11D2-87C4-502F15BEAA77:0x1.6]) in application
    "FTCompile_cl0", pid 28331 on node stardev in environment <unknown>.
    FATAL ERROR: Invalid class ProductBMServices.ProductSecurityMgrProxy
    (0x4ecd,0x19a)
    Class: qqsp_ImplementationException
    Detected at: qqcg_TRclass::SetClass at 2
    Last TOOL statement: method ForteCompiler.ProcessPGF
    Error Time: Tue Aug 18 17:52:44
    Exception occurred (locally) on partition "Forte_Executor",
    (partitionId = 9EA25A00-36FE-11D2-87C4-502F15BEAA77:0x1, taskId =
    [9EA25A00-36FE-11D2-87C4-502F15BEAA77:0x1.6]) in application
    "FTCompile_cl0", pid 28331 on node stardev in environment <unknown>.
    The solution for this instance is to clean up the invalid classes using the c4tstdrv utility.
    c4tstdrv > setrepos star8
    c4tstdrv > setwork dmcompiledbuild
    c4tstdrv > open
    Type Service Flags Level
    err sh * 255
    trc rp 1 4
    c4tstdrv > findproj productbmservices
    c4tstdrv > cleanuprtclasses
    Removing extraneous RTclass ProductShootingLocationMgrProxy
    Removing extraneous RTclass PRTerritoryBaseMgrProxy
    Removing extraneous RTclass PRTerritoryMgrProxy
    Removing extraneous RTclass TalentBaseMgrProxy
    Removing extraneous RTclass TalentTypeMgrProxy
    Removing extraneous RTclass TitleTypeBaseMgrProxy
    Removing extraneous RTclass TitleTypeMgrProxy
    Removing extraneous RTclass ProductSecurityBaseClass
    Removing extraneous RTclass ProductSecurityBaseQuery
    Removing extraneous RTclass ProductSecurityQuery
    Removing extraneous RTclass ProductSecurityMgrProxy
    c4tstdrv > commit
    c4tstdrv > exit
    Integrate the changes to the workspace, start the build again and this should have cured the problem.
    However, its hard to know what the cause of your problem is without seeing the output in the log files.
    Good luck.
    Mark Carruthers
    20th Century Fox
    "Forte Consultants" <[email protected]> 01/22/99 08:35am >>>
    Hi,
    I'm doing application distribution for my application using a fscript
    script and am forcing compilation on 2 of my partitions.
    This I have been doing from quite sometime successfully. Recently I
    developed a new service and plugged it into my application for
    deployment.
    I'm successfully able to distribute & deploy the interpreted code. But
    I'm getting a long list of system errors when I try doing distribution
    for compiled code. And I see only one of the .exe generated instead of
    two because of which I'm unable to go ahead with installaion. I would
    appreciate if anybody let me know why this's happening ?. The following
    is the main chunk of this error list.
    Thanks in advance.
    --Anand Ramaswamy
    SYSTEM ERROR: Cannot resolve the distributed reference for an object of
    class
    (qqlo_Object) named (<Unknown>) for the reasons below.
    Class: qqsp_DistAccessException
    Error #: [601, 144]
    Detected at: qqdo_ProxyMgr::ResolveOutGoingProxy at 10
    Error Time: Fri Jan 22 10:44:22
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: Can not initially communicate with the object named
    (Unnamed),
    which is supposed to be in partition
    (32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x616:0x1).
    Class: qqsp_DistAccessException
    Error #: [601, 140]
    Detected at: qqdo_ProxyMgr::CheckAccess at 1
    Error Time: Fri Jan 22 10:44:22
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: Attempt to send to unknown destination partition
    (32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x616:0x1).
    Class: qqsp_DistAccessException
    Error #: [601, 102]
    Detected at: qqdo_PartitionMgr::SendMsg at 1
    Error Time: Fri Jan 22 10:44:22
    Distributed method called: qqdo_InternalMessage.<Message> (object
    name
    Unnamed) from partition "CodeGenerationSvc_cl0_Part1-router",
    (partitionId
    = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615.2]) in application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: Partition (32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x616:0x1)
    no
    longer exists. The process associated with the partition probably
    terminated.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::CheckStarted at 1
    Error Time: Fri Jan 22 10:44:22
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: This method invocation is being retried because the
    failures
    shown below and the fact that the dialog duration is MESSAGE. This is
    try #2.
    Class: qqsp_DistAccessException
    Error #: [601, 54]
    Detected at: qqdo_Message::Failed at 1
    Error Time: Fri Jan 22 10:44:19
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: The load balanced router is disabled or has no members.
    This
    can happen if all of the members terminated or failed.
    Class: qqsp_DistAccessException
    Error #: [601, 161]
    Detected at: qqdo_LbRouter::Route at 1
    Error Time: Fri Jan 22 10:44:19
    Distributed method called: GenerationMgrProxy.GeneratePartitionCode
    (object name
    site/codegenerationsvc_cl0/codegenerationsvc_cl0-codegensvc)
    from partition "Fscript_cl9_Client", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614.2]) in application
    "fscript",
    pid 4b81 on node MOOSUP in environment IGTSDENV
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    SYSTEM ERROR: This method invocation is being retried because the
    failures
    shown below and the fact that the dialog duration is MESSAGE. This is
    try #1.
    Class: qqsp_DistAccessException
    Error #: [601, 54]
    Detected at: qqdo_Message::Failed at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (locally) on partition "Fscript_cl9_Client",
    (partitionId = 32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1,
    taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.1]) in application
    "fscript", pid 4b81 on node MOOSUP in environment IGTSDENV.
    SYSTEM ERROR: Access to a load balanced router member (which is a
    service
    object) failed for the reasons below.
    Class: qqsp_DistAccessException
    Error #: [601, 162]
    Detected at: qqdo_LbRouter::Route at 2
    Error Time: Fri Jan 22 10:44:15
    Distributed method called: GenerationMgrProxy.GeneratePartitionCode
    (object name
    site/codegenerationsvc_cl0/codegenerationsvc_cl0-codegensvc)
    from partition "Fscript_cl9_Client", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614.3]) in application
    "fscript",
    pid 4b81 on node MOOSUP in environment IGTSDENV
    Distributed method called: qqlo_Object.<Message> (object name
    Unnamed)
    from partition "Forte_Executor", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615.12]) in application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    SYSTEM ERROR: Cannot resolve the distributed reference for an object of
    class
    (qqlo_Object) named (<Unknown>) for the reasons below.
    Class: qqsp_DistAccessException
    Error #: [601, 144]
    Detected at: qqdo_ProxyMgr::ResolveOutGoingProxy at 10
    Error Time: Fri Jan 22 10:44:15
    Distributed method called: qqlo_Object.<Message> (object name
    Unnamed)
    from partition "Forte_Executor", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615.12]) in application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    SYSTEM ERROR: This distributed reference was previously invalidated due
    to the
    reasons below.
    Class: qqsp_DistAccessException
    Error #: [601, 132]
    Detected at: qqdo_ProxyMgr::ResolveOutGoingProxy at 3
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: Network partner closed connection. This usually means the
    process at the other end of the wire failed. Please go look there and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: Asynchronous Failure: Recieved a close from the network
    partner:
    Internet Location - Host: moosup.iroquois.com Port Number: 2504 Dot:
    193.1.11.26 %LINKDISCON, network partner disconnected logical link
    Event 4
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    SYSTEM ERROR: This method invocation is being retried because the
    failures
    shown below and the fact that the dialog duration is MESSAGE. This is
    try #1.
    Class: qqsp_DistAccessException
    Error #: [601, 54]
    Detected at: qqdo_Message::Failed at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Fri Jan 22 10:44:15
    Distributed method called: qqlo_Object.<Message> (object name
    Unnamed)
    from partition "Forte_Executor", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615.12]) in application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: Network partner closed connection. This usually means the
    process at the other end of the wire failed. Please go look there and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    INFORMATION: Asynchronous Failure: Recieved a close from the network
    partner:
    Internet Location - Host: moosup.iroquois.com Port Number: 2504 Dot:
    193.1.11.26 %LINKDISCON, network partner disconnected logical link
    Event 4
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Fri Jan 22 10:44:15
    Exception occurred (remotely) on partition
    "CodeGenerationSvc_cl0_Part1-router", (partitionId =
    32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x615:0x1, taskId =
    [32271CD0-4E62-11D2-AF29-9F40A9E1AA77:0x614:0x1.10]) in
    application
    "CodeGenerationSvc_cl0", pid 7487 on node MOOSUP in environment
    IGTSDENV.
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi,
    If this INCLUDE is in a function group go the MAIN program and activate from there.
    Can you list out the include name?
    a®

  • No data in Application failure Analysis report for a particular application alone.

    Dear All, 
    We are not able to get the data in Application Failure Analysis report from Appadvisor for a particular application(say ABC) alone, whereas it works fine for different application. Also,we could get the data from other reports(such
    as Application status,Problem distribution analysis,etc) for the same application(ABC). PFB snapshot for your reference.
    Thanks in Advance.
    Regards,
    Rajesh Kumar C

    Hi,
    Is there any error message when you run Application Failure Analysis report for the specific application?
    Does this application have any failure alerts?
    You may also look into operation manager even logs to check is there any errors or warnings.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Group Policy processing failure on 2008 when MIX Domain 2003 with DC 2008

    Dear I try to add additional Windows 2008 Domain to My Domain controller 2003  and I ma Receiving Group policy error in DC 2008  With Event ID 1055
    The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
    a) Name Resolution failure on the current domain controller. 
    b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" /> 
      <EventID>1055</EventID> 
      <Version>0</Version> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Opcode>1</Opcode> 
      <Keywords>0x8000000000000000</Keywords> 
      <TimeCreated SystemTime="2014-03-06T14:36:44.411955300Z" /> 
      <EventRecordID>3859</EventRecordID> 
      <Correlation ActivityID="{28DAD258-26D0-4C1E-A4B7-F37DEE04C8F1}" /> 
      <Execution ProcessID="952" ThreadID="3276" /> 
      <Channel>System</Channel> 
      <Computer>PRIMARYDC.Qtit.com</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="SupportInfo1">1</Data> 
      <Data Name="SupportInfo2">1632</Data> 
      <Data Name="ProcessingMode">0</Data> 
      <Data Name="ProcessingTimeInMilliseconds">1578</Data> 
      <Data Name="ErrorCode">5</Data> 
      <Data Name="ErrorDescription">Access is denied.</Data> 
      </EventData>
      </Event>
    I install See KB939820 for a hotfix applicable to Microsoft DC 2003 regrading to he KRBTGT account 
    Refer Url : http://support.microsoft.com/kb/939820 
    I run dcdiag /v on  and repadmin /showrepl at DC 2008
    the dcdiag /v result
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       * Verifying that the local machine PRIMARYDC, is a Directory Server. 
       Home Server = PRIMARYDC
       * Connecting to directory service on server PRIMARYDC.
       * Identified AD Forest. 
       Collecting AD specific global data 
       * Collecting site info.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Qtit,DC=com,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
       The previous call succeeded 
       Iterating through the sites 
       Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
       Getting ISTG and options for the site
       * Identifying all servers.
       Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=Qtit,DC=com,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
       The previous call succeeded....
       The previous call succeeded
       Iterating through the list of servers 
       Getting information for the server CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com 
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       Getting information for the server CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com 
       objectGuid obtained
       InvocationID obtained
       dnsHostname obtained
       site info obtained
       All the info for the server collected
       * Identifying all NC cross-refs.
       * Found 2 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\PRIMARYDC
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             Determining IP4 connectivity 
             * Active Directory RPC Services Check
             ......................... PRIMARYDC passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\PRIMARYDC
          Starting test: Advertising
             The DC PRIMARYDC is advertising itself as a DC and having a DS.
             The DC PRIMARYDC is advertising as an LDAP server
             The DC PRIMARYDC is advertising as having a writeable directory
             The DC PRIMARYDC is advertising as a Key Distribution Center
             The DC PRIMARYDC is advertising as a time server
             The DS PRIMARYDC is advertising as a GC.
             ......................... PRIMARYDC passed test Advertising
          Test omitted by user request: CheckSecurityError
          Test omitted by user request: CutoffServers
          Starting test: FrsEvent
             * The File Replication Service Event log test 
             There are warning or error events within the last 24 hours after the
             SYSVOL has been shared.  Failing SYSVOL replication problems may cause
             Group Policy problems. 
             A warning event occurred.  EventID: 0x800034C8
                Time Generated: 03/06/2014   10:18:56
                Event String:
                The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer PRIMARYDC. The File Replication Service might not recover when power to
    the drive is interrupted and critical updates are lost.
             A warning event occurred.  EventID: 0x800034C8
                Time Generated: 03/06/2014   10:53:21
                Event String:
                The File Replication Service has detected an enabled disk write cache on the drive containing the directory c:\windows\ntfrs\jet on the computer PRIMARYDC. The File Replication Service might not recover when power to
    the drive is interrupted and critical updates are lost.
             ......................... PRIMARYDC passed test FrsEvent
          Starting test: DFSREvent
             The DFS Replication Event Log. 
             Skip the test because the server is running FRS.
             ......................... PRIMARYDC passed test DFSREvent
          Starting test: SysVolCheck
             * The File Replication Service SYSVOL ready test 
             File Replication Service's SYSVOL is ready 
             ......................... PRIMARYDC passed test SysVolCheck
          Starting test: KccEvent
             * The KCC Event log test
             Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
             ......................... PRIMARYDC passed test KccEvent
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Domain Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role PDC Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Rid Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=SECONDAD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             ......................... PRIMARYDC passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             Checking machine account for DC PRIMARYDC on DC PRIMARYDC.
             * SPN found :LDAP/PRIMARYDC.Qtit.com/Qtit.com
             * SPN found :LDAP/PRIMARYDC.Qtit.com
             * SPN found :LDAP/PRIMARYDC
             * SPN found :LDAP/PRIMARYDC.Qtit.com/QTIT
             * SPN found :LDAP/e3d8c76c-1b59-4de6-9f7f-c438df9a2863._msdcs.Qtit.com
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/e3d8c76c-1b59-4de6-9f7f-c438df9a2863/Qtit.com
             * SPN found :HOST/PRIMARYDC.Qtit.com/Qtit.com
             * SPN found :HOST/PRIMARYDC.Qtit.com
             * SPN found :HOST/PRIMARYDC
             * SPN found :HOST/PRIMARYDC.Qtit.com/QTIT
             * SPN found :GC/PRIMARYDC.Qtit.com/Qtit.com
             ......................... PRIMARYDC passed test MachineAccount
          Starting test: NCSecDesc
             * Security Permissions check for all NC's on DC PRIMARYDC.
             The forest is not ready for RODC. Will skip checking ERODC ACEs.
             * Security Permissions Check for
               DC=ForestDnsZones,DC=Qtit,DC=com
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=ForestDnsZones,DC=Qtit,DC=com
             * Security Permissions Check for
               DC=DomainDnsZones,DC=Qtit,DC=com
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=DomainDnsZones,DC=Qtit,DC=com
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=Qtit,DC=com
                (Schema,Version 3)
             * Security Permissions Check for
               CN=Configuration,DC=Qtit,DC=com
                (Configuration,Version 3)
             * Security Permissions Check for
               DC=Qtit,DC=com
                (Domain,Version 3)
             ......................... PRIMARYDC failed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             Verified share \\PRIMARYDC\netlogon
             Verified share \\PRIMARYDC\sysvol
             ......................... PRIMARYDC passed test NetLogons
          Starting test: ObjectsReplicated
             PRIMARYDC is in domain DC=Qtit,DC=com
             Checking for CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com in domain DC=Qtit,DC=com on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com in domain CN=Configuration,DC=Qtit,DC=com on 1 servers
                Object is up-to-date on all servers.
             ......................... PRIMARYDC passed test ObjectsReplicated
          Test omitted by user request: OutboundSecureChannels
          Starting test: Replications
             * Replications Check
             * Replication Latency Check
                DC=ForestDnsZones,DC=Qtit,DC=com
                   Latency information for 18 entries in the vector were ignored.
                      18 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                DC=DomainDnsZones,DC=Qtit,DC=com
                   Latency information for 18 entries in the vector were ignored.
                      18 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                CN=Schema,CN=Configuration,DC=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                CN=Configuration,DC=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
                DC=Qtit,DC=com
                   Latency information for 20 entries in the vector were ignored.
                      20 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
             * Replication Site Latency Check 
             ......................... PRIMARYDC passed test Replications
          Starting test: RidManager
             * Available RID Pool for the Domain is 14607 to 1073741823
             * SecondAD.Qtit.com is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 14107 to 14606
             * rIDPreviousAllocationPool is 14107 to 14606
             * rIDNextRID: 14124
             ......................... PRIMARYDC passed test RidManager
          Starting test: Services
             * Checking Service: EventSystem
             * Checking Service: RpcSs
             * Checking Service: NTDS
             * Checking Service: DnsCache
             * Checking Service: NtFrs
             * Checking Service: IsmServ
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... PRIMARYDC passed test Services
          Starting test: SystemLog
             * The System Event log test
             A warning event occurred.  EventID: 0x0000A001
                Time Generated: 03/06/2014   16:04:05
                Event String:
                The Security System could not establish a secured connection with the server ldap/PRIMARYDC.Qtit.com/[email protected]. No authentication protocol was available.
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:06:35
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:11:36
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:16:38
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:21:39
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:26:41
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:46
                Event String:
                Driver TOSHIBA e-STUDIO16/20/25 PCL 6 required for printer TOSHIBA e-STUDIO16/20/25 PCL 6 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:48
                Event String:
                Driver Microsoft XPS Document Writer v4 required for printer Microsoft XPS Document Writer is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:30:49
                Event String:
                Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:14
                Event String:
                Driver Send to Microsoft OneNote 15 Driver required for printer Send To OneNote 2013 is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:16
                Event String:
                Driver Microsoft XPS Document Writer v4 required for printer Microsoft XPS Document Writer is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x00000457
                Time Generated: 03/06/2014   16:31:16
                Event String:
                Driver WebEx Document Loader required for printer WebEx Document Loader is unknown. Contact the administrator to install the driver before you log in again.
             An error event occurred.  EventID: 0x0000041F
                Time Generated: 03/06/2014   16:31:42
                Event String:
                The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
                a) Name Resolution failure on the current domain controller. 
                b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
             ......................... PRIMARYDC failed test SystemLog
          Test omitted by user request: Topology
          Test omitted by user request: VerifyEnterpriseReferences
          Starting test: VerifyReferences
             The system object reference (serverReference)
             CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com and backlink on
             CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             are correct. 
             The system object reference (serverReferenceBL)
             CN=PRIMARYDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Qtit,DC=com
             and backlink on
             CN=NTDS Settings,CN=PRIMARYDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Qtit,DC=com
             are correct. 
             The system object reference (frsComputerReferenceBL)
             CN=PRIMARYDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=Qtit,DC=com
             and backlink on CN=PRIMARYDC,OU=Domain Controllers,DC=Qtit,DC=com are
             correct. 
             ......................... PRIMARYDC passed test VerifyReferences
          Test omitted by user request: VerifyReplicas
          Test omitted by user request: DNS
          Test omitted by user request: DNS
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : Qtit
          Starting test: CheckSDRefDom
             ......................... Qtit passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Qtit passed test CrossRefValidation
       Running enterprise tests on : Qtit.com
          Test omitted by user request: DNS
          Test omitted by user request: DNS
          Starting test: LocatorCheck
             GC Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             PDC Name: \\SecondAD.Qtit.com
             Locator Flags: 0xe00001bd
             Time Server Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             Preferred Time Server Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             KDC Name: \\PRIMARYDC.Qtit.com
             Locator Flags: 0xe00031fc
             ......................... Qtit.com passed test LocatorCheck
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope
             provided by the command line arguments provided. 
             ......................... Qtit.com passed test Intersite
    repadmin /showrepl Result
    ******************************8
    ==== INBOUND NEIGHBORS ===================================
    DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:41:04 was successful.
    CN=Configuration,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:41:39 was successful.
    CN=Schema,CN=Configuration,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 15:53:01 was successful.
    DC=DomainDnsZones,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 16:27:31 was successful.
    DC=ForestDnsZones,DC=Qtit,DC=com
        Default-First-Site-Name\SECONDAD via RPC
            DSA object GUID: c5ef6e17-77f0-43f6-8d39-5497c563f
            Last attempt @ 2014-03-06 15:53:01 was successful.
    I try to down the DC 2003 and access \\Qtit.com it success open the syslog on DC 2008
    Any help or advice 

    Hi,
    Were there other error codes logged in Event Viewer?
    Regarding Event ID 1055, the following article can be referred to for troubleshooting.
    Event ID 1055 — Group Policy Preprocessing (Security)
    http://technet.microsoft.com/en-us/library/cc727272(v=ws.10).aspx
    Based on the report you posted, this issue may be related to FRS replication service. As a result, we can use ntfrsutl tool to check whether the replication service is healthy.
    Regarding this point, the following articles can be referred to for more information.
    Troubleshooting File Replication Service
    http://technet.microsoft.com/en-us/library/bb727056.aspx
    Ntfrsutl
    http://technet.microsoft.com/en-us/library/hh875636.aspx
    In addition, we can also try doing a non-authoritative Sysvol restore on Windows Server 2008 DC to see whether the issue persists.
    Using the BurFlags registry key to reinitialize File Replication Service replica sets
    http://support.microsoft.com/kb/290762/en-us
    Hope it helps.
    Best regards,
    Frank Shen

  • Root.sh failure during Grid install - segmentation fault for clscfg

    Hi anyone got any idea how to resolve the following error during execution of root.sh on second node of a RAC installation. I see there is a failure when clscfg -localadd is run - perhaps this is the start of the issue. I have no idea what this command is doing
    Any help appreciated
    Installing verison 11.2.0.2 on RHEL 5
    ntpd was NOT running - I ignored this during the pre-reqs at the end of the runInstaller - perhaps this is the issue and i need to start fresh and make sure its running before running root.sh ?
    root.sh....
    Entries will be added to the /etc/oratab file as needed by
    Database Configuration Assistant when a database is created
    Finished running generic part of root script.
    Now product-specific root actions will be performed.
    Using configuration parameter file: /opt/app/11.2.0/grid/crs/install/crsconfig_params
    Failure with signal 11 from command: 1 /opt/app/11.2.0/grid/bin/clscfg -localadd
    OLR initialization - successful
    Adding daemon to inittab
    ACFS-9200: Supported
    ACFS-9300: ADVM/ACFS distribution files found.
    ACFS-9307: Installing requested ADVM/ACFS software.
    ACFS-9308: Loading installed ADVM/ACFS drivers.
    ACFS-9321: Creating udev for ADVM/ACFS.
    ACFS-9323: Creating module dependencies - this may take some time.
    ACFS-9327: Verifying ADVM/ACFS devices.
    ACFS-9309: ADVM/ACFS installation correctness verified.
    CRS-2672: Attempting to start 'ora.mdnsd' on 'coden-ota-odc'
    CRS-2676: Start of 'ora.mdnsd' on 'coden-ota-odc' succeeded
    CRS-2672: Attempting to start 'ora.gpnpd' on 'coden-ota-odc'
    CRS-2676: Start of 'ora.gpnpd' on 'coden-ota-odc' succeeded
    CRS-2672: Attempting to start 'ora.cssdmonitor' on 'coden-ota-odc'
    CRS-2672: Attempting to start 'ora.gipcd' on 'coden-ota-odc'
    CRS-2676: Start of 'ora.cssdmonitor' on 'coden-ota-odc' succeeded
    CRS-2676: Start of 'ora.gipcd' on 'coden-ota-odc' succeeded
    CRS-2672: Attempting to start 'ora.cssd' on 'coden-ota-odc'
    CRS-2672: Attempting to start 'ora.diskmon' on 'coden-ota-odc'
    CRS-2676: Start of 'ora.diskmon' on 'coden-ota-odc' succeeded
    CRS-2676: Start of 'ora.cssd' on 'coden-ota-odc' succeeded
    Start of resource "ora.ctssd" failed
    CRS-2672: Attempting to start 'ora.ctssd' on 'coden-ota-odc'
    CRS-2674: Start of 'ora.ctssd' on 'coden-ota-odc' failed
    CRS-4000: Command Start failed, or completed with errors.
    Cluster Time Synchronisation Service start in exclusive mode failed at /opt/app/11.2.0/grid/crs/install/crsconfig_lib.pm line 6455.
    /opt/app/11.2.0/grid/perl/bin/perl -I/opt/app/11.2.0/grid/perl/lib -I/opt/app/11.2.0/grid/crs/install /opt/app/11.2.0/grid/crs/install/rootcrs.pl execution failed
    I executed the /opt/app/11.2.0/grid/bin/clscfg to see what the result was and it returns a Segmentation Fault to std err
    Edited by: 787789 on Nov 10, 2010 6:58 AM

    Hi,
    here is one document you can go for work around but it is on windows platform but similar error as you posted *CRS Installation Failed with "failed to configure Oracle Cluster Registry with CLSCFG, ret 9" [ID 851742.1]*
    Thanks

Maybe you are looking for