Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
I am using Creo Parametric Release 5.0 and Datecode5.0.5.0
My engineering team has been experiencing two new issues this week that have affected multiple people working on completely separate projects. Error 1: This error comes up when attempting to promote recently checked in objects. From the publisher it seems that it is in the que to be promoted correctly, but there is no person assigned to do the review/accept. The person promoting it usually assigns these to themselves, but we don't see any requests.
Error 2: It occurs when attempting to upload assemblies (4 separate ones so far with no similarities that can be found) that use existing parts (but not all). We are used to having to re-download the correct version of some common parts before checking in, but when going through the process of add>download on all these parts we would usually regenerate and reupload from Creo. However, regenerating it makes windchill think we've modified those parts again and refuses to let us upload in creo. We can get around this by promoting within windchill (as this doesnt regenerate) but this isnt an acceptable solution as anyone modifying or opening these later will have the same issues upon regenerating.
Here are the errors that I faced
Error 1: "ATTENTION: A persistence error has occurred. Contact your administrator for assistance."
Error 2: "A SQL error has occurred. Database system message follows:"
What version of Windchill are you using and what database and version?
These issues are more related to Windchill than Creo.
Hi this is copy-pasted from the windchill about. I'm not sure how to check which database/version
Release: 11.1 M020
Products Installed
Creo View - Clients
windchill 1.3 REST Services
windchill 11.1 help center
Creo View - Adapters
windchill 11.1 service pack
windchill pdmlink 11.1
windchill 11.1 info*engine
windchill 11.1 Services
windchill 11.1 common base
Did you ever figure this out? I too have been dealing with "SQL Error" and have been able to work around it, but am now unable to check in a large assembly. I hope you figured out a fix!