cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

"Error writing file; check disk space or write permissions".

Level 1

"Error writing file; check disk space or write permissions".

I have a user who is occasionally getting the message: "Error writing file; check disk space or write permissions" when he tries to save an assembly. He is able to save individual parts he is working on in the same directory, but not the assembly itself. Plenty of free disk space and looks like his security settings are correct. The odd thing is, the problem only happens occasionally. I noticed he is using an earlier build of Pro/E - M030, going to update him to a newer build, see if that helps.

Anyone else run into this problem?


Windows XP, Wildfire 3.0 - M030.


Thanks,

David

11 REPLIES 11

"Error writing file; check disk space or write permissions".

I have run into this problem as well.

Disk space is fine. Windows XP Professional, WF2, M160

Yes it was sporadic, and it is not doing it now. Curious to see if you
find out anything. We are upgrading to WF4 soon.

Doug

"Error writing file; check disk space or write permissions".

I have experienced this as well. I take it as an indicator that it is time
to restart my computer. That seems to correct the problem.

Erik Olsen



_____

"Error writing file; check disk space or write permissions".

That is interesting. It has been awhile, but I thought we tried that
and it didn't seem to make a difference.

Doug

"Error writing file; check disk space or write permissions".

What I've found is that one (or possibly more) files get set to
"open" or "in use" by Windows on the Server. I discovered this by
viewing my Retrospect Back Up Error Log the first time I got a
back-up error. If Windows thinks a file is in use by another user -
it will not allow the write.
This usually occurs when a Check-In fails for some reason or another
- I specifically remember it happening when I lost a connection when
checking in from home - sure enough - I had a file set to open on
Monday morning and my Check-In would fail.
By rebooting the server - we were able to get windows to "release"
the offending file.
A DB-Shutdown didn't do it - the Server had to be rebooted - a real pain.

Could be the culprit - or maybe not.

Anthony


"Error writing file; check disk space or write permissions".

We used to have that problem a lot when we were on 2001, it happened a
lot less on WF 2.0, have not yet noticed it in the 2 weeks we have been
on WF 3.0 M120.

Usually seemed to die when saving family table parts that were in the
assembly. Also if you hit the save button again immediately it would go
through just fine. We never did get a good answer as to what the issue
might be. Tech support suggested that it was a network issue but I
don't know that I buy that.

Parameters filled out from excel

Has anyone imported IGES or Step into PROE and then imported from excel,
data that would fill out parameters within the proe model?

Parameters filled out from excel

Sorry, I forgot to attach the example file.





Lance Lie
Sr. Tech. Support Eng. II
310.952.4347
310-952.4452 fax
-







"Todd Bagdonas" <->
03/19/2008 03:34 AM
Please respond to
"Todd Bagdonas" <->


To
-
cc

Subject
[proecad] - Parameters filled out from excel







Has anyone imported IGES or Step into PROE and then imported from excel,
data that would fill out parameters within the proe model?

Parameters filled out from excel

Todd,



We have been doing the same steps as Lance for a few years and it works
great. Recently we have replaced the parameters/relations step with
modelcheck used in save mode.





Curtis Odom



CAD Manager

BLACK & DECKER HHI

19701 Da Vinci

Lake Forest, CA 92610

RE: Parameters filled out from excel

Lance & Co,

Is there some reason you wouldn't want the imported files to use the start part files? We use the config.pro option "intf_in_use_template_models" >yes to force STEP, IGES, etc. to use our start part template. That way we've got our parameters, datums, layers in the model. The user just tells Pro/E to open the import file and it automatically contains our standard info. Just a thought.



Rich