Skip to main content
S
sm_011-Visitor
1-Visitor
October 21, 2016
Solved

Academic Windchill Server Upgrade Status

  • October 21, 2016
  • 3 replies
  • 14357 views

Hi everyone,

PTC is in the process of staging the Windchill 11.0 upgrade for the Academic Windchill server and plans to execute the upgrade next month. I will let you know as soon as a upgrade date is chosen to make sure it does not conflict with any activities you might have. PTC typically does the update over a weekend and tries to minimize the downtime as much as possible.

-Scott

    Best answer by smorris

    No, I'm assuming your issue has to do with the database indexes and I'm curious if the restart Alex Ouellet‌ announced the other day might have corrected it.

    3 replies

    S
    smorris1-Visitor
    1-Visitor
    December 23, 2016

    If you have not already noticed, the PTC Academic Windchill server has been updated to Windchill 11.0

    The PTC team worked overtime to get this in before the end of the year to allow teams to update software and make adjustments before the FRC season starts. The update was completed on Wednesday and its ready for production use. To learn more about post upgrade actions or requirements, please check out this link: Important! Read Me First, which is also available at the top of every page in Windchill.

    This new version will fix the age-old problem of Chrome and Firefox not behaving with Creo View. Personally, I would still recommend using Internet Explorer (not Edge) as your browser of choice for Windchill.

    There is one last item that need to be addressed in January. The current version of Creo View available on the server is Creo View 3.1 F000. To fix the issues with the Chrome browser, PTC needs to post Creo View 3.1 M010. The plan is to do that at the start of the year so everyone can update their environments.

    If you have any comments, suggestions, questions or feedback, please post them here.

    R
    RWHahn1-Visitor
    1-Visitor
    January 4, 2017

    I am having trouble logging into the server. The message "The server is not supported" pops up. Trying to create a new one with different name produces the same result.

    A fresh install on a student's computer connected to the server but he gets the message "A persistence error occurred. System message follows:" and nothing.

    R
    RWHahn1-Visitor
    1-Visitor
    January 4, 2017

    Found discussion "Windchill register server not woking". Erased indicated folders then tried to add new server. Get the same message and then "Invalid server location. Please change the "Location" field and try again.  Location was cut and paste from discussion.

    N
    nrensing1-Visitor
    1-Visitor
    January 5, 2017

    We're having similar problems. Before I changed anything, Creo started up smoothly and I could log into Windchill, but when I tried to open last year's robot model I got an error (in the bottom message bar, not a dialog box) that the model cannot be opened.

    I cleared the browser and Java caches and deleted the ProEngineer folder as per the instructions above. I now get the script error dialog boxes (as shown above), and can't browse through the Windchill cabinets because of these errors. However, I can still get to the Windchill folders by clicking on the "open file" icon. I can find the Creo assembly I'm looking for, but it doesn't open. Some older models do open. This model was last modified in November.

    Interestingly, even though I deleted the ProENGINEER folder as instructed above, my Creo session still automatically logs into the Windchill server - it remembers the URL and my credentials.

    Suggestions?

    N
    nrensing1-Visitor
    1-Visitor
    January 5, 2017

    For what it's worth, I disconnected from the server, closed Creo, deleted the ProENGINEER file, cleared the Java cache, restarted Creo, and reconnected to the server. (Note that I didn't not have to re-enter my credentials, Creo still had those - where are they stored?) That resolved the script error. Now I can browse to the Windchill folder using the built-in browser. Trying to open that file generates the "Persistence error" in the event  manager dialog box.

    The assembly is currently checked in and the students don't recall anything unusual happening when they worked with it in November.

    S
    smorris1-Visitor
    1-Visitor
    January 5, 2017

    Noa, I just realized there are some other files that hang onto the server credentials in %USERPROFILE%\AppData\Roaming\PTC. You can remove the PTC folder and it will clear everything. The contents of this folder are created and then referenced at run-time, so there should not be any issues with removing it. If you feel safer renaming it, you can do that also.

    If you want to PM me the name of the CAD file, I can try opening it on my side to see what happens.

    S
    smorris1-Visitor
    1-Visitor
    January 11, 2017

    *** UPDATE FOR ALL ***

    I missed a critical step in this year's Windchill upgrade; validating which maintenance release of Creo 3.0 is certified. Unfortunately, I completed all the User Acceptance Testing with Creo 3.0 M110 forgetting that most teams are either on M040 or M070. It has been reported that M070 fixes the connections issues, but M100 is the minimum version to be certified with Windchill 11.0.

    PTC is in the process of updating the maintenance release of Creo 3.0 and Creo View 3.0 available on the Academic Software Downloads page. As soon as I've received notification its ready, I will post a general response to all and post a banner on the community.

    My apologies for this mix up, it is completely my fault for not remembering to validate the maintenance version. Hopefully we can get everyone up and running properly with a simple update installation.

    N
    nrensing1-Visitor
    1-Visitor
    January 11, 2017

    Scott,

    Is it likely that the persistence error we ran into is related to the version incompatibility?

    Thanks

    Noa

    S
    smorris1-VisitorAnswer
    1-Visitor
    January 11, 2017

    No, I'm assuming your issue has to do with the database indexes and I'm curious if the restart Alex Ouellet‌ announced the other day might have corrected it.

    Terms & ConditionsCookie settingsAccessibility statement