pack n go leaving behind a couple of files?

[Anonymous]

I ran pack-n-go on an assembly yesterday evening and today when I go to open
the assembly that was output it is missing two parts? Anybody seen this
before? Where do I look for the cause?

gcooper

[Anonymous]

Yes, I've seen it happen. I didn't have time to search for a cause, I just
copied the missing files manually.

Mike

"gcooper" wrote in message
news:930F0CA12597A9594CAC76FA252354D9@in.WebX.maYIadrTaRb...
> I ran pack-n-go on an assembly yesterday evening and today when I go to
open
> the assembly that was output it is missing two parts? Anybody seen this
> before? Where do I look for the cause?
>
> gcooper
>
>

[Anonymous]

I've seen it happen too.

"Mike Maenpaa" wrote in
message news:C82E80B47B4AB5E605C32C75194F76F6@in.WebX.maYIadrTaRb...
| Yes, I've seen it happen. I didn't have time to search for a cause, I just
| copied the missing files manually.
|
| Mike
|
| "gcooper" wrote in message
| news:930F0CA12597A9594CAC76FA252354D9@in.WebX.maYIadrTaRb...
| > I ran pack-n-go on an assembly yesterday evening and today when I go to
| open
| > the assembly that was output it is missing two parts? Anybody seen this
| > before? Where do I look for the cause?
| >
| > gcooper
| >
| >
|
|

[Anonymous]

> I ran pack-n-go on an assembly yesterday evening...

It would be helpful to know a few things:

- was the assembly migrated?
- if so, from what to what?
- on careful inspection are the filenames included in the assembly correct?

We have seen cases the involve files the include the string: ".newver" which
is a temporary string that gets added during some internal migration but
which is never supposed to see the light of day.

There is currently an open bug logged against this - so the answer is "yes,
we've seen it but no, we haven't figured it out yet..."

If any of you have a data set which you can repeatably attempt to
pack-and-go which will routinely not pack everything, please contact me.

Thanks!

Gary R. Smith
gary.r.smith@autodesk.com

[Anonymous]

> - was the assembly migrated?

I believe parts of this assembly were generated as far back as 5.3, though
everything has been migrated to 7. So I guess the answer is "yes".

> - if so, from what to what?
> - on careful inspection are the filenames included in the assembly
correct?

I did not see any anomalies.

>

I will attempt to generate a data set for you, this is a large assembly. Do
you need both sets or just the parent?

Thanks for responding.

gcooper


"Gary R Smith (Autodesk)" wrote in message
news:5EA0A2F7F0F87D7C76734C3A769B200E@in.WebX.maYIadrTaRb...
> > I ran pack-n-go on an assembly yesterday evening...
>
> It would be helpful to know a few things:
>
> - was the assembly migrated?
> - if so, from what to what?
> - on careful inspection are the filenames included in the assembly
correct?
>
> We have seen cases the involve files the include the string: ".newver"
which
> is a temporary string that gets added during some internal migration but
> which is never supposed to see the light of day.
>
> There is currently an open bug logged against this - so the answer is
"yes,
> we've seen it but no, we haven't figured it out yet..."
>
> If any of you have a data set which you can repeatably attempt to
> pack-and-go which will routinely not pack everything, please contact me.
>
> Thanks!
>
> Gary R. Smith
> gary.r.smith@autodesk.com
>
>

[Anonymous]

In my case, the files were created in 5.3. Were migrated into 6, coworker
worked on them in 6 and I mimgrated into and worked on in 7.

Filenames appear to be correct.

I have .zipped all files in the project. It's about 15.6MB. I would rather
not post this publicly, please inform me of where I can post this.

Steps taken to reproduce this:

1. Pack and Go the .IDW to a single folder.

2. Activate the PnGoed .IPJ

3. Open the top level .IAM. This is when I'm informed of the missing files.

This is assembly also contains another curious problem, which I have pointed
out on the newsgroup

here: news:F61FE36C9964CAFEE937FD9987CFD6A7@in.WebX.maYIadrTaRb

Thanks for your help!

Mike




"Gary R Smith (Autodesk)" wrote in message
news:5EA0A2F7F0F87D7C76734C3A769B200E@in.WebX.maYIadrTaRb...
> > I ran pack-n-go on an assembly yesterday evening...
>
> It would be helpful to know a few things:
>
> - was the assembly migrated?
> - if so, from what to what?
> - on careful inspection are the filenames included in the assembly
correct?
>
> We have seen cases the involve files the include the string: ".newver"
which
> is a temporary string that gets added during some internal migration but
> which is never supposed to see the light of day.
>
> There is currently an open bug logged against this - so the answer is
"yes,
> we've seen it but no, we haven't figured it out yet..."
>
> If any of you have a data set which you can repeatably attempt to
> pack-and-go which will routinely not pack everything, please contact me.
>
> Thanks!
>
> Gary R. Smith
> gary.r.smith@autodesk.com
>
>

[Anonymous]

Anyone who would prefer to burn a CD and snail mail me:

Autodesk
attn.: Gary Smith
7995 SW Mohawk
Tualatin, OR 97062

Thanks!

G

[Anonymous]

Gary,
I used Pack-n-go to clean up a messy project a month ago and saw problems.
I'll try and find some time next week to duplicate what I did - I still have
the source folder intact.
If it still behaves badly, I'll send you a CD.

"Gary R Smith (Autodesk)" wrote in message
news:12C85C0F36E405CA24867FD0FAEEC563@in.WebX.maYIadrTaRb...
> Anyone who would prefer to burn a CD and snail mail me:
>
> Autodesk
> attn.: Gary Smith
> 7995 SW Mohawk
> Tualatin, OR 97062
>
> Thanks!
>
> G
>
>

[reeds_93me]

Sorry to chime in so late, but one other thing to investigate besides the (semi-)known issue of p'n'g with older versions of IV is your project structure. There is a checkbox on whether you want LIBRARY parts to go with you or not. This may not be your problem, but it was a handy feature I stumbled across recently and you may want to check into that as well.

- Reed