Forum Thread: Failed to Create Package

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:

This thread has been marked as locked.
dsoper Failed to Create Package
Member 19th Jun, 2013 23:31
Ranking: 0
Posts: 7
User Since: 22nd Jun, 2012
System Score: N/A
Location: US
So, I'm moving my Secunia console from a Windows 2003 32-bit box to a Windows 2008 64-bit box. Installation is done and I can connect between the console machine and my WSUS server. However, when I try to create a package, I get the following error:

[06/18 13:16:21.820] Publishing package
[06/18 13:16:44.596] Failed to create package: : -2147352567 , In 'Publisher.invoke'
Code: -2147467259
CreateDirectory failed
--> System.ComponentModel.Win32Exception: CreateDirectory failed
at Microsoft.UpdateServices.Internal.FileSystemUtilit ies.CreateDirectory(String path)
at Microsoft.UpdateServices.Internal.BaseApi.Publishe r.CreatePackageDirectory(String customDirectoryName)
at Microsoft.UpdateServices.Internal.BaseApi.Publishe r.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)
at Microsoft.UpdateServices.Internal.BaseApi.Publishe r.PublishPackage(String sourcePath, String packageDirectoryName)
at plugin.DotNetWrapper<Microsoft::UpdateServices: :Administration::IPublisher>.invoke(DotNetWrapp er<Microsoft::UpdateServices::Administration::I Publisher>* , PluginBstr* name, Arguments* args, PluginMarshal* marshal)
[06/18 13:16:46.811] Received incremental data from server, processing 550 bytes
[06/18 13:16:46.827] Executed 10 statements in 0ms
[06/18 13:16:46.827] Data processing complete
[06/18 13:16:46.827] fCalibrateUI: Begin

Anyone know what might be going on?

This user no longer exists RE: Failed to Create Package
Secunia Official 4th Jul, 2013 08:49
Last edited on 3rd Jun, 2014 10:28 Hi,

The error you encountered indicates that the CSI cannot perform publishing of packages, as any of the following scenarios may likely be the reason for the errors you've seen:

1. Disc Space - The location where WSUS stores newly published packages is running out of disc space. Please check if the default update storage location (C:\WSUS\UpdateServicesPackages) has enough space to store new updates. If it's running out of space, you need to clean up the repository before you are able to publish new packages.

2. Privileges issue - check if your domain user account used to run CSI, (or the IE browser if you're using CSI 7.x) has been added to the local WSUS Administrators group at the WSUS server (lusrmgr.msc > Groups > WSUS Administrators). Secondly, check the permissions of the ...\WSUS\UpdateServicesPackages directory and see if your account was given privileges to access the directory.

3. The UpdateServicesPackages directory where packages are normally published was moved from its original location (C:\WSUS\UpdateServicesPackages) to a new location (f.e. D:\WSUS) without following the recommended steps by Microsoft. Please confirm with the below posted article at Microsoft Technet if your WSUS folder was transferred to the alternative location correctly:

4. Check if the ...\WSUS\UpdateServicesPackages location was shared correctly by your WSUS and whether the server repositories are accessible for the user running the CSI (or the IE if using CSI 7.x). You should also check if your user was given 'Write' permissions to the WSUS folder. You may try to access the server's shared drives from a remote machine by using the UNC path of the server machine in the Windows Explorer address bar. This test will yield a permission error if you are not allowed access to the WSUS server.

5. It is also possible that this is a DNS issue - if your WSUS has an Alias naming different than the NetBIOS name of the system, you shall check whether your DNS contains A records pointing to the alias WSUS name. You may as well try re-connecting to the WSUS by using an IP address instead of using the server names (Patching > WSUS Configuration > Configure Upstream Server).

Finally, if none of the suggestions helped, please send us a new email to, so that a Secunia CSC specialist can be assigned to your case and investigate.

Let us know if you have additional questions.

Kind Regards | Stay Secure
Rosen Danailov | Junior Solution Specialist
Secunia Customer Support

This thread has been marked as locked.