Windburn reboot log

[Patriot_1776]

Ok, every time I have to kill the process and reboot I'm going to post up. So far, second time today.......

[Patriot_1776]

Whoops! Crashed again just trying to do a simple search for a component. Yay.......

[Patriot_1776]

WooHoo! Windburn is hung up again. Killed the process. wow.....

[Patriot_1776]

WooHoo! Windburn hasn't crashed yet this morning! Oh, wait.....I haven't turned it on yet........

[Patriot_1776]

Crasshed again, WooHoo! Way to go guys!

[Patriot_1776]

Crashed again, just trying to do an update of a few file. Man, is this the most awesome software or what? I can get it to crash on command every time. BRILLIANT!

[Patriot_1776]

WooHoo! Completely bombed again, blew me completely out of Pro/E and everything this time, just trying to change some layers. Nice!

Maybe we should change "creo" to "Crasho"?

[Patriot_1776]

Windburn blew up again, forcing me to kill the process again, just trying to "update" 2 objects.

[Patriot_1776]

Bombed again. Awesome..........

[TomD.inPDX · Accepted solution]

Fire the I.T. guy and call PTC support ...oh wait, did I get that backwards? ...again.

[Patriot_1776]

Bwahahaha!

[Patriot_1776]

WooHoo! Done blowed up again!

[Patriot_1776]

Wow, blowed up yet again. Cool. That's "enhanced" productivity for ya!

[Patriot_1776]

wow, Pro/E's locked up just trying to get INTO Windburn. Man, is it my lucky day or what?

[Patriot_1776]

Whoa, hey, looky, windburn crashed again. Surprise!

[Patriot_1776]

Crashed again. Nice......

[Patriot_1776]

Crashed a couple more times. Finally had to completely blow away my cache and a few other files in that directory. Nice huh? This is the second time I've had to do this in the last 2 months or so. I gotta say the robustness of the software is somewhere around the durometer of tap water....

[Patriot_1776]

WooHoo! Had to kill the process again. Awesome!

[dhermosillo]

Wow! 10 days without a reboot? We're still rebooting every day since implementation.

[Patriot_1776]

WooHoo! Another one!

Yeah, man, this is some great and reliable software, huh? (Sarcasm....)

[Patriot_1776]

Been trying to check in a dwg since last night. No go. One Windburn-created issue after another. Not I had to kill it again. This is an assembly with only a coupe hundred part. Man, I can't even IMAGINE the nightmare of trying to get a REAL large assembly into and out of Windburn. You know dumping this garbage and simply saving to a network drive sounds like a REAL good idea for our company right about now. Seriously going to have to write an e-mail to the boss and tell how bad things are with this.

[Patriot_1776]

Awesome! Another crash! some sort of stupid Javascript error or something. Nice. Great idea running a vaulting system through the LEAST secure and reliable network in the world.

[Patriot_1776]

I've spent 8 hours so far and STILL can't get the dwg/assy back into Windburn. There's only about 360 models in this assembly. Funny how much trouble this is with Windburn, vs. when I worked on an assembly on the old PDMLink back in the late '90's that had over 1,400 models in it and had NO problems. That's what I call progress!

[Patriot_1776]

WooHoo! Bombed again.......

[Patriot_1776]

Done blowed up again. Surprise! (No, not really.....)

[Patriot_1776]

Awesome, blew up again. This is actually going to work out well, I think. I'm going to show this to my boss and tell him this is what happened when we switched from Intralink to Windchill, and how much time has been was just recently.

[Patriot_1776]

Had to reboot the POS 3 times in about 2 hours.

It took over 2 hours to check in the files I needed (dwg and referenced models). Needless to say I'm infuriated. I had to trick the system by first doing a back up of the dwg (and by default all the files) to a local directory. Then I deleted the files form the workspace. Then I checked out all the files again (thank God it was an assembly of less than 10 parts!), but didn't open the dwg. Then I opened the dwg FROM THE LOCAL DRIVE where I did the back up. Made a couple small changes to make sure Windburn saw it was changed, and it actually checked in ok. Amazing that you have to use a LOCAL DRIVE in place of Windburn. I'm wondering if we shouldn't always do this and just avoiding using Windburn altogether........it sure would save us tons of $$ in maintenance and licensing fees.

[TomD.inPDX]

Okay, silly question: What is the justification for using WC? Who is using the downstream data?

[Patriot_1776]

PTC took a great product, Intralink, which I think did a very good job of storing and linkig data, and since they acquired Windchill from another company, decided to phase Intralink out and replace it with the monstrosity that is Windchill. The justification for it is PTC rams it down your throat (or, in reality, UP another orifice) by not supporting Intralink anymore, and by making sure you can't go past WF4 without using it. It's supposed to be like SAP (another nightmare - I've used that too) to try and run just about all your business needs.

[TomD.inPDX]

I've been there with Teamcenter (iman) although properly managed, it atleast worked.

But still... is there any downstream benefit? If you are the end user of your files, maybe a simpler strategy is in order.