2009 Autoloader: Could not validate files

[Anonymous]

Well, it says it's validating the files. All 10,793 of them. And it takes
a good three hours to do it. Then it hangs on file 10,793, with an
amazingly unhelpful error message. No clue what's wrong; you just wasted
most of the day trying to get your dataset loaded. Wanna try again?

I'm just ranting; I already found SLB 3D's post, and suspect that I'm having
similar problems, since our title blocks have a bitmap, and even though it's
in a folder that's clearly mapped in the project file, Inventor looses track
of the thing on a regular basis.

Why, if the dataset will scan, will it not validate? And why does the silly
thing burn hours of time to get to the point where it will tell you that
sorry, you're out of luck; it's not going to do it's job after all? I had
hopes that Vault would show some improvement for 2009, but Autoloader still
has the feel of an application that was farmed out to Junior's Code, Bait
and Tackle. I have to go into the Windows registry and *create my own
entries* just to get it to make a log file??

Yeesh.

Walt

[Anonymous]

Well, it seems that there were two assembly files--two files out of almost
11,000--that Autoloader's validation process had some kind of problem with.
That was enough to cause the entire two-and-a-half-hour process to fail
without any explanation whatsoever. I opened those two files...nothing
unusual about them, so I poked and prodded them a little, saved them, and
(sigh) ran autoloader again. Half-hour to scan, then another 2.5 hours to
validate and...oh joy; everything's all ducky, and the files pushed up to
the vault.



I'm appalled at the amateurish implementation of this application. Once
again, it creates no log by default unless the entire process completes
successfully--and at that point what would you need the log for? In order
to get it to make a log file that might actually be useful you actually have
to go in and manually add entries to the Windows registry. What kind of
application makes you do that?



Here's a wild thought: We could maybe do this thing--let's call it a dialog
box. Yeah! A dialog box for application preferences. I know it's a little
out of the box, but hang with me here...if you had one of those, you could
put a little check box option thingy in there, to tell the software to write
a log file as it goes, instead of only creating one if it won't be needed
anyway. An Application Preferences dialog box. It's a radical idea, but I
think it's time has come.



Even better, how about the software itself not discarding the last several
hours worth of work for the sake of two bloody files that don't have
anything wrong with them, but somehow can't be validated anyway? How about
some real-world error handling capability? Something a little better than
"hey, I know I couldn't do my job, and I'm not going to tell you why, but at
least I didn't actually crash".



Oh, and go check out the process (it's buried on Autodesk's website) if you
want to call your main vault folder something other than "designs". An XML
file in the vault directory? What kind of funky programming is that? It's
like being back in 1986, trying to get a cheap Sound Blaster knockoff to
work in a DOS/Windows machine.



Autodesk, you're shameless, putting out junk like this.



Walt

[Anonymous]

Sounds like we need a response from Otto Deskus on how much fun it is to
laugh and play with our vault today!!!!!

Gary

"Walt Jaquith" wrote in message
news:5897387@discussion.autodesk.com...
Well, it seems that there were two assembly files--two files out of almost
11,000--that Autoloader's validation process had some kind of problem with.
That was enough to cause the entire two-and-a-half-hour process to fail
without any explanation whatsoever. I opened those two files...nothing
unusual about them, so I poked and prodded them a little, saved them, and
(sigh) ran autoloader again. Half-hour to scan, then another 2.5 hours to
validate and...oh joy; everything's all ducky, and the files pushed up to
the vault.



I'm appalled at the amateurish implementation of this application. Once
again, it creates no log by default unless the entire process completes
successfully--and at that point what would you need the log for? In order
to get it to make a log file that might actually be useful you actually have
to go in and manually add entries to the Windows registry. What kind of
application makes you do that?



Here's a wild thought: We could maybe do this thing--let's call it a dialog
box. Yeah! A dialog box for application preferences. I know it's a little
out of the box, but hang with me here...if you had one of those, you could
put a little check box option thingy in there, to tell the software to write
a log file as it goes, instead of only creating one if it won't be needed
anyway. An Application Preferences dialog box. It's a radical idea, but I
think it's time has come.



Even better, how about the software itself not discarding the last several
hours worth of work for the sake of two bloody files that don't have
anything wrong with them, but somehow can't be validated anyway? How about
some real-world error handling capability? Something a little better than
"hey, I know I couldn't do my job, and I'm not going to tell you why, but at
least I didn't actually crash".



Oh, and go check out the process (it's buried on Autodesk's website) if you
want to call your main vault folder something other than "designs". An XML
file in the vault directory? What kind of funky programming is that? It's
like being back in 1986, trying to get a cheap Sound Blaster knockoff to
work in a DOS/Windows machine.



Autodesk, you're shameless, putting out junk like this.



Walt

[Madhan_T]

Hi, Walt,

This is indeed a great feedback and we sincerely appreciate for expressing your concerns. We are looking in to this and we would be addressing this in future release. It would be good if you could participate in our beta programs and send us the feedback.


Regarding failure of two assemblies that you had mentioned, I feel that it could be related to the files being in older version and never migrated. But we wanted to take a look at what exactly has caused this. Please drop me an email to “madhanagopal.t@autodesk.com ”and we would get in touch with you.

Your idea about editing BUU.xml via Options/Preferences is good and we would consider this for future release.

Thanks again for your feedback.

Regards,
Madhan

[Anonymous]

We ran the autoloader, firstly on ipt's, sorted the issues.
then iam's, sorted the issues
then ipn's & idw's, and sorted the issues.
(Also ran scriptpro to sort the "older than R14 dwg" files)
Which has taken us weeks & weeks.
Came to run the scan on all file types, and it has brought up all the issues again..........FFS, we cant be doing all that again, there must be another way. Something is wrong!
Help/suggestions please.

Precision WorkStation 390

Windows XP Professional (5.1, Build 2600) Service Pack 2

Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz (2 CPUs)

3582MB RAM

NVIDIA Quadro FX 3500
DirectX Version: DirectX 9.0c (4.09.0000.0904)
Driver Version: 6.14.0010.8426 (English)

inventor 2008 sp2
vault build 12.1.145.0
Atuocad 2008 sp1

Autodesk Design review:
build version 4.1.0.87
DWF toolkit 7.3.0.142
Whip! toolkit 7.8.601.142
Heidi 9.0.54.0

[Madhan_T]

Hi,

Could you please log a Support Request with us if you are on Subscription? Alternatively, please request your reseller to log a Support Request for you. We will contact you and help you to get these issues resolved.

Regards,
Madhan

[Anonymous]

Logged, with VAR.

I didn't mention that when I open the files, they open fine, without issues or message boxes.

[Anonymous]

With a little help from our VAR we got to the next step and started the validating process, (through the night) with our 25,023 files. Greeted with the silly error message this morning. Autoloader hanging there on 25,023 of 25,023 files......What now? how did you know where to find where those 2 assemblies were? What do i do now?

[Anonymous]

Couple of years ago it was impossible to upload large amounts of data to the vault.

So the program Autoloader was introduced, and still they cant get it right! This is ridiculous!
Hours and hours of wasted time!
I can see so much more wasted time, doing this in smaller chunks to find out the issues.

This is what I have come to expect from Autodesk products..

[hmhaga]

Old thread, but...

I have exactly the same problem with Autoloader 2009, it fails with "could not validate files" in 99% of the time - at the very last file (most probably not the last file which is causing the problems).
However, if I click "Back" and re-run the copy and file redirection" process - it completes successfully!

I'm not that impressed with Autoloader either... it has cost a fortune 😉

[polo.zhenshi]

Hi,
Can you send us the log file of autoloader, base on
http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=7777543&linkID=9261340, this will help to diagnose the issue. Which version of Inventor are you using? Have you tried any other folder with inventor data?

Regards,
Polo Message was edited by: Polo Shi(Autodesk)

[OBarre]

The link you posted is not working...
And I'm having the same problem as these guys.

[polo.zhenshi]

To create a detailed log file
1.On the Start menu (Windows), click Run.
2.In the Run dialog box, enter regedit.
3.In the Registry Editor, locate the following key:
HKEY_CURRENT_USER\Software\Autodesk key
4.If this key does not exist, create a new key called Autoloader.
5.Under Autoloader, create a new key called Current Version.
6.Create a new DWORD value named LogLevel and set its value to 2.
When you run the Autoloader, a log file named AutoloaderTrace.log will be created in the C:\Documents and Settings\[username]\Local Settings\Temp folder.

Regards,
Polo

[marshallw]

Madhan,

So here we are in Autoloader 2013 & NONE of the issues have been addressed (4 years)

Still get the same silly "Cannot Validate" error. No problems with the scan or with opening files in Inventor prior to attempting upload via Autoloader. Typical.

Bravo Autodesk!

[Bryan79]

2014  and im having the same problem Could not validate file.

[jacoj]

Hi All,

same issues here,

any idea how to get pass the not validating issue,

a full day of validation wasted,

anyway to force continue the uploads,

Autodesk needs to streamline this process,

all errosr should report in the scanning process so we can sort the issues out before validation,

any help appreciated

[JamesMabe4219]

Well here it is 2015 and still no Log file I can find that tells me ... and an old post gave  regedit info on how to get an advance log file but the keys seemed to have changed.... maybe there is somewhere in Autoloader where I can get an advance log file so I know which file our of a couple thousand is the issue...anyone help please. I dont remember if it was 2 am this morning or 2 am yesterday morning it started to go thru the hours long process...