Skip to main content

preloadpkgonsite generates failed to get specified package in database errors

ran into this today while trying to bring back a new site server with all the current packages.

C:\SMSPKG>preloadpkgonsite.exe pkg00001
****** Preload Package On Site ******
Failed to get the specified package pkg00001 in the database. Please check if you have instance rights to that package.

 

smells conspicuously like a permission problem even though i’m getting my rights through a global group assigned to this server.  i tried it again, this time with local system permissions.  much better.

D:\SMSPKG>PreloadPkgOnSite.exe pkg00001
****** Preload Package On Site ******
Forward package status for pkg pkg00001 to site PKG
****** Successfully set the Compressed Package Path on this site ******
****** Successfully forwarded the information up the hierarchy ******

 

if you’re looking for how to execute preloadpkgonsite.exe, you can refer to this earlier post.

Labels:

Comments

  1. spadge0073/8/10, 9:37 AM

    Hi, I am having the exact same problem trying to use the PreloadPkgOnSite utility with SMS 2003 SP2. I have used the utility before without any problems but last year we upgraded the primary site server database from SQL2000 to SQL2005. I'm wondering if this might be the cause of the problem.

    You mention you had success running as the local system permissions. How exactly did you do that?

    Cheers

    Darren

    ReplyDelete
  2. ::marcus3/8/10, 9:51 AM

    here's one way:
    http://marcusoh.blogspot.com/2006/06/os-i-cant-see-interactive-cmd-shell.html

    ReplyDelete
  3. spadge0073/8/10, 9:54 AM

    Thanks for the speedy response. I tried the interactive shell but was confused when the command window didn't appear. I have another 6 secondary sites to move so I will try again at the weekend and see if your workaround works this time ;-)

    ReplyDelete
  4. Mathieu5/28/10, 2:47 PM

    Can anyone tell me why do you have to use the local system permission and nothing else?

    Mathieu

    ReplyDelete
  5. Marcus Oh6/25/10, 5:27 PM

    hey mathieu -

    wish i had a clue man! never did bother to try to understand why. i figured it was just a programming quirk.

    ReplyDelete
  6. Anonymous4/2/13, 3:52 AM

    If the package not available on the primary site and you try to do then you get the same error

    paddymaddy

    ReplyDelete

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m
3 comments
more »