Thks for quick response.
Yes, running Crystal Enterprise v8.5 in clustered environment of 2 APS and component servers and 2 Web servers.
I checked the date/time on the CE servers and both have same date/time.
It seems that when an recurring instance failed, it created an additional recurring instance with same next start date/time, resulting in 2 identical recurring instances.
Is this a valid assumption ? If so, why or under what circumstances this may occur ?
Can u think of any other reasons which may cause a recurring instance to be duplicated.
We have an install of CE10 that has had this problem intermittently. From talking to support, I know it is a problem some customers have, especially in a clustered cms (aps) environment. If you have technical support maintenance at Crysal, I suggest you call this one in. As far as I know, they haven't resolved the issue, but I think they have a patch they are working on. Personally, I have disabled one of my 2 cms's until I can get this and other issues resolved, which means no failover on the cms service. Our main issue is Pendings, possibly caused by the recurrings, so if anyone has any information on jobs which go into Pending when job childs are still available, I'd like to hear from you.
dchant,
Don;'t know if you still need this information, but Crystal released a patch this week which addresses "extra recurring jobs" in a clustered CE environment. Search for track number ADAPT00229886 on their website.
dchant,
Don't know if you still need this information, but Crystal released a patch this week which addresses "extra recurring jobs" in a clustered CE environment. Search for track number ADAPT00229886 on their website.
We're experiencing the same issue. It started over the weekend. Have a ticket it in with Crystal support but no response yet. Running CE9 clustered and we have the same symptoms reported in this thread where we have a duplicate recurring schedules with usually a pending and a failed instance. I tried to locate the ADAPT00229886 track number on the website but was unable to find it. We knew about the duplicates because clients were receiving duplicate reports in their email. When we checked the report in CMC there were no duplicate schedules or instances visible. It wasn't until after I restarted the crystal services that they became visible in the CMC.
According to Crystal Support this issue has not yet been resolved. The theory is that the duplicates are created in a clustered environment when the second APS is starting and a recurring job is already running. So the recurring job that is already running gets duplicated when the second APS comes up. I don't think this scenario applies to our case but the recommendation when restarting the APS is to stop the job servers first and wait a couple minutes before restarting either APS service. The theory may be accurate but there are obviously other scenarios where duplicates can be created because we hadn't had this problem until Monday and we hadn't restarted the Crystal services in a couple weeks.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.