Autoloader 2008 validate error ?

[leeroy]

Using Autoloader 2008 with hotfix, generates "unable to validate file" towards the end of the copy pass.

Any one have any ideas?

[leeroy]

Opps. We are running against Inventor files. Most of which are 2008. However, many of them may go back 3 or 4 versions.

[Anonymous]

You might also want to try to post this in the Vault NG

I have seen this a few times - you probably want to turn on the "advanced
logging" and post the log to the Vault newsgroup and we'll take a look at
it...

turn it on here.

http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=7777543&linkID=9242498

--
Thank You,

Brian Roepke
Manager, Customer Success, Data Management
Autodesk, Inc.

wrote in message
news:5693464@discussion.autodesk.com...
Opps. We are running against Inventor files. Most of which are 2008.
However, many of them may go back 3 or 4 versions.

[leeroy]

Thanks we will try that. We were tossing around the possibility that maybe due to some older version files. We're in the process of getting ready to run the scheduler utility to migrate everything to IV 2008 to see if that would resolve it since we had no other ideas.

[Anonymous]

Unmigrated files won't cause issues - Autoloader will support back to 5.3
and the scan phase will report issues. This isn't it.

When I have seen this is is due to a fairly complex mapping on the front end
with the original project file. sometimes if there are too many search
paths or if there are too many files that were manually "reorganized"
autoloader can't figure out how to put them back together after it creates
it's own "autoloader" project file...

so... I really suggest you run that verbose logging and post it over. a
migration probabaly won't fix it...

(however... if it does it means that the later of the above is true... where
it just need to save the new references from a reorgainzation.)

--
Thank You,

Brian Roepke
Manager, Customer Success, Data Management
Autodesk, Inc.

wrote in message
news:5695223@discussion.autodesk.com...
Thanks we will try that. We were tossing around the possibility that maybe
due to some older version files. We're in the process of getting ready to
run the scheduler utility to migrate everything to IV 2008 to see if that
would resolve it since we had no other ideas.