CVI9 - Distribution Log

Hi all,
I've got a problem with the Document Distribution.
When I decide to start the distribution for a DIR I can see in the CVI9 transaction that the "Status of partial order" is egual to "ER".
If I launch the Workflow Log I also can see that the step "Generate distribution order package 00000000000000000026" got a "Generation error".
Have you any suggestions / advice?
Thanks,
Marco.

hi,
Starting the Distribution from the Log
Use
You can start the document distribution from the Distribution Log in different processing situations.
When the system has started the distribution automatically by an event from SAP Business Workflow, you must start the distribution manually from the distribution log.
You can start erroneous distribution order packages that have not been sent a second time from the distribution log.
Note: The distribution was started either manually or automatically by an event from SAP Business Workflow. The part orders must be allocated to a distribution package and have a specific status. The user must have the required Authorizations.
Procedure,
Procedure
Select the part order that you want to start the distribution for.
Choose Extras - Start distribution - <Start function> (for example, manual).
Please note that the part order you select must have a status that is supported for this distribution. How you proceed depends on the start function you choose.
1.Manual: The system starts the distribution for the part order you select without you having to enter any further data.
2.Erroneous: The system starts the distribution again for all the erroneous part orders in a package without you having to enter any further data.
3. Start again with changes: The Start document distribution basic data screen appears. and copies the data for the documents that you want to distribute and for the recipients. You can change this data and add any other documents or recipients as required. As soon as you choose the Start function on the basic data screen, the system returns to the distribution log.
Benakaraja
Edited by: benaka rajes on Jun 24, 2009 12:41 PM
Edited by: benaka rajes on Jun 24, 2009 12:42 PM

Similar Messages

Error found in Software Distribution log

I found below error in my software distribution log. I think it is related to WSUS and many comptuers are not getting proper patches. Any resolution is really appriciated
2014-11-24 15:27:26.773 UTC   Warning   w3wp.325   SoapUtilities.CreateException   ThrowException: actor = http://xxxx.xxxx.xxxx.com:8530/ClientWebService/client.asmx, ID=e5cd4691-63d8-4740-b5a6-f732027896db,
ErrorCode=ConfigChanged, Message=, Client=e78cd58f-cb87-4829-945d-d5ab39d8486d

What do you mean of "not getting proper patches"?
Did these clients fail to update with any error code?
Almost certainly the above log entry is occurring in combination with an 0x8024400D error code ... a very common manifestation of duplicated SusClientIDs.
The log snippet on the client side would look something like this:
2012-02-09 10:02:34:595 948 1994 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2012-02-09 10:02:34:595 948 1994 PT WARNING: SOAP Fault: 0x00012c
2012-02-09 10:02:34:595 948 1994 PT WARNING:     faultstring:Fault occurred
2012-02-09 10:02:34:595 948 1994 PT WARNING:
ErrorCode:ConfigChanged(2)
2012-02-09 10:02:34:596 948 1994 PT WARNING:     Message:(null)
2012-02-09 10:02:34:596 948 1994 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2012-02-09 10:02:34:596 948 1994 PT WARNING:     ID:6b1c0796-e40b-4800-a3c9-d75624d59acf
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Alerts for distribution logs (SCUL)

Hi,
I wanted to know how can we setup CUA alerts i.e. alerts for the errors found in SCUL trx
If the distribution logs in SCUL trx can be emailed if in error.
Please let me know is there any way to do this?
Regards,
Chintan

Hi Ankit,
Yes, this can be done. But for that you have use a script, schedule in cron with 10 mins daily, which will count the number of file and save it log file with some KEYWORD.
For eg, if the number of file are more than 50 then the log file will contain a message, "warning".
Now, as soon as agent finds this message in this file, an auto reaction method will be triggered and emails can be sent for notification.
You can refer below link for more information.
535199 - CCMS agents: Monitoring log files
https://help.sap.com/saphelp_nw04s/helpdata/en/65/f3156d443e744abe15dbe14e4e32b5/content.htm
Regards,
Divyanshu

Replication Distribution log file huge 700gb

Hello to all, Got a replication issue here. I might have found the answer but I'm afraid to run it and want to check with experts first.
I have transactional replication set up on SQL Server 2012 sp1. 13 publications.
Problem: Distribution data file = 19gb Distribution log file = Ballooned to dangerous 700gb
Setup: 1) Transactional replication setup, continuous 2) 13 publications 3) Largest database = 200 gb 4) Distributor properties: Transaction retention 0-72 hours History Retention 48 hours 5) Subscriptions all configured as pull
subscriptions 6) Distribution DB recovery model simple 7) Distribution clean up: distribution job run fine in 13 min(kinda long though) 8) Agent history clean up runs fine (2 sec) 9) Expired cleanup job runs fine (17 sec)
I noticed a few setup inefficiencies and recently made this change: 1) Changed each publications from "never expire" to 120 hour retention
Manually ran some diagnostics: Segment Name Group Id Size in MB Space Used Available Space Percent Used distribution 1 19629.00 3635.81 15993.19 18.52 distribution_log 0 774523.06 741109.16 33413.91 95.69
DBCC OPENTRAN
No active open transactions
Manually ran EXEC dbo.sp_MSdistribution_cleanup @min_distretention = 0,@max_distretention = 72 Removed 0 replicated transactions consisting of 0 statements in 80 seconds (0 rows/sec).
DBCC Loginfo
Returns 1104 rows
Select name, Log_reuse_wait_desc FROM sys.databasess Name Log_reuse_wait_desc distribution LOG_Backup REPLuserdb Replication
Manually confirmed all data from source to subscriber has been replicated and is a match. The data is all there at the subscriber.
Considering running the following command I read about in a few blogs: EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time= 0, @reset = 1
Then running the distribution cleanup job again or shrinking the log. Is there any danger in this,is this the right approach? THANKS!!!

Good idea changing the recovery model. I may have also tried simply running the CHECKPOINT statement to see if that helped change status on some of those entries in loginfo.
I may have missed it in your description, but be sure to INCREASE the default growth increment of the log. I've seen many situations where a very small increment is left from db creation and it results in literally 100s of thousands of VLFs. Now that you've
got it shrunk, change the growth increment to try and avoid this in the future.
Verify that your publication has the "immediate_sync" property set to false. Unless you add subscriptions frequently, this property should always be set to false as it lets the cleanup process cleanup transactions immediately after they have been replicated
to all subscribers. This means that transactions can be cleaned up from the distribution database ahead of the retention period. When set to "true" transactions are always retained for the full retention period which can cause the distribution
database to bloat unnecessarily. There are situations where you want transactions retained (adding new subscriber), but I find it easy to work around those in most cases.
Regarding sp_repldone. It would have probably been fine to run this and I can tell you that I've never seen it cause reinitialization. You probably know that this procedure tells the log reader agent to stop scanning, or really that all of the
transactions in the published database log file have been scanned. It will scan new activity after you run it with those NULLs. When you run DBCC OpenTran in a replicated database, it tells you the oldest distributed LSN. repldone basically
updates that value to the most recent LSN in the log - try it on an unimportant database with some activity and see how OpenTran changes.

Distribution log retation - log is huge!

Hi,
I have 26 publishers with transactional replication to a central subscriber.
All the distributor properties and publication properties in these publishers are the same.
5 of these 26 publishers (publisher/distributor in the same server) have huge distribution log files (up to 100GB) and the log space used is over 90%, even using recovery model simple.
I already tried to configure the distribution retention and the publication retention, already checked the cleanup jobs and even executed the cleanup procedures myself, but the % space used in the huge logs are still over 90%.
I can understand a log retention in the publication database because the log reader agent needs to read the log and send the information to the distributor, but I can't understant this retention in the distributor database. As far I know, the information
in the distributor database is inside the system tables, the cleanup jobs delete old information in these tables, but why I still have this problem in the distribution log and only 5 of 26 distributors with this problem ?
How can I shrink the distribution log in this case ? The database is already in simple recovery model, I'm not understanding the log retention.
Thank you !
Dennes - Se resolveu, classifique a mensagem, por favor - [http://www.bufaloinfo.com.br] NOVO DVD Segurança no ASP.NET : http://www.bufaloinfo.com.br/LearingSeriesSegurancaASPNET2.asp

I had the same exact problem and tried everything thing:
Problem:
Distribution data file = 19gb
Distribution log file = Ballooned to dangerous 700gb
Setup:
1) Transactional replication setup, continuous
2) 13 publications
3) Largest database = 200 gb
4) Distributor properties:
Transaction retention 0-72 hours
History Retention 48 hours
5) Subscriptions all configured as pull subscriptions
6) Distribution database is set to simple
7) Distribution clean up: distribution job run fine in 13 min(kinda long though)
8) Agent history clean up runs fine (2 sec)
9) Expired cleanup job runs fine (17 sec)
I noticed a few setup inneficiencies and recently made this change:
1) Changed each publication from "never expire" to 120 hour retention
Manually ran some diagnostics:
Segment Name Group Id Size in MB     Space Used Available Space Percent Used
distribution 1 19629.00       3635.81 15993.19  18.52
distribution_log 0 774523.06      741109.16 33413.91  95.69
DBCC OPENTRAN
No active open transactions
Manually ran EXEC dbo.sp_MSdistribution_cleanup @min_distretention = 0, @max_distretention = 72
Removed 0 replicated transactions consisting of 0 statements in 80 seconds (0 rows/sec).
DBCC Loginfo
Returns 1104 rows
Select name, Log_reuse_wait_desc FROM sys.databasess
Name             Log_reuse_wait_desc
distribution        LOG_Backup
REPLuserdb        Replication
Manually confirmed all data from source to subscriber has been replicated and is a match. The data is all there at the subscriber.
I considered stopping the sql server agent and running the following command to reset the replication status: EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time= 0, @reset = 1    Then running the distribution cleanup
job again or shrinking the log.
....but this is very disruptive.
Finally I just changed the recovery model to full and back to simple and truncated the log file. Just like your case this is the only thing that worked!

Document Distribution Log Status

HI All,
In CVI9 I can set a document distribution status to Ignore but I cannot find anywhere in the log that it records who set that status and when. Does anyone know if there is a background table where this information is stored so I can write a query to determine who set this status.
Thanks,
Bill

Hi Bill,
in the standard I think there is only the 'Log' and 'Workflow' button which enables you to get further information about how the distrbution was processed. However here the user and time of the change is not displayed.
Best regards,
Christoph

Confirm Receipt - in Document Disribution

Hi All
In Doc Distribution, when I give Confirm receipt option, it asks to give Return Date..
When I distribute the documents, the recipient gets a link to "Confirm Receipt"..
But the originator of the DIR doesn't receive any mail stating the Confirm Receipt of the recipient.. If that is not avaiable, wat is the functionality of "Confirming Receipts"
Can someone explain "Confirm Receipt" function and also about Return Date..???
Regards
Aby

Hi Aby
The recipient needn't do the confirm receipt in cvi9/distribution log. He can just tell the person who initiated the distribution, or the distribution point, by phone/email and then the concerned person can do the confirm receipt in the distribution log the part order is OK (Distribution completed successfully set as green).
This is the scenario given in
http://help.sap.com/saphelp_47x200/helpdata/en/c1/1c249243c711d1893e0000e8323c4f/frameset.htm
in that distribution log->confirming receipt tab you will find the detail information.
Regards
Prasad
Edited by: Prasad Kamarajugadda on Mar 4, 2009 10:43 AM

DMS Document Distribution Problem Pls, Help Will be appreciated

When executing T-Code CVI8(Document Distribution), there is a system message that the order was successfully created. But when we looked at the distribution log using T-Code CVI9, the status of the document remains as SY and the processing of the distribution stops. We already finished the settings for document distribution and still this error persists. What could have been wrong? Pls advice.
Mail Me On:- [email protected]
Regards,
Akshit A. Patel

Hi Athol,
i have checked the workflow config accordingly,
workflow templates 20000104 and 20000137. are active.
a. 20000104 BUS1082 x 2 (Initiated and Resend)
b. 20000137 BUS1082002 x 1 (Resend)
But the Release status for these templates is NOT DEFINED, should it be RELEASED & the container tab for 20000104 shows a warning icon(Mandatary import parameter)on partial order & intial value not set & same for 20000137 shows warning icon on distribution order package & initial value not set.
what does this mean, is there any setting required for this?
2. Transaction SWU3 ensure that all has been generated (activated). Pay special attention to Maintain Runtime Environment -> Configure RFC destination.
I HAVE checked the above all are active except Configure RFC destination, what is the setting required for the same.
the 3, 4,& 5 setting what u have suggested are ok,i have checked them.
Please suggest for the 1 & 2 points.
thanks in advance.

DMS-Document Distribution Setup

Hello ,
I would appreciate if any one can give me some idea's on config part of Document Distribution in Document management system.
I maintained recipeint list and in CVI8 i started document distribution which gave me back an internal order number later i went to CVI9 to execute the initial order number which took me to Distribution log screen .
There i get message like Not assigned to distr. order package,i selected the Box highlighted pertiaing to that document and i executed for document distribution i received a message like Only partial orders with status AS, MA, ER, WO, or WR are allowed.
Guys sorry i may be wrong with the approach on the above step i carried out but can u breif me up what i should have to config and acheive my document distribution succesfull.
Regards,
Murali.S
Points will be awarded for sure.

Hi Murali,
please implement the attached note 1008281 which should solve this
behaviour.
Further please go to the swdd transaction and enter the following worklow
templates (WS20000104 and WS20000137).Go to the edit mode and activate
them once again.
Best regards,
Christoph

Document Distribution Workflow Error

Dear Expert,
After Up gradation from 4.7e to ECC 6.0 in new system we are facing problem in Documents Distribution, after executing Tr. Code CVI8 system generates message Initial order XXX has been successfully created
But, the problem is, in tr. code SBWP document is not received in recipient ID and in distribution log(CVI9) document is shown with yellow flag & "PC" status (i.e. Package crated successfully).
Actually we are maintaining same configuration in both system ECC 6.0 & 4 .7e but its working fine for 4.7e system not for ECC 6.0. Whereas Workflow log gives message "You have not entered a distribution order package"
I already checked
1) Re-activate the following workflows in transaction SWDD: WS20000104 & WS20000137
2) In Tr. code SWU3, Automated workflow customization
3) Activated Even Linkage Type
4) In Tr. Code SWE3 Instances for Event Linkage.
Any suggestions.....Thanks in advance...

Hi Sam,
I have experienced a simliar problem. I'm trying my best to remember how it was resolved.
I think the problem we had was to do with the Context.
1.It had not been defined
2. It was not assigned to an event
Hope this helps.
Neil

Document Distribution - Confirming Receipt

Hi All,
I have setup document distribution to use both RML & INT, with both distribution types requiring confirmation of reciepts.
When distributing via RML the distribution log shows status 'WR' - waiting receipt
When distributing via INT the distribution log shows status 'OK'
Question:
Why does distribution type INT not show status 'WR' - waiting receipt? Users cannot confirm receipt if the status is 'OK'
Please help
Thanks Neil

Hi Christoph,
The tick on the distribution type INT was not ticked & only the confirmation tick was ticked in the Recipient List.
This has been solved
Regards,
Neil
Edited by: Neil Mclaren on Jun 1, 2011 12:33 PM

Document Distribution in R/3 system

hi experts,
Is it possible to use functionality of Document Distribution in DMS without use of Content Server means only using R/3 database.
if yes, how to do it ..what are steps while configuration.
for useful answer points will be awarded. Be sure..
thx...

hi
i had done same things as mentioned below
For document distribution between SAP USERS in SAP DMS
1) I maintained communication type and address for RML.
2) Maintained distribution type activated it and makes it default
3) Also checked: Activating Event type linkage.
4) Maintained the value '2' as processing type for RML
5) Created recipient list and started distribution in Tr. Code CVI8
6) Initial Order is generated, got message document sent successfully.
what is missing, is it necessary a RFC connection & workflow for document distribution within SAP users in same client.
the problem is that in tr. code SBWP document is not received and in distribution log document is shown with yellow flag & "SY" status
thx..

Automatically start Document Distribution

Hello all,
i have a requirement to start the SAP standard document distribution automatically for a specific document if the status of this document is set to a release status.
I stll have implemented the Note 824949 and therefore have activated the event type linkage for the following BUS objects:
BUS1082 INITIATED
BUS1082 RESEND
DRAW     CHANGED   DOKST
DRAW     CHANGED   DWNAM
DRAW     CHANGED   DISTRIBUTION
The manual distribution for documents is still working fine but (the distribution log and the SBWP say it)
But I don't get any log entry and not SBWP mails if a document of a distribution list is set to a release status!!!!!!!! So the automatic process is not working until now.
Do you have some more hints?
Thanks,
Christian

I would use a workflow, at the point when a document is released you create an event. Based on this you can send the information. This is potentially not the easiest way but allows you to do function as you need it.
Regards
Thomas

Document change starts automatic distribution

Hello, Sirs
I am working on automatic distribution of document after a change in a document.
All customizing steps have been covered and distribution is triggered normally but AFTER a change in the document status. So I am forcing the user to change the status to "In treatment", save it, back to "Released" and save it again, in order to start automatically the distribution.
I would like to know if it is possible to start the distribution for a released document , for instance , after a change in the description or the attached file, but if the status of the document remains unchanged.
Thanks for your help
Dario

And also refer the following:
[Document distribution General Information|https://wiki.sdn.sap.com/wiki/display/PLM/1.GeneralInformation]
[Recipient Management|https://wiki.sdn.sap.com/wiki/display/PLM/2.RecipientManagement]
[Recipient Lists|https://wiki.sdn.sap.com/wiki/display/PLM/3.RecipientLists]
[Distribution orders|https://wiki.sdn.sap.com/wiki/display/PLM/4.Distributionorders]
[Distribution Log|https://wiki.sdn.sap.com/wiki/display/PLM/5.DistributionLog] And
[Hints for Document Distribution|https://wiki.sdn.sap.com/wiki/display/PLM/HintsforDocument+Distribution]
Good luck
Regards
Amaresh Makal

Software Updates in an Untrusted Forest

Hi all,
I've build a SCCM2012R2 site with 2 forests involved. They are UNTRUSTED.
Forest 1 contains a primary site with SQL and a secondary across WAN distribution point. This all worked great for Applications and Window Updates.
The second untrusted forest has 1 site server with a Management Point, Fallback Status point, Distribution point and default roles. for some reason I can't get a client in the untrusted forest to get the software update packages I create.
I have deployed them to all distribution points and the clients in the untrusted forest (manually installed) have shown up in SCCM and are in the correct test collection.
Boundary groups have been setup with boundaries on IP subnets.
Is there any specific logs I can check? Does the a Software update point need adding to the untrusted forest site system?
A firewall block communication between the forest to I have created Site server to Site server rules but untrusted forest client don't have access back to the primary site server.
If I could just get this software updates working I'm complete!! Any help would be great!!

Thanks for the help trouble shooting,
This is now resolved.
For info the clients in the untrusted forest need to be able to access the WSUS website. As I have a locked down firewall between my forests I add an Any to SCCM WSUS on port 8530 and tested on IE. Page comes up as access denied but it proves the connection.
Software deployment and WSUS on an untrusted domain with out any AD connection, DNS or WINS requires a manual (or scripted) install of the clients specifying the SMSLP, SMSSITECODE, SMSMP and SMSFSP for that forest. All these roles need are required
to be installed for the site server for that untrusted forest when adding it into SCCM if you don't have access to the forests AD or DNS.
The only connection clients seem to need back to the primary site it the WSUS website for syncing. Packages are still distributed to the servers in the untrusted.
As I have been using a firewall between the sites I allowed the site servers communication over the following ports.
80,443,445, 135,1027, 49152-65535
Note: Without the RPC dynamic port range I got errors in SCCM distribution logs.
Site servers to SQL was as standard. 1433,4022.

CVI9 - Distribution Log

Similar Messages

Maybe you are looking for