Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Troubleshooting the Macros

Troubleshooting the Macros

Office 2003

This topic provides information to help you troubleshoot problems you may encounter when running the IPFullTrust and SignCode macros.

Error Message:

"The form definition (.xsf) file is read-only. Ensure that the manifest file is not read-only before running this macro. If you are using a source control system, ensure that the manifest file is checked out."

Or

"The template file is read-only. Ensure that the template file is not read-only before running this macro. If you are using a source control system, ensure that the template file is checked out."

The IPFullTrust macro must make modifications to the manifest.xsf and template.xml files. These files cannot be set to read-only. If you are using a source control system such as Visual Source Safe, be sure you have both of these files checked out.

Error Message:

"The form definition (.xsf) file is locked or in use by another application or user. Ensure that the InfoPath designer is not currently open and that no other applications or users are accessing the file."

Or

"The template file is locked or in use by another application or user. Ensure that the InfoPath designer is not currently open and that no other applications or users are accessing the file."

The IPFullTrust macro must make modifications to the manifest.xsf and template.xml files. These files cannot be open in the InfoPath editor when the macro is run. Close the InfoPath designer and then re-run the macro.

Error Message:

"An error occurred registering the solution: <detailed error message>"

The IPFullTrust macro calls the RegisterSolution method of the InfoPath COM automation object. If any error occurs when this method is called, the message will be displayed in the Macro output window. Please see the InfoPath SDK documentation for troubleshooting any of these errors.

Error Message:

"Access is denied to the form definition (.xsf) file."

Or

"Access is denied to the template file."

Write access has been denied to the file due to a security access restriction. View the file's access control list to verify that your account has permission to modify the file.

Error Message:

"The form definition (.xsf) file contains elements, attributes, or structures that are not valid."

Or

"The template file contains elements, attributes, or structures that are not valid."

This indicates the file's XML is not valid. Use Visual Studio .NET to edit the file directly and correct the problem.

Error Message:

"SignCode.exe was not found. Ensure that SignCode.exe is in the path environment variable."

The SignCode macro is dependent on the .NET Framework SDK utility SignCode.exe. The macro looks for this utility in the SDK directory of your Visual Studio .NET 2003 installation directory, typically C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin. If the file is not found here or in any of the directories included in your PATH environment variable, this error will result. To correct the problem, be sure the .NET SDK has been properly installed on your system.

Error Message:

"No code signing certificate found at C:\Documents and Settings\username\My Documents\Visual Studio Projects\myInfoPathProject\myCertificate.cer."

No code signing certificate was found in the InfoPath project directory. To sign your InfoPath .xsn file, you must have a certificate file named myCertificate.cer and a corresponding private key file named myKey.pvk in the project directory.

Problem

You are prompted to enter a password for your private key file during the build process.

Private key files are often password protected. If your key file is password protected, you will be prompted for the password every time you build the project. For the development and testing phase, it is recommended that you use a "test" certificate and key file. Enter a blank password when the key file is created to avoid this dialog. DO NOT use this test certificate for the final, release version of your project. A valid code signing certificate should be obtained from a certificate authority for release versions of your project.

Other Problems

If the SignCode.exe utility encounters any errors during the signing of your project, these errors will be displayed in the Visual Studio build output window. Please refer to the .NET Framework SDK documentation to troubleshoot these problems.



Show:
© 2015 Microsoft