The following error(s) occurred.
-Could not find a part of the path 'C:\Documents and
Settings\Administrator\Local
Settings\Temp\tmp12\File\17-CopyAdapterFiles.vbs'.

i look to the path and see:

'C:\Documents and Settings\Administrator\Local
Settings\Temp\tmp12\File\16-CopyAdapterFiles.vbs'

the same mismatch occurs on install.

the vbs script is called from a pre_script.bat

any ideas??

btw: what´s the right way to deploy? first import and then install or
opposite??

thanks in advance!

lars

[ Post a follow-up to this message ]

The order of the Installation and Import operations generally should not
matter.  What you are seeing may be a related to a bug in the Beta version.

Most likely reason for error is that the VB script file
(CopyAdapterFiles.vbs) has gone through the following:

1. Added to BizTalk Server 2006 Beta-1 version
2. Exported into an MSI and then imported at least once
3. Afterwards the BizTalk Server 2006 beta version has been upgraded
4. Then at some point the current MSI is created (steps 3 and 4 can be
swapped)

Due to a Beta-1 bug, there can be a mismatch between the app id associated
with the serialized script resource and the app id of the packed
application.

The fix will be to delete the script and add it again to the application.
Actually, to be on the safe side, all the File, PreProcessingScript, and
PostProcessingScript type resources should be deleted and added again.
Afterwards, the MSI needs to be created again and it should work.

Had the system you are working on previously used a beta version, or was
the application imported from a beta version?

Regards,
Doug Girard [MSFT]

Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>Thread-Topic: import msi failed
>thread-index: AcaEElCLRr+C2DMbT92pgSOBL8gleQ==
>X-WBNR-Posting-Host: 213.61.227.216
>From: examnotes <lwi@discussions.microsoft.com>
>Subject: import msi failed
>Date: Tue, 30 May 2006 10:56:02 -0700
>Lines: 22
>Message-ID: <F5A62768-0C72-4A12-A67D-072607EC2F61@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>	charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.biztalk.general
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:37920
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>The following error(s) occurred.
>-Could not find a part of the path 'C:\Documents and
>Settings\Administrator\Local
>Settings\Temp\tmp12\File\17-CopyAdapterFiles.vbs'.
>
>i look to the path and see:
>
>'C:\Documents and Settings\Administrator\Local
>Settings\Temp\tmp12\File\16-CopyAdapterFiles.vbs'
>
>the same mismatch occurs on install.
>
>the vbs script is called from a pre_script.bat
>
>any ideas??
>
>btw: what´s the right way to deploy? first import and then install or
>opposite??
>
>thanks in advance!
>
>lars
>

[ Post a follow-up to this message ]

thanks a lot!

after refreshing the script ressources and rebuild the msi it works fine.

a use the bts deved from msdn download. no beta version was installed before
.
i moved some ressources from one to a new application without refreshing the
ressources. that was the reason.

doug, please.....would you have a look to my other thread "post import
scripting".
is makes me tons of headache.


thanks!

lars

"Doug Girard [MSFT]" wrote:

> The order of the Installation and Import operations generally should not
> matter.  What you are seeing may be a related to a bug in the Beta version
.
>
> Most likely reason for error is that the VB script file
> (CopyAdapterFiles.vbs) has gone through the following:
>
> 1. Added to BizTalk Server 2006 Beta-1 version
> 2. Exported into an MSI and then imported at least once
> 3. Afterwards the BizTalk Server 2006 beta version has been upgraded
> 4. Then at some point the current MSI is created (steps 3 and 4 can be
> swapped)
>
> Due to a Beta-1 bug, there can be a mismatch between the app id associated
> with the serialized script resource and the app id of the packed
> application.
>
> The fix will be to delete the script and add it again to the application.
> Actually, to be on the safe side, all the File, PreProcessingScript, and
> PostProcessingScript type resources should be deleted and added again.
> Afterwards, the MSI needs to be created again and it should work.
>
> Had the system you are working on previously used a beta version, or was
> the application imported from a beta version?
>
> Regards,
> Doug Girard [MSFT]
>
> Note: This posting is provided "AS IS" with no warranties, and confers no
> rights.
> -------------------- 
>
>

[ Post a follow-up to this message ]

Glad to hear it.  I'll take a look at the other thread.

Regards,
Doug Girard [MSFT]

Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>Thread-Topic: import msi failed
>thread-index: AcaEjjoNX1GWBKIqQXWE3YtNzD142g==
>X-WBNR-Posting-Host: 213.61.227.216
>From: examnotes <lwi@discussions.microsoft.com>
>References:  <F5A62768-0C72-4A12-A67D-072607EC2F61@microsoft.com>
<9RBI6lEhGHA.1740@TK2MSFTNGXA01.phx.gbl>
>Subject: RE: import msi failed
>Date: Wed, 31 May 2006 01:43:02 -0700
>Lines: 97
>Message-ID: <B5C0378E-C247-45E8-9D62-BE87C879555D@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>	charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.biztalk.general
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:37931
>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>thanks a lot!
>
>after refreshing the script ressources and rebuild the msi it works fine.
>
>a use the bts deved from msdn download. no beta version was installed
before.
>i moved some ressources from one to a new application without refreshing
the
>ressources. that was the reason.
>
>doug, please.....would you have a look to my other thread "post import
>scripting".
>is makes me tons of headache.
>
>
>thanks!
>
>lars
>
>"Doug Girard [MSFT]" wrote:
> 
version.[vbcol=seagreen] 
associated[vbcol=seagreen] 
application.[vbcol=seagreen] 
no[vbcol=seagreen] 
or[vbcol=seagreen] 
>

[ Post a follow-up to this message ]