Hi,

Thanks for your post. One quick thing to check would be the to verify the account you are using to login to OME is part of OMEAdministrators group and has full permissions to access the path "D:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate\Packages"

Regards

Abhijit

Thanks for the updates. For both cases the error is for the same update. Is it possible for you to try any other update package. That will tell us if the error is related to the catalog entry for this specific update package.

Regards

Abhijit

There are five update packages available, and all fail the same way. Is the fact that OME not installed to the C: drive in any way a problem? I have confirmed that the account I'm using is in OMEAdministrators, and that that group and the account itself have full control all the way through the folder structure, down to the individual package files.

Thanks for the updates. OME non default install path should not be an issue. For Repository Manager, it looks like OME cannot find the package in the path listed in the catalog. Can you verify if the repository generated is in the same folder as the catalog?

For ftp it may be downloading the package successfully but the file verification may be failing. Can you check if you see the downloaded packages under "Packages" folder?

Regards

Abhijit

Has this been resolved? I have exactly the same issue.

I've created a repository using RM, downloaded the files but if I try and update a system using OME i get the Invalid package path error. I can confirm that files exist in the path shown and that the account i'm using has full access to the directory. I get this no matter what package i try to install, i have tried multiple packages and a single package with the same results.

Hi,

Thanks for your post. Few more questions for you.

Are you running repository manager and the updates from OME server directly or are you doing it from remote machine using web interface?

Can you check if OME website is part of the trusted sites in your browser security settings?

Also check if the account you are using has full permissions not just to the source folder where the updates and catalog are located but also to the system updates folder on OME machine (C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate)

After all these are verified, you can try importing the catalog again.

Regards

Abhijit

Hi,

I am running repository manager and OME directly on the server and using a Domain Admin account so don’t believe it is a permissions problem. I’ve confirmed that the account I am using has full control to the C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate folder. The OME site has been added to the trusted sites in browser settings.

I have tried using the online dell online catalog to do system update but I get the following error. Package unavailable ftp.dell.com/.../Network_Driver_TJPWC_WN32_3.00.08_A00.exe  (I believe this is caused by our proxy server which is why we are trying to use a local repository)

I have just tried to import the catalog created with Repository manager again and have tried to update a single driver on a server and get the same results. "Invalid Package path"

Just to confirm my environment, I created the repository using Dell Repository Manager 1.4.113 (Server) I selected create-Dell OpenManage Essentials Repository, I saved the catalog file and update packages to a folder on the D: drive of the server. I then imported the saved catalog file in OpenManage Essentials.

Regards

Thanks for the updates.

For the online catalog proxy issue, have you tried configuring proxy settings located under the Preferences tab? You can use the Test connection button to verify the connectivity. That might allow you to use the online repository while we sort out the local repository issue.

Regarding local repository, can you check if the domain admin accout is part of local administrators group in OME? Sometimes file permissions are specific to local administrators and don't get transferred to domain administrator accounts unless that account it explicitly added as local administrator.

You are doing everything right for importing the catalong from repository manager.

Regards

Abhijit

Ok, I have tried this with a different Proxy server (one does that not scan downloads) and this has worked using the FTP site, the local repository is still not working. Using the local repository is the preferred solution.

Added account to local administrators group, OME administrators grop on the OME server as suggested but still get the following error when trying to push out an update.

"Invalid package path FOLDER00412796M/1/Network_Driver_H8HTP_WN32_17.2.0_A00.EXE FOLDER00409443M/1/Network_Driver_TJPWC_WN32_3.00.08_A00.EXE"

Is there a way to check that this path is actually referring to "D:\Dell Updates\FOLDER00412796M\1" which is where i have created the repository and not "C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate\Packages" where the packages are saved using the FTP catalog??

Thanks for the updates.

It is possible that either the generated path is incorrect or it has some invalid XML character. Can you open the catalog generated by Respository manager in IE and see if there is any error opening the file?

If the catalog opens successfully, you can search for "Network_Driver_TJPWC_WN32_3.00.08_A00.EXE" and check the path for the file listed there.

If the path is valid, try browsing to that path and check if you see the update file at that location.

The way update process works, it uploads the update file from the path listed in the catalog to OME server in the "C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate\Packages" folder. From there it is distributed to the target servers.

Regards

Abhijit

Hi Abhijit, Thanks for the quick response.

I looked at my saved Catalog file and noticed the following entry <"Manifest baseLocation="" dateTime="2012-09-12T09:24:05+10:00" releaseID="ba0fd7ff-37ef-4e85-a320-d2a3043f2418" name="Dell Updates">

I would think this should be pointing to the directory where my updates have been saved? I have deleted the repository and all files and re-created it, this time selecting save in RM and saving all files to my location. The catalog file now has this entry "Manifest baseLocation="D:\Dell Updates" dateTime="2012-09-12T09:24:05+10:00" releaseID="ba0fd7ff-37ef-4e85-a320-d2a3043f2418" name="Dell Updates"

I have re-imported the catalog but still get the same error when trying an update "Invalid package path FOLDER00409443M/1/Network_Driver_TJPWC_WN32_3.00.08_A00.EXE"

I have searched the xml file for this exe and found two different entries

" "

and

"

I have also confirmed that the exe exists in "D:\Dell Updates\FOLDER00409443M\1" and I can run the exe from there. It looks like OME still can't find the source files to upload but not sure where this settings is kept?

Thanks for the updates.

The entries you have listed look alright and the paths also look correct. You can take a look at the active catalog in OME(located at Manage->System Updates->View Active Catalog). That shows the type of the catalog and the location where it is read from. The package path where OME looks for the package is combination of baseLocation which is "D:\Dell Updates" in this case and the path listed in the SoftwareComponent node which is "FOLDER00409443M/1/Network_Driver_TJPWC_WN32_3.00.08_A00.EXE"

As you have verified, the file is indeed located in that path.

I'm assuming you have the same problem for all packages.

At this point, the only option is to open a support ticket, so that they can get the catalog from you and investigate it further. Here is the number for support 800-945-3355

Regards

Abhijit

Nice. Thanks for the update.

In the upcoming OME 1.2 release (tentative July 2013 RTS), we will have support to use different names for the catalog file.

-Raj Shresta

Opened a case with Dell today. Learned that this "invalid folder path" issue can occur when one doesn't use the default name for the catalog file - catalog.xml. I was renaming the file when exporting and I see the original poster did the same. At Dell's recommendation, I performed a fresh export of my repository from Repository Manager (to an empty folder) and I left the name catalog.xml alone. That catalog.xml file was imported into OME. I've successfully deployed updates now.