Windows 10 build failing "ERROR_INVALID_PASSWORD"

  • 2
  • Question
  • Updated 4 years ago
Windows 10 build failing

"Build Date: 2016-04-27 17:27:35 +0000
Cannot decode object: The specified network password is not correct. 0x80070056 (WIN32: 86 ERROR_INVALID_PASSWORD)
CertUtil: -dump command FAILED: 0x80070056 (WIN32: 86 ERROR_INVALID_PASSWORD)
CertUtil: The specified network password is not correct."

The password is correct, I have retried many times and recreated the key. Is there something non-obvious about this process.

AppID: 1450418
Photo of Stuart

Stuart

  • 8 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 2
Photo of JesseMonroy650 (Volunteer)

JesseMonroy650 (Volunteer), Champion

  • 3325 Posts
  • 122 Reply Likes
@Stuart
What is this about?

Since this is your first post, please answer the following question.
- Is this your first hybrid App?
- Are you using the Phonegap Desktop App?
- Are you using CLI, SDK or Build? Please do not assume the answer, please read the link.

Jesse
Photo of Stuart

Stuart

  • 8 Posts
  • 0 Reply Likes
This is my first app, but I have been building the IOS and Android versions with signing keys and uploading to their respective app stores for about 12 months.

I just pushed to version cli-6.1.0 to test the windows 10 universal app building.

This is through the Phonegap build environment. I am uploading the application through the commandline interface. The other versions are continuing to build correctly, only the windows one is failing.

I read the instructions from the MSDN article linked off the 6.1.0 announcement blog post http://phonegap.com/blog/2016/04/25/w..., but I am clearly missing a step somewhere since my windows environment only won't build.
Photo of JesseMonroy650 (Volunteer)

JesseMonroy650 (Volunteer), Champion

  • 3325 Posts
  • 122 Reply Likes
@Stuart,
Okay. I think you meant to say, "This is my NOT first app".

On using CLI, these few sentences will explain the largest difference.

On your issue I believe, that since you have build successfully on other platforms (Android and/or iOS). I am also assuming that you have built with Windows successfully before (if not let me know).

On you windows issue, there have been some build issues with the system, but I don't build windows and I have not reviewed the documentation - YET.

Give a bit to figure this out. In the meantime, there are other person who might be able to help. Note, they will likey have more questions.

Jesse
Photo of JesseMonroy650 (Volunteer)

JesseMonroy650 (Volunteer), Champion

  • 3325 Posts
  • 122 Reply Likes
@Stuart,
While reviewing this issue, one thing did come to mind. When you enter the password into the webpage - use cut and paste. The webpage will accept the password - even if it is wrong. There is no way to see this until the build fails.

Please cut and paste the password into the webpage for the Windows certificate.

Jesse
Photo of Stuart

Stuart

  • 8 Posts
  • 0 Reply Likes
Jesse-
I did notice this. Actually I think I found a behavior problem with the pvk2pfx.exe program in the WDK. I was following the commands here:
https://msdn.microsoft.com/en-us/libr...

But when running the pvk2pfx command you can specify the password on the command-line or leave it off. If you leave it off you are prompted with a windows dialog. I entered the password in this dialog, but then COULD NOT import that same certificate to the machine on which it was just created.

So, moral of the story is specify the password on the windows command line when using pvk2pfx or the .pfx will not be generated with the correct password.
Photo of JesseMonroy650 (Volunteer)

JesseMonroy650 (Volunteer), Champion

  • 3325 Posts
  • 122 Reply Likes
I would say "it is too easy to enter the wrong password when you can't see what you typed."

FWIW, did this fix your issue?

Jesse
Photo of Stuart

Stuart

  • 8 Posts
  • 0 Reply Likes
All right, now that the certificate can be imported properly, the windows build is continuing to fail. The log file only shows the output of the PFX import:

Build Date: 2016-04-27 19:55:45 +0000
================ Certificate 0 ================
================ Begin Nesting Level 1 ================
Element 0:
Serial Number: c9cd3d1fbb2cc2b14*******************
Issuer: CN=*******************
NotBefore: 4/27/2016 7:32 PM
NotAfter: 12/31/2039 11:59 PM
Subject: CN=*******************
Signature matches Public Key
Root Certificate: Subject matches Issuer
Cert Hash(sha1): 52 b6 4b 52 f5 8a 35 9f 4b ** ** ** ** ** ** ** ** ** **
---------------- End Nesting Level 1 ----------------
Provider = Microsoft Strong Cryptographic Provider
Signature test passed
CertUtil: -dump command completed successfully.
Photo of JesseMonroy650 (Volunteer)

JesseMonroy650 (Volunteer), Champion

  • 3325 Posts
  • 122 Reply Likes
@Stuart,
Okay.
Can you validate the Serial Number and the Cert Hash?
Are there any other reported errors?
If not, can you post the entire "build log" some place public so we can look at it?

Thanks
Jesse
Photo of Stuart

Stuart

  • 8 Posts
  • 0 Reply Likes
The serial number and cert hash do check out. Full build log is:

Build Date: 2016-04-28 14:35:38 +0000
================ Certificate 0 ================
================ Begin Nesting Level 1 ================
Element 0:
Serial Number: ************************
Issuer: CN=9EDDF9C6-1280-4E6F-A2B5-40FFF655B45F
NotBefore: 4/27/2016 8:54 PM
NotAfter: 12/31/2039 11:59 PM
Subject: CN=9EDDF9C6-1280-4E6F-A2B5-40FFF655B45F
Signature matches Public Key
Root Certificate: Subject matches Issuer
Cert Hash(sha1): **********************************************
---------------- End Nesting Level 1 ----------------
Provider = Microsoft Strong Cryptographic Provider
Signature test passed
CertUtil: -dump command completed successfully.
--------------------------------------------------------------------------------
PLUGIN OUTPUT
--------------------------------------------------------------------------------
Fetching plugin "cordova-plugin-camera" via npm
Installing "cordova-plugin-camera" for windows
Fetching plugin "cordova-plugin-compat" via npm
Installing "cordova-plugin-compat" for windows
Fetching plugin "cordova-plugin-media-capture" via npm
Installing "cordova-plugin-media-capture" for windows
Fetching plugin "cordova-plugin-file" via npm
Installing "cordova-plugin-file" for windows

The Android Persistent storage location now defaults to "Internal". Please check this plugins README to see if you application needs any changes in its config.xml.

If this is a new application no changes are required.

If this is an update to an existing application that did not specify an "AndroidPersistentFileLocation" you may need to add:

""

to config.xml in order for the application to find previously stored files.
Fetching plugin "cordova-plugin-console" via npm
Installing "cordova-plugin-console" for windows
Fetching plugin "cordova-plugin-device" via npm
Installing "cordova-plugin-device" for windows
Fetching plugin "cordova-plugin-device-orientation" via npm
Installing "cordova-plugin-device-orientation" for windows
Fetching plugin "cordova-plugin-dialogs" via npm
Installing "cordova-plugin-dialogs" for windows
Plugin "cordova-plugin-file" already installed on windows.
Fetching plugin "cordova-plugin-file-transfer" via npm
Installing "cordova-plugin-file-transfer" for windows
Fetching plugin "cordova-plugin-geolocation" via npm
Installing "cordova-plugin-geolocation" for windows
Fetching plugin "cordova-plugin-inappbrowser" via npm
Installing "cordova-plugin-inappbrowser" for windows
Fetching plugin "cordova-plugin-media" via npm
Installing "cordova-plugin-media" for windows
Fetching plugin "cordova-plugin-network-information" via npm
Installing "cordova-plugin-network-information" for windows
Fetching plugin "cordova-plugin-whitelist@1.0.0" via npm
Installing "cordova-plugin-whitelist" for windows
Fetching plugin "cordova-plugin-splashscreen" via npm
Installing "cordova-plugin-splashscreen" for windows
CertUtil: -importPFX command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.
my "Personal"
CertUtil: -delstore command completed successfully.
Photo of JesseMonroy650 (Volunteer)

JesseMonroy650 (Volunteer), Champion

  • 3325 Posts
  • 122 Reply Likes
@Stuart,
The next to the last line in this log file indicates that the file named Personal" is missing. This appears to be related to the Certificate we have been debugging. You will want to check your configuration file for that Certificate.

Jesse
Photo of Stuart

Stuart

  • 8 Posts
  • 0 Reply Likes
I thought the pfx uploading was only handled in the Account Settings --> Signing Keys dialog. Is there a required reference in the config file too?
Photo of JesseMonroy650 (Volunteer)

JesseMonroy650 (Volunteer), Champion

  • 3325 Posts
  • 122 Reply Likes
@Stuart,
Is there a required reference in the config file too?

I can't tell you if something is required in config.xml for the windows build. I do not build for windows, and I see nothing in the general documentation. Perhaps there is something in the blog post.

BLOG says:
Ensure the Subject Name of your signing certificate matches the Windows Publisher ID from your Microsoft Developer Account.


I can tell you the error is pointing to a misconfiguration. Since other people have successfully built with PGB, I must presume the error is in the configuration for the certficate - plainly the error log is stating so. Read the last four (4) lines of the error log you posted.

Jesse
Photo of Stuart

Stuart

  • 8 Posts
  • 0 Reply Likes
I believe the misconfiguration is server side. The certutil command runs on the windows build machine and the should run something like

certutil -importpfx myimportfile.pfx

But even on my development machine, i tested miskeys or a bad password sent to that command and it returns the same error we're seeing above in the log such as this example from my machine

$ certutil -importpfx mysecret.pfx -
Enter PFX password:
CertUtil: -importPFX command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.

I can't find any additional reference to anyone who is actually building on the new Windows 10 universal app platform on PGB, actually I hopped onto another thread where a user this morning is tracking the same issue:

https://forums.adobe.com/thread/2147110
Photo of Stuart

Stuart

  • 8 Posts
  • 0 Reply Likes
OK, we can close this one now, the ticket was resolved over in
https://forums.adobe.com/thread/2147110

Server side import in the certutil command is now working correctly.

Thank you for your help Jesse
Photo of JesseMonroy650 (Volunteer)

JesseMonroy650 (Volunteer), Champion

  • 3325 Posts
  • 122 Reply Likes
@Stuart,
thanks for letting us know. We'll make note of it.

Best of Luck,
Jesse
Photo of Frank Chabrie

Frank Chabrie

  • 9 Posts
  • 0 Reply Likes
The issue is not resolved. The whole last week I was not able to build because of the certutil file not found error, yesterday in the evening, I was able to build for windows 10, today I run in the error again. The app has not changed during the time.
Photo of Thomas LE MAGOUROU

Thomas LE MAGOUROU

  • 1 Post
  • 0 Reply Likes
Today is the same error, Yesterday was ok.
Photo of Frank Chabrie

Frank Chabrie

  • 9 Posts
  • 0 Reply Likes
same here
Photo of Michel Schilder

Michel Schilder

  • 4 Posts
  • 1 Reply Like
Ah, same here! Since yesterday can't build a windows app anymore (cli-6.1.0)
Photo of Ludo Naut

Ludo Naut

  • 4 Posts
  • 0 Reply Likes
same Problem
Photo of sammca

sammca

  • 35 Posts
  • 1 Reply Like
Experiencing this since I started building with 6.1.0, has never successfully built.

App id: 1237362
Photo of Petra V.

Petra V., Champion

  • 7794 Posts
  • 1391 Reply Likes
The PGB developers still haven't fixed this.
You should keep an eye on the Blog and cross your fingers.