Summary
Consider the following scenario:
-
Your application uses a DataAccessControl.CreateCustomPackages API call to create custom packages that are configured in an XML file.
-
The package contains multiple sections.
-
The DataAccessControl.CreateCustomPackages call fails for some reason.
In this scenario, you receive an error message that resembles the following:
Status: Failed to create package '<PackageCollection>.<ID>.<Token>'
State = 0
Status: Failed to allocate package.
State = 0
Status: The package creation process has failed on resource 'ResourceName':
State = 0
Execution failed.
However, even if you can identify the failing section by viewing the token, you don't know the details about why the command failed. After you apply this hotfix, you can get a more detailed error message, including the SQLCODE, SQLSTATE, and SQLCAMESSAGE elements, as provided by the DB2 database.
For example:
Status: Failed to create package '<PackageCollection>.<ID>.<Token>'
State = 0
Status: Failed section: '2'
State = 0
Status: ILLEGAL SYMBOL "ORDERS". SOME SYMBOLS THAT MIGHT BE LEGAL ARE: , FROM INTO SQLSTATE: 42601, SQLCODE: -104
Status: The package creation process has failed on resource 'ResourceName':
State = 0
Execution failed.
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur, or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
You must have cumulative update package 2 for Microsoft Host Integration Server 2013 installed to apply this hotfix. For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2929767 Cumulative Update 2 for Host Integration Server 2013
Microsoft Host Integration Server 2013
Cumulative update information
The fix that resolves this problem is included in cumulative update package 3 for Host Integration Server 2013. For more information about how to obtain the cumulative update package, see Cumulative update package 3 for Host Integration Server 2013.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
