Re: Problem in deployment using MSI

I am still waiting for any help from the experts out there, this is a very
serious issue for us since we'd shortly need to start deploying our
applications to the production server and this can really halt us in that
regard.


Regards,
Sajid

"Saravana Kumar" wrote:

I'm experiencing problems with the news reader, hope this message is posted
only once.

Hello Sajid,

I personally never experienced this problem before. If I were in your shoes
I would try to do the following.

1. Clear all the resources from the application
2. Install just BizTalk assemblies from VS
3. Create MSI and Install it in target machine.

If the above steps succeed without any issue
4. Add first additional resource, create MSI and install it in the target
machine.

I just repeat step 4 with all my available resource.

This is just my theoretical suggestion

"Sajid" <Sajid@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9A46FE3D-CD4E-41DC-97D8-039249FCEC02@xxxxxxxxxxxxxxxx
Saravana,

Thanks alot for your time, Yeah we have resources other then the biztalk
resources. We mostly have a component used for our biztalk projects and we
added it to the Resources after deployment bcz when we make a MSI for the
project, it will automatically GAC it on the target machine. You are
saying
the problem can be because of that.

But what I am not able to understand in your reply is you are saying that
we
deploy that project again using VS and then add resources one by one.
Thats
what we've done, so whats wrong with that. Also we've tried by adding a
bindings file as a resource as well as not adding it as a resource, so
that
it goes by default on target machine. In both cases greeted with same
error.
Kindly tell me what I am not able to understand.


Thanks & Regards,
Sajid

"Saravana Kumar" wrote:

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
    ... deployments directly using Visual Studio to our Staging Server, ... 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 ...
    (microsoft.public.biztalk.general)
  • Re: Errors with Nant deployment.
    ... BizTalk Solution Developer ... Microsoft Certified Technology Specialist: BizTalk Server 2006 ... I am new to Biztalk and helping out on a deployment when we ... "The database BizTalkMsgBoxDb_2S on the server ENTAAP271S\INST4 is ...
    (microsoft.public.biztalk.general)
  • Re: Problem in deployment using MSI
    ... this time we chose to export a fresh biztalk ... obviously 2003 server is the same. ... Clear all the resources from the application ... MSI's from dev machines and install it on 2003 servers. ...
    (microsoft.public.biztalk.general)
  • Errors with Nant deployment.
    ... "The database BizTalkMsgBoxDb_2S on the server ENTAAP271S\INST4 is ... Develpoment machine is running Biztalk SP2, deployment machine is SP1. ...
    (microsoft.public.biztalk.general)
  • Re: SQL Server does not exist or access denied
    ... This is probably because the BizTalk database that the project wants to ... then "Deployment". ... "Server" specified within this section. ... The error message showed "SQL Server does not exist or access ...
    (microsoft.public.biztalk.general)