RE: Problem in deployment using MSI



Hi Sajid,

We have a setup similiar to what you have. All the DEV machines are running
on XP and productions/Test servers on Windows 2003. We constantly export
MSI's from dev machines and install it on 2003 servers. So, I can tell you
for sure the problem you are facing is not due to XP --> 2003 OS difference.

I did some search and find out this link
http://blogs.msdn.com/windows_installer_team/archive/2005/11/02/486616.aspx
if you look at Question 7, its exactly what you are getting (but the MSI
creation process is not with BizTalk)

That tells me, there is some problems in the way files are added to your
package. Are you additing any additional resources to your application apart
from your normal BizTalk deployment, things like additional dll's, batch
files etc via "Add Resource". I can suggest you one thing.

1. Remove all the resources from the application
2. Deploy the project via VS, so you'll get all the BizTalk related
resources into the application, then
3. Add additional resources one by one.

Let us now, whether this helped you.

--
Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]


"Sajid" wrote:

Hi All,

When deploying a biztalk app. which was developed on a win 2003 server
machine, exposed as web service, to another 2003 server machine, we faced no
problems. We just exported the MSI, ran it on the server machine, imported it
in the applications. It created all the bindings and the virtual directories
for us and it was a real breeze.

But for a project developed on a XP machine, we exported several MSI's, and
ran them on the 2003 server only to be greeted with the same error every time:

The file’_1B55FD57536C453C9E2B57589DB1441’ cannot be installed because the
file cannot be found in cabinet file ‘_7189CC22058D58A4179EACDB37865787’.
This could indicate a network error, an error reading from the CD-ROM, or a
problem with this package.

The projects and export process dont have any errors and are running fine on
the dev. machine. We dont know why this must be happening, the same error for
all the MSI's, perhaps it has something to do with XP, as the successful
deployment was developed on a 2003 server machine and deployed on another
2003 server machine and it didn't created any problems. Kindly help us in
this regard.


Thanks & Regards

Sajid

.



Relevant Pages

  • Re: Problem in deployment using MSI
    ... Install just BizTalk assemblies from VS ... Yeah we have resources other then the biztalk ... added it to the Resources after deployment bcz when we make a MSI for the ... which was developed on a win 2003 server ...
    (microsoft.public.biztalk.general)
  • Re: Problem in deployment using MSI
    ... Install just BizTalk assemblies from VS ... Yeah we have resources other then the biztalk ... added it to the Resources after deployment bcz when we make a MSI for the ... which was developed on a win 2003 server ...
    (microsoft.public.biztalk.general)
  • RE: Can not view network neighborhood
    ... I am interested in accessing the resources on the ... I need to access SQL server, and a "file share" which are on ... Do I still need to VPN directly to the SBS? ...
    (microsoft.public.windows.server.sbs)
  • Re: [Xen-devel] Re: [ANNOUNCE] Xen high-performance x86 virtualization
    ... >> that each virtual machine only gets the resources that its sponsor ... This allows companies providing virtual servers to ... Ensim's 'private virtual server' product is the most complete ... even in the buffer cache. ...
    (Linux-Kernel)
  • Re: Changing Node & Virtual IPs for Print Server Cluster
    ... It's a clustered print server. ... Cluster Node 1 Name: cluster1a.domain.com ... Move all resources to Node A. ... IP addresses for all virtual servers including the cluster itself. ...
    (microsoft.public.windows.server.clustering)