Options
SQLPackage error
Brian Donahue
Posts: 6,590 Bronze 1
Hi Neal,
Definitely not. The SQL Packager executables are stand-alone. What I
think is that since you're packaging up a large database, SQL Packager has
divided your package into several dll files and one exe, and the exe can't
find the dlls because you hadn't copied them into the same folder before you
ran the exe.
Please let me know if this is right.
Regards,
Brian Donahue
Red Gate Technical Support
"Neal Makely" <nmakely@ahcinc.com> wrote in message
news:JOF5IA2aEHA.3124@server53...
> I'm testing out SQL Packager for a deployment in the coming weeks. I
> created an EXE with the program, but when I try to deploy it on a test
> workstation, I get the following error:
> "File or assembly name SQLPackageStore1.dll, or one of its dependencies,
was
> not found."
>
> Does this mean that SQL Packager has to be installed on both the creating
> and receiving station?
>
> Thanks.
> Neal
>
>
Definitely not. The SQL Packager executables are stand-alone. What I
think is that since you're packaging up a large database, SQL Packager has
divided your package into several dll files and one exe, and the exe can't
find the dlls because you hadn't copied them into the same folder before you
ran the exe.
Please let me know if this is right.
Regards,
Brian Donahue
Red Gate Technical Support
"Neal Makely" <nmakely@ahcinc.com> wrote in message
news:JOF5IA2aEHA.3124@server53...
> I'm testing out SQL Packager for a deployment in the coming weeks. I
> created an EXE with the program, but when I try to deploy it on a test
> workstation, I get the following error:
> "File or assembly name SQLPackageStore1.dll, or one of its dependencies,
was
> not found."
>
> Does this mean that SQL Packager has to be installed on both the creating
> and receiving station?
>
> Thanks.
> Neal
>
>
This discussion has been closed.
