PeopleTools 8.22.19 Upgrade : Distribution Agent fails to distribute

After we upgraded our People Tools from 8.20.13 to 8.22.19, the distribution agent fails to distribute reports. Does anyone have similar experiences before or any know solutions? Please share here.

Elvis,
Did you change the hardware ? If so, then did you checked the existence of the report repository and write access ?
Did you (re)checked the report node definition ? Is it still valid ?
What error did you got from the process scheduler log file ?
Nicolas.

Similar Messages

The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.

One of my replication job failed with below error, which means job failed because of permission issue on the folder. To resolve that, I have granted the permission and it started working fine. Now the question is as my job was running fine since long time
without any issue then how suddenly the permission of the folder got omitted automatically? I am sure that no one deleted the permission from the folder and as the server is part of SQL cluster no failover occurs.
Error:-The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.
Rahul

Hi Rahul,
Error code 5 indicates that the error is "access is denied." Please make sure that the COM folder is excluded from any antivirus scan that occurs on the system.
If the issue still persists, I recommend you use
Process Monitor to find out a bit more about the accounts and access requests involved. Then grant write permission to the exact COM folder for the account that is running the SQL Server Agent service. For more details, please review the following similar
thread.
http://www.sqlservercentral.com/Forums/Topic1364832-1550-1.aspx
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

Distribution agent failed to create temporary files in

Hello,
we are configured transnational replication in sql server 2005 location, all replication jobs are running fine,
while we checking sql server errorlog showing below error :
Distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\100\COM' directory. System returned errorcode 5.
NOte: normally we are configured replication 2005 [90] , but while see the above error it shows [100] comparability level .

Hi,
If the account that is running SQL Server Agent does not have write access to the COM folder, the Distribution Agent will fail
when it is running as a job. If you run the Distribution Agent from a command line by using an account that does not have write access to the COM folder, the same failure will occur.
To work around this
issue, grant write permissions to the COM folder for the account that is running the SQL Server Agent service. If you run the Distribution Agent from a command line, grant write permissions to the COM folder for the account that you use to run the Distribution
Agent.
For more information, please go through the below URL:
http://support.microsoft.com/kb/956032/en-us

Install agent fail (Agent host must be registered before an agent can be installed or upgraded.)

I got the following error with trying to install agent
# java -jar agent.jar -d /u01/avagent/
Agent host is not registered.
Agent host must be registered before an agent can be installed or upgraded. Agent deployment failed.
database firewall ip address is 10.0.0.10 (for management) and 192.168.0.10 (for traffic source)
auditvault server ip address is 10.0.0.11 (for management)
I have 2 IP address on my DB 10.0.0.9 and 192.168.0.9
when i register host with ip 192.168.0.9 i will get the error
but if i register host with ip 10.0.0.9 installation is fine with no error
i want to monitor audit traffic on 192.168.0.9 interface which is for client to access so i need to register host with ip 192.168.0.9

hi Stefan,
this is expected behaviour, or at least it's better to say : in a multi homed system the choice of the network path that is used is determined by the underlying tcp network,
it doesn matter which path the sqlnet connection from agent to AV server takes as long as it is able to connect. Your statement about 'monitor audit traffic on 192.168.0.9'
does not make sense, the agent / collection framework is the part that fetches audit records from secured targets and has nothing to do with monitoring network traffic since
that part of the functionality is done by the firewall component. Anyway if you want to change the nework path you need to use 'route' and force it,
greetings,
Harm ten Napel

Distribution manager failed to connect to the distribution point

After upgrading my distribution point to windows server 2012 standard I can't distribute content to my distribution point.
I see the following error.
source: SMS Server
Component: SMS_DISTRIBUTION_MANAGER
message id 2391
Distribution Manager failed to connect to the distribution point Check your network and firewall settings.
The firewall is not enabled.
wbemtest is able to connect to the remote server that has the distribution point role installed.
The network access account is working.
How do I fix this?

but why does it most of the time work? I did inplace upgrade at least 6 times from 2008 R2 to 2012 R2 and every DP except one works fine.
I'm not completely sure, but I think, my faulty one, that I'm trying to get working, was working correctly after the inplace upgrade. But as I said, that is only a theory, I'm just curious if that's possible.
I have the same issue as described above.
The IT guys from LukOIL

Distribution manager failed to create the defined share or folder on distribution point and failed to connect to remote distribution point

We have recently upgraded remote distribution point to SCCM 2012 R2 CU4. when i try to distribute the package getting the error on the distribution point configuration status "Distribution manager failed to create the defined share or folder on distribution
point and failed to connect to remote distribution point"
Errors on the package transfer log file.
CWmi::Connect() could not connect to \\XXXXXXXX.COM\root\SCCMDP. error = The operation completed successfully.. Will try FQDN
CWmi::Connect() failed to connect to \\XXXXXXX.COM\root\SCCMDP. error = The RPC server is unavailable.
Failed to connect to the DP WMI namespace on the remote DP

Thanks Sandys for your suggestions.
i have tried wbemtest from site server(Secondary site) and remote DP server. Receiving the "The RPC
server is unavailable" from both ends.
error:0x800706ba - The RPC server is unavailable

What is an upgrade distribution system?

In Apple discussion document 2465 [ https://discussions.apple.com/docs/DOC-2465 ] I found this question and answer:
Q: Are there any pitfalls to watch out for?
A: With all upgrades, backing up your data at least twice has been a given. Hardware can fail independently of downloads and upgrades, though may happen simultaneously. Software may be found to be incompatible that has not been tested with the new upgrade, or combination of other software that might be installed with the upgrade. It is also strongly recommended once your backup is complete, to shut down your computer, remove all but Apple wired keyboard and mouse (notebooks remove all input devices). Then once done, reboot, and go directly to the upgrade distribution system available.
Third party system tools, modification, and "maintenance" applications should be verified as compatible, or removed until known to be compatible. Check with developers how to remove if it is essential to use Lion before those applications become compatible. Most "maintenance" tools that deal with system cache, prebinding, are not really maintenance tools. Ask on forum when are the appropriate times to use them before assuming they should be used for upgrades or otherwise.
What is an upgrade distribution system?
Thanks.

Well, if you happen to have several computers that run the same versions of software
and have similar need to upgrade them, essentially offline to not duplicate the costs of
bandwidth activity (and thus perhaps lose access due to overage fee or penalty) the
idea to download copies in a more traditional sense may be more difficult than with the
previous versions of OS X. With up to three Macs at similar OS X version build series,
it made sense to save all of the download compressed document or application files to
share with the other computers, to install & update them offline. And fully restore them
should the need arise, with complete copies of upgrade & updates, saved offline.
Now these require an Apple ID and other steps, the path isn't quite as clear. There may
be a path but it isn't as simple as copying a .zip file to a USB flash drive, and plug that
drive into another Mac, and drag the file to its desktop in Finder. It may be that simple
if you were to get the download without the baggage of ownership tags it may imply.
This is an area I haven't gotten into much, with only one Mac tied to an Apple ID.
The latest OS X is Mavericks 10.9.5, it is OK. I don't push it much with only 4GB RAM.
And the other computers mostly run Leopard 10.5.8. One Tiger 10.4.11. Another that
is seldom turned on, Mac OS8.6 (PowerMac 7600.) None are networked by server.
You could say I kinda made a mistake and kept a new old-stock Mini quad core server
that was ordered in December, so here it is. Although it asks on occasion for me to get
the AppleCare Plan, and extra RAM (it can use 16GB) it has two 1-TB HDDs. Sadly
both are only 5400-RPM rotational, not 7200-RPM; to supplement data transfer time.
Anyway, if you get a fair deal on a refurbished or new-old-stock i7 Mini quad core, it
may be a server model with dual hard drives. You could upgrade them & the RAM too.
And choose to not use the Server. With less RAM, now discontinued model runs OK
with the as-shipped Mavericks. Older stock was said to have Mountain Lion. Better yet
in situation where RAM and system resources are less. Yosemite likes even more...
Well, have fun with it, if possible...
Good luck & happy computing!

SCOM : Issues while upgrading SCOM agent from 2012SP1 to R2

Hi,
We have upgraded SCOM setup from SP1 to R2 but facing issues with agent upgrade.
We were able to view only ~70% agents in pending management (Agent requires update).
Further, when I tried to upgrade agents through console, some are successfully upgraded but rest are giving
error.
Can someone help me to understand why all agents are not appearing in pending management for upgrade?
I also tried to upgrade agent manually but no luck. It gives error "The path 'C:\Windows\.........\monagent.msi'
can not be found. Verify that you have access to location and try again or try to find installation package.........". , though I had logged into server with admin access.
Also most of servers are remotely manageable but unable to upgrade through console.
Thanks,
Priya

Hi Priya,
I understand you require the Agent data. How ever the events clearely say the issue is because of the old installation files.
I was looking a a article on updating an agent to SCOM 2012 R2 from the below link.
https://technet.microsoft.com/en-us/library/dn249715.aspx
So the link says:
When you upgrade an agent, the Operations Manager installer service runs and is not removed until after the completion of the upgrade.
If the agent upgrade fails, you might have to re-install the agent because the installer service was not properly removed. If you attempt to upgrade the agent again and it fails, you should re-install the agent after you have completed upgrading all features
of Operations Manager.
So i would suggest you is you try the below on only 1 agent.
1. Download the Agent Dump from the below link and try updating it. (This is my copy of MOM Agent.msi from my installation media of SCOM
2012 R2)
https://www.dropbox.com/s/wv7y37moyd04209/MOMAgent.msi?dl=0
If the above does not success and gives you the same error then try the below
1. Select an agent and pull all the perfmon data / Alerting data required for it using SQL Query or Reporting.
2. Uninstall the Old SP1 Agent setup.
3. Install the Agent via Discovery Wizard or do a manual installation and see if the issue resolves.
I think either from both the steps will solve the issue.
Gautam.75801

Added another subscriber to existing publication. Snapshot delivered but ket re-initializing if Distribution agent is restarted

Hi,
Here is the situation. We have existing replication with sql 2008 r2 publisher and a subscriber on same edition. The database is quite big so snapshot generally takes about 4 hours or more. There are additional tables on subscriber so a backup / restore
mode of initialization is not suitable.
This replication is working just fine, now there is a need to add a sql 2014 subscriber to this publisher and same tables as in current publication, so we decided to simply add another push subscription for this new sql 2014 subscriber. During the process
the Initial snapshot is generated and applied to new 2014 subscribe, keep in mind we have not made any change to publication to avoid affecting the existing subscriber. So when snapshot is delivered and appeared in replication monitor it started creating primary
keys on subscriber database. We have few big tables where we are not sending clustered and non clustered indexes across so that replication snapshot goes fast (although it is over 4 hours). These indexes and primary keys get created with manual scripts after
snapshot is generated. During this time log reader agent has been actively sending transactions to existing subscriber that is telling me that as soon as distribution agent done with the snapshot it will start sending transactions to new subscriber (which
is quite normal). Now the problem, after snapshot is done I need to run manual scripts to create PK and indexes on new subscriber, to do that I have to stop distribution agent so that indexes and PKs don't get blocked. After I stopped distrib
agent temporarily, the Scripts got completed successfully within 20 minutes and when I re-started distribution agent , to my surprise it started initializing the new subscriber again and sending same snapshot that was already applied. It make me puzzled
what caused the distribution agent to reinitialize although it already delivered snapshot and I have indexes created and ready to go. I tried this process again with more careful approach and gave about one hour after snapshot delivered message received. but
it did the same thing. Only explanation I can think of that publisher database is actively sending transactions when I was applying snapshot and as soon as it is delivered, the distribution agent started delivering transaction, I could see Undistributed
Commands kept on growing high telling me that there are lots of transactions for new subscriber to catch up but without indexes and some missing primary keys it would not even catch up and so I always stop the distrib agent and run my scripts on subscriber
and run into this situation. During all these times the existing subscriber never had any issue.
Do I need to make sure no ort minimal transactions happening on publisher when I initialize the new subscriber.
Or should I create new separate publication on the same publisher and use that.
Any other suggestions are welcome
Thanks!
dba60

Snapshot was set of initialize immediately. No errors in repl_errors table. Distribution agent was using default profile.
Do you think that I should be running missing PK and indexing scripts as part of replication, replication provides an option run scripts before or after snapshot was applied. Also, I am wondering if creating some missing PKs is triggering the snapshot to
be reapplied. Also, Why the primary key for some tables not coming along during snapshot delivery?
Do you think having lots of transactions on publisher database while snapshot being applied would be affecting it too?
Also, is it possible to use a different distributors for each publication from same publisher?
My plan now is to create new publication for same publisher and database, this way I will have more control over changing article properties.
Thanks!
dba60

Agents failing when sent as attachments (pdf or excel) in OBIEE 11g

Hello,
We have issue agents failing with following error when set up with attachment (pdf or excel only) either as Dashboard or Report. If the same agent is run as inline then the agent is working fine. OBIEE version is 11.1.1.6.0 unclustered.
[nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: A fatal error occurred while processing the request. The server responded with: java.io.IOException: The system cannot find the path specified.
Error Codes: AGEGTYVF
Location: saw.rpc.mis.read, saw.subsystem.portal.pdf, saw.delivers.rpc.getDeviceContent, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads
We tried logging in as user/Administrator and running the report from catalog without any error. Also strangely this is evident in only a specific environment. Not sure what is causing the issue.
Please advise.
Thanks

What is the size of the attachments of reports you are trying to send thru Agents .? either PDF or EXCEL ?
What does you JavaHost log .?
I think this is a same Bug 14680611 : ERROR CODES: AGEGTYVF RUNNING AGENTS WITH LARGE REPORT AS EXCEL ATTACHMENT
If your are not able to download even smaller attachments/reports then, I would raise an SR with Oracle.
Let us know. Hope this Helps.!
Thanks,
SVS

How to Upgrade Target Agent from 10.2.0.3 to 10.2.0.4

Hi Everybody,
I am doing this first time so need some help
Q1. I need to Upgrade Target Agent from 10.2.0.3 to 10.2.0.4 manually and can't seem to find the right patch I need.
I tried p3731593, but this seems to be installing much more than what I need so I cancelled it
One option I thought of was to uninstall 10203 agent and install 10204 in the same agent home But I was wondering if there is a way I can upgrade my agent.
Q2. Does the agent version on target and host(OMS) need to be same or can I have Target Agent 10.2.0.4 and host agent 10.2.0.3?
Thanks for helping in advance
Jeet

Hi Jeet,
You can use Patch 3822442 to upgrade the agent.
The agent can be of different version.
Regards
Lai

Why call between WebClient agents fails?

Hi,
I have just recently installed the mySAP CRM 4.0 IC WebClient (CRM40 SP00).
I have been testing the installation with CCS (Contact Center Simulator) and for a basic CCS supported tests (Inbound Phone call, Outbound Phone call, Chat) everything seems to be ok, but a call between WebClient agents fails due to an java error. The Phone Call between WebClients which should work according the CCS webpage.
What should I do to get WebClient agents to call each others? Any configuration or customization tips? Note that I do not have CC integration in place, just the IC WebClients.
Here is the test done in details and the error reported by WebClient:
0) I restarted SAP CRM to be sure no pending sessions exists
1) Open the CCS to see that no agents are logged in with WebClient
2) Login as java_ic with WebClient
3) CCS shows java_ic Workmode (=status) as 'Not Ready'
4) Switch java_ic to ready by from the WebClient
5) CCS shows java_ic Workmode (=status) as 'Ready'
Then I do the same for agent 'sap*' with another MSIE browser window. At this point, the CCS shows Workmode for both agents as 'Ready' and I have two WebClient browsers opened. I also verify that both has Phone selected from the channel selector in the WebClient.
6) With java_ic agent, I press the Dial Pad, enter the sap* agent phone
number (Phone: +15550002; shown in the CCS for both agents logged in) and then I press the Dial button on Dial Pad to call to +15550002.
6.1) After pressing the Dial button, the WebClient displays a pop-up in
the middle of the screen with info: "Your request is being processed." After this there is an Info message under the buttons in the WebClient for java_ic saying: "No account information found".
7) Java_ic WebClient shows that it's doing an outbound call and is 'Dialing' state.
8) sap* WebClient window has blinking button with labels 'Accept' and 'Reject'. So, it clearly got an notification of the Inbound Phone call coming from java_ic. But there is also an error message under the buttons in the same WebClient webbrowser screen (not in the JavaConsole, not in separate alert message this time) for sap*:
"Java error: type= APPLICATION ERROR, ID= GETIAD_FAILED, description=".
9) With sap* WebClient I cannot answer or reject the call. Nothing happens. The browser Status Bar says: javascript:void(0) when I press the Accept button.
10) At this situation, the CCS shows that the agents's sap* Workmode is
switched from the previous 'Ready' state to 'Not Ready' automatically (while the sap* WebClient status is still in Ready). So, the sap* automatically, due to the error, changed the status to 'Not Ready'.
11) java_ic remain on 'Dialing' status for all the time trying to get connected with sap*.
I got informed that the call between WebClient COULD BE seen as a "call transfer" between clients by the CRM system. This might be something to do with the problem in calling between WebClients.
Because the java_ic reports: "No account information found" when placing the Outbound Phone call, one could assume that account details should be passed along with the call transfer. Possibly sap* cannot receive the
inbound phone call due to a missing account information thus reporting java error: "Java error: type= APPLICATION ERROR, ID= GETIAD_FAILED, description=".
Best Regards,
Jani

[loaded] com.genieo.completer.download.plist Adware! [Remove]
[loaded] com.genieo.completer.ltvbit.plist [Support]
[running] com.genieo.completer.update.plist Adware! [Remove]
[not loaded] com.macpaw.CleanMyMac.helperTool.plist [Support]
[not loaded] com.macpaw.CleanMyMac.trashSizeWatcher.plist [Support]
[not loaded] com.macpaw.CleanMyMac.volumeWatcher.plist [Support]
[loaded] com.macpaw.CleanMyMac2Helper.diskSpaceWatcher.plist [Support]
[loaded] com.macpaw.CleanMyMac2Helper.scheduledScan.plist [Support]
[loaded] com.macpaw.CleanMyMac2Helper.trashWatcher.plist [Support]
Your machine is slow because you loaded a bunch of third party junk on it.

Distribution Manager Failed To Access The Source Directory

Hello All,
I have this issue distributing content to my Distribution Points for months now. I keep running into this error below:
Distribution Manager Failed to Access the source directory (\\share\folder\file.wim)
Possible Cause: Distribution Manager does not have sufficient rights to the source directory.
Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.
Possible Cause: There is not enough disk space available on the site server.
Solution: Verify that there is enough free disk space available on the site server.
I checked the distmgr.log file and received these messages:
GetTempFileNameA failed; 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
CFileLibrary::AddFile failed; 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
CContentDefinition::AddFile failed; 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
Failed to add the file. Please check if this file exists.   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
SnapshotPackage() failed. Error = 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
Failed to take snapshot of package CSU0006A   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
There is enough space on the site server and the site server has full control over the source directory. I wish I can give you more information but I'm hoping this is enough info to get some assistance. If more information is needed please let me know!

We usually give the DP's computer account and the site server computer account read access to these shares in our environment.
... which is not enough for drivers and updates (as there will also files be added).
Torsten Meringer | http://www.mssccmfaq.de
... And for capture Image too if your capture destination points on that share

Distribution Manager failed to process package triggers an update of the packages

Hi all,
we have randomly following issue:
SCCM 2012 Sp1 CAS, takes a snapshot of a Windows update package in the morning (not sure how the frequency of this check is done). If for any reason it fails, SCCM automatically redistributes the package to all sites. This happened this morning again for 5
Windows updates packages. You understand that this means GB sent to all Secondary sites (66) with an useles amount of data sent out.
From the Status messages I see
Information Milestone RC0 06.11.2014 07:12:11 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2300 Distribution Manager is beginning to process package "SUP-2014.09" (package ID = RC00017B).
Then lot of updates lists with comment taking a snapshot and finally
Error Milestone RC0 06.11.2014 07:12:29 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2302 Distribution Manager failed to process package "SUP-2014.09" (package ID = RC00017B). Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
This triggers immediately an update of all DPs
Information Milestone RC0 06.11.2014 07:43:52 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2304 Distribution Manager is retrying to distribute package "RC00017B". Wait to see if the package is successfully distributed on the retry.
Any idea
How this can be avoided, since nobody changed the package and we suppose it was a temp connection issue between the CAS and the package repository server
If this check can be set up to once a week for instance or even less?
Thanks,
Marco

Hi Daniel,
thanks for the prompt answer. Actually I saw it yesterday at least for 1 package (the last one). The error is generate by SQL killing a task
Adding these contents to the package RC00010D version 347.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:23
7796 (0x1E74)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:23 3652 (0x0E44)
*** [40001][1205][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 152) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
5460 (0x1554)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCHVSGGSC600.rccad.net SITE=RC0 PID=2144 TID=5460 GMTDATE=jeu. nov. 06 06:12:25.422 2014 ISTR0="SUP-2012.Q4" ISTR1="RC000068" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RC000068"
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
5460 (0x1554)
Failed to process package RC000068 after 0 retries, will retry 100 more times
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
5460 (0x1554)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:25 5460 (0x1554)
Used 4 out of 5 allowed processing threads.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:26
3300 (0x0CE4)
Starting package processing thread, thread ID = 0x894 (2196)
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
3300 (0x0CE4)
Used all 5 allowed processing threads, won't process any more packages.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
3300 (0x0CE4)
Sleep 1828 seconds... SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:27 3300 (0x0CE4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCHVSGGSC600.rccad.net SITE=RC0 PID=2144 TID=2196 GMTDATE=jeu. nov. 06 06:12:27.716 2014 ISTR0="SUP-2014.M05" ISTR1="RC00011D" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RC00011D"
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
2196 (0x0894)
Start updating the package RC00011D... SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:27 2196 (0x0894)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=RC00011D, Version=14, Status=2300
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
2196 (0x0894)
*** [40001][1205][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 154) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
1424 (0x0590)
Taking package snapshot for package RC00011D
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
2196 (0x0894)
Now as I mentioned it was probably an SQL (more likely) or networ issue, however the question was more about how to avoid that. Finally the packages were not changed and if possible I would avoid any automatic SCCM action on packages unless an operator manually
triggers them.
I didn't see any error today, so it should not be a configuration issue.
Is this possible?

Calendaring agent failed with error code 0x8000ffff Event id 8206 and 8207

Hi to all
We have an Exchange 2007 SP3 with Update Rollup 11 and all the user use Outlook 2003 with SP3.
Suddenly in our Exchange Server we have start to receive a lot of 8206 and 8207 EXCDO errors in the Application.
Event Type: Error
Event Source: EXCDO
Event Category: General
Event ID: 8206
Date:  5/2/2015
Time:  11:17:41 πμ
User:  N/A
Computer: EXCHANGESRV1
Description:
Calendaring agent failed with error code 0x8000ffff while saving appointment.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 48 72 53 61 76 69 6e 67   HrSaving
0008: 41 70 70 74 3a 3a 48 72   Appt::Hr
0010: 43 68 65 63 6b 50 61 74   CheckPat
0018: 74 65 72 6e 20 66 61 69   tern fai
0020: 6c 65 64 2e 20 4d 61 69   led. Mai
0028: 6c 62 6f 78 3a 56 61 73   lbox:x
0030: 73 69 6c 69 73 2e 4b 6f   xxxx.xxx
0038: 6e 74 6f 67 69 61 6e 6e   xxxxxxx
0040: 69 73 40 45 55 52 4f 43   xx@xxxx
0048: 48 41 52 54 49 4b 49 2e   xxxxxxx.
0050: 47 52                     GR
Event Type: Error
Event Source: EXCDO
Event Category: General
Event ID: 8207
Date:  5/2/2015
Time:  11:19:41 πμ
User:  N/A
Computer: EXCHANGESRV1
Description:
Calendaring agent failed with error code 0x8000ffff while deleting appointment.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 48 72 44 65 6c 65 74 69   HrDeleti
0008: 6e 67 41 70 70 74 3a 3a   ngAppt::
0010: 5f 48 72 47 65 74 42 75   _HrGetBu
0018: 73 79 49 6e 66 6f 20 66   syInfo f
0020: 61 69 6c 65 64 2e 20 4d   ailed. M
0028: 61 69 6c 62 6f 78 3a 56   ailbox:x
0030: 61 73 73 69 6c 69 73 2e   xxxx.xxx
0038: 4b 6f 6e 74 6f 67 69 61   xxxxxxxxx
0040: 6e 6e 69 73 40 45 55 52   xxx@xxx
0048: 4f 43 48 41 52 54 49 4b   xxxxxxxx
0050: 49 2e 47 52               I.GR
All the errors come ONLY FROM 1 USER.
How can i fix this errors?
If you require any further information do not
hesitate to let me know
Thanks and regards.

You must ask in Exchange forum
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver

PeopleTools 8.22.19 Upgrade : Distribution Agent fails to distribute

Similar Messages

Maybe you are looking for