Skip to main content
N
nebraska-engr1-Visitor
1-Visitor
June 26, 2019
Solved

Windchill Loading Wheel Spins Forever -- Creo Embedded Browser

  • June 26, 2019
  • 2 replies
  • 9754 views

Previous posts are getting marked as spam? Seems PTC doesn't want the word out that their programs don't work. Oh well, here we go again! Third time at trying to post this. All I'm looking for is help, guys!

 

I am running Creo 5.0.4.0 with Windchill 11.1 on Windows 10.1 This issue was first discovered while I was running Creo 5.0.0.0 on Windows 10.1. After upgrading to Creo 5.0.4.0, the issue was fixed for about a week. Since then, the issue has come back and I cannot check-in through the embedded Windchill browser on Creo.

 

I have run into an issue where I am unable to check-in, revise, or set state of files when the operation is done from my workspace or Windchill Commonspace. However, I am able to check-in by opening parts in Creo, and using the manual File>Check-in option.

 

At first I thought it was just being slow. I let it sit over the weekend and the loading wheel never stopped. It seems like the embedded browser is getting "stuck" after I click the check-in button on the embedded browser.

 

So far, I have tried the following:

* Changed my browser option from internet_explorer to chromium, and back

* Opened a PTC support case

* Cleared/Delete cache files

* Uninstalled Creo, completed fresh install

* Cleared/Deleted appdata in %appdata%/local/PTC and %appdata%/Roaming/PTC on the PC

 

 

None of these attempts have solved the issue. Does anyone here have any ideas?

 

Edit: I've been told this issue is being called the Rotanus of Death. *dun dun dunnn...*

Best answer by nebraska-engr

Issue seems to be caused by a faulty config.pro file.

 

We created another temporary directory for the debugging logs that were requested by PTC support. Only this time, we did not copy over the config.pro file that existed in the original working directory. When we tried to reproduce the error, the issue did not occur.

In order to verify that config.pro was the source of the error, we added it to the new temporary directory and the issue returned. We removed config.pro and the issue was again fixed.

 

When we create new users and install Creo on new devices, we typically copy an existing config.pro and copy it to the new machine. We printed out the config.pro that I use and the one used by mstrahl, and they appeared to be identical. I am still using the same config.pro file with no issues, while mstrahl’s config.pro file seems to be the root cause of the problem.

 

Does anyone here know how or if a config.pro file can become corrupted?

2 replies

J
JHall1-Visitor
1-Visitor
June 26, 2019

@nebraska-engr 

I know Win 10 has played havoc with our  Workgroup Manger for Inventor.  Are you using OneDrive?  If so, you might want to turn off it's folder sharing feature, that seems to have helped us.

Good luck, though, that sounds very frustrating.

James

N
nebraska-engr1-VisitorAuthor
1-Visitor
June 26, 2019

We are using OneDrive, but not for our Windchill files. Our Windchill server is hosted on a virtual server independent of OneDrive.

J
JHall1-Visitor
1-Visitor
June 26, 2019

Hm... well maybe it has nothing to do with your setup, but we found that OneDrive screwed up our local workspaces. This fixed that particular problem, though again, maybe not yours. 

 

Cause

  1. OneDrive activated

Resolution

  1. Turn off the "Files on Demand" feature in OneDrive settings
  2. Reboot the client
N
nebraska-engr1-VisitorAuthorAnswer
1-Visitor
June 27, 2019

Issue seems to be caused by a faulty config.pro file.

 

We created another temporary directory for the debugging logs that were requested by PTC support. Only this time, we did not copy over the config.pro file that existed in the original working directory. When we tried to reproduce the error, the issue did not occur.

In order to verify that config.pro was the source of the error, we added it to the new temporary directory and the issue returned. We removed config.pro and the issue was again fixed.

 

When we create new users and install Creo on new devices, we typically copy an existing config.pro and copy it to the new machine. We printed out the config.pro that I use and the one used by mstrahl, and they appeared to be identical. I am still using the same config.pro file with no issues, while mstrahl’s config.pro file seems to be the root cause of the problem.

 

Does anyone here know how or if a config.pro file can become corrupted?

    S
    21-Topaz I
    STEVEG21-Topaz I
    21-Topaz I
    June 27, 2019

    It's probably not corrupted.  There is just a line in there that is causing the issue.

     

    I suggest removing a few lines at a time and test it.  Eventually you should find what is the problem.

      Terms & ConditionsAccessibility statement