I am sorry I don't have a direct solve it all answer to this, but I figured
I'd share the 10% information I had on this.
We had the same issue when we upgraded to .NET 1.1.
I don't remember too much about how we fixed it (though I can find out), but
I clearly remember that the crystal runtime wasn't properly being
distributed even though we had a proper setup and deployment created MSI. I
remember we had to painfully find each dll one by one and replace it and see
what it did.
As a quick shortcut, try finding all the crystal runtime dlls
(C:\WINDOWS\CRYSTAL?), and put them in the same directory as the
application - see if that works.
If you get tired of banging your head on this, I can ask a guy who I work
with who actually found the solution to this.
- Sahil Malik
Independent Consultant
You can reach me thru my blog - http://dotnetjunkies.com/WebLog/sahilmalik/
> Error is: " File or assembly name CrystalDecisions.CrystalReports.Engine, or
> one of its dependencies, was not found.
[quoted text clipped - 27 lines]
> > >
> > > Wayne
Wayne Wengert - 21 Jun 2004 19:16 GMT
Sahil;
Thanks... I'll try that.
Wayne
> I am sorry I don't have a direct solve it all answer to this, but I figured
> I'd share the 10% information I had on this.
[quoted text clipped - 50 lines]
> > > >
> > > > Wayne
Wayne Wengert - 22 Jun 2004 15:43 GMT
That didn't help! Bummer.
Wayne
> Sahil;
>
[quoted text clipped - 65 lines]
> > > > >
> > > > > Wayne
ambshah - 28 Jul 2004 18:47 GMT
try the support group at businessobjects the latest
owners of crystal
this is a known issue.
1) ms_vcrt dlls + stl dlls are required
2) if you installed VS on top of Crystal , Reinstal Crystal
3) use the MSM files for 2003
hth
Ambrish
www.Simplesoftconsultants.com
> That didn't help! Bummer.
>
[quoted text clipped - 72 lines]
> > > > > >
> > > > > > Wayne