We have also checked the data deployment through the DDT and we are getting the same issue. I believe that when you are opening the package for data deployment that it is trying to open as readwrite.

Make a package file readonly on your machine. Try to deploy data from said package file. You will get the same error from the DDT.

Error message below:">

We implimented the recommendations you explained. We are not having an issue with the package file being open but that the file cannot be opened from a read only drive. If I make my directory "with the package file" on the harddisk readonly, I get the same error as if it were on a DVD.

This happens when we try to deploy data, not metadata from same package file.

What do you think about this error ?  

TIA

Kenneth

Actually this isn't an issue. There is another thread or two out here about this, but it has to do with the access to the PKG file already being open via the previous process. Just FYI, this is something that we do as well and so I am very confident in this process.



One thing that you can do to make sure that the issue is resolved is to totally close the DatabaseMigrator class and re-created it and re-open the package. So when the meta-data is completed, you will close the migrator, re-create it and then start the data deployment phase. This is one way to ensure that the PKG file is not being held open.

Hey guys,
    I've ran into an issue deploying package files from a dvd.  The meta-data phase works smoothly, but then errors when attempting to deploy the actual data.  The error message is 'Access to path D:\mypackage.pkg' is denied.

I was able to get around this by changing the code in DbEngine -> DatabaseMigrator -> EnumDeploymentPackages where it was attempting to open it with FileAccess.ReadWrite (the default for a new PackageFile). 

from:
Dim loPackage As New PackageFile(MetaDataPkgPathAndFileName, True, False, PkgPassword)

to this:
Dim lopackage As New PackageFile()
lopackage.FileOpenAccess = FileAccess.Read
lopackage.Open(MetaDataPkgPathAndFileName, True, False, PkgPassword)

Any chance of including this in your next update/release?