Stats

  • Locked Locked
  • Replies 3
  • Subscribers 166
  • Views 4643
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ERROR(ORCAP-32007): Netrev failed -- only when design is on Google File Stream drive

bowerymarc

Anyone else run into this and have a solution?

I have an orcad sch on a google filestream drive, and trying to create netlist and update board file:

(note the output directory also on google filestream)

I get:

Digging in the logfile, there are two places where files fail to write:

Performing a partial design check before saving.
Failed to open file 'G:/MY DRIVE/10-REV001/allegro/#Taaaaac30420.tmp'.

netrev run on May 17 10:34:12 2019
DESIGN NAME : 'REV001'
PACKAGING ON Feb 15 2016 19:53:59


2 errors detected
No oversight detected
No warning detected

cpu time 0:32:06
elapsed time 0:00:19

File save problem: The requested operation cannot be performed on a file with a user-mapped section open.

--- and then later ----

------ Oversights/Warnings/Errors ------


#1 ERROR(SPMHNI-235): Error detected saving design.

ERROR(SPMHNI-234): Cannot write drawing, 'G:/MY DRIVE/10-REV001/allegro/REV001.brd' out to the directory: 'Error while saving the drawing.'.

#2 Run stopped because errors were detected

When I copy the whole thing to a directory in my 'Documents' directory (on C: as usual) then the whole thing works with no errors.

So my two theories are that 

1) non-NTFS file system somehow screws it up

2) non C: directory somehow screws it up

3) what's really going on (of which I have no idea!)

The right answer is probably 3 ;)

  • oldmouldy

    You don't mention anything about which version of the tools you are using but, I would say, the first thing to do is change the mapping point for the drive to remove the space from the folder name, as in, G:\My Drive isn't going to work but G:\My_Drive (for example) likely would. This has certainly been an issue in older versions of the tools. I don't think that 1) and 2) are likely to be factors if Windows can read / write the target location for the files.

  • jc teyssier
    in reply to oldmouldy

    I agree with oldmouldy: space in folder or file names have to be avoided.

    Such as @ , é, &, µ and so on...

  • bowerymarc
    in reply to oldmouldy

    Sorry for not mentioning, version 16.6.  And, I have shortened the names to protect my client, but there were spaces in the file names in both the drive stream and non-drive stream version.  So that's not it, I thought the same thing at first.  Also, windows 10, totally updated, english version, no language packs.  No strange characters in the path names.   I should also mention, for those who don't know, that when you copy a file from NTFS to DriveStream you'll often (and in the case of the .brd file) get a warning that 'properties of the file won't be copied'.  Could be part of the issue?

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.