New package: cjmurph.PlexService version 1.2.3

[Exorcism0666]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue?
• Resolve [Package Request]: Plex Media Server service wrapper for windows #146946

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[stephengillie]

Automatic Validation ended with:

Installation failed with exit code -1978335226
2024-03-29 10:16:00.936 [CLI ] ShellExecute installer failed: 1603
CreateUser: Error 0x80070103: failed to read attributes from custom action data
CustomAction CreateUser returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Property(S): ErrorDialog = ErrorDlg
MSI (s) (88:50) [10:16:00:651]: Product: Plex Service -- Installation failed.

(Automated response - build 876.)

[Exorcism0666]

For moderators

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

Warning

With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

Important

Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

[stephengillie]

From the installer log:

CreateUser: Error 0x80070103: failed to read attributes from custom action data
CustomAction CreateUser returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Running installer manually:

This installer appears to require a service account username and password - is that accurate?

[Exorcism0666]

From the installer log:

CreateUser: Error 0x80070103: failed to read attributes from custom action data
CustomAction CreateUser returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Running installer manually:

This installer appears to require a service account username and password - is that accurate?

@palopezv

[palopezv]

From the installer log:

CreateUser: Error 0x80070103: failed to read attributes from custom action data
CustomAction CreateUser returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Running installer manually:

This installer appears to require a service account username and password - is that accurate?

Yes, it is accurate, as shown in the screenshot.

[Exorcism0666]

From the installer log:

CreateUser: Error 0x80070103: failed to read attributes from custom action data
CustomAction CreateUser returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Running installer manually:
This installer appears to require a service account username and password - is that accurate?

Yes, it is accurate, as shown in the screenshot.

@stephengillie

[stephengillie]

The silent install appears to be blocked by a lack of credentials - the username and password needed to create a user account in the OS. Is there a way to supply these through another means, such as installer switch?

It might be possible to specify these settings through a --custom switch, which could let the package manager pass the user-specified username and password through to the installer. I'm not completely sure how it would operate, but having another means to specify these credentials is the first step.

[Exorcism0666]

The silent install appears to be blocked by a lack of credentials - the username and password needed to create a user account in the OS. Is there a way to supply these through another means, such as installer switch?

It might be possible to specify these settings through a --custom switch, which could let the package manager pass the user-specified username and password through to the installer. I'm not completely sure how it would operate, but having another means to specify these credentials is the first step.

@palopezv

[palopezv]

I forgot to mention that the account can anything as long as it has administrative privilege. I use my personal account. The thing is: the installer asks for a preexisting account.

[Trenly]

The silent install appears to be blocked by a lack of credentials - the username and password needed to create a user account in the OS. Is there a way to supply these through another means, such as installer switch?

It might be possible to specify these settings through a --custom switch, which could let the package manager pass the user-specified username and password through to the installer. I'm not completely sure how it would operate, but having another means to specify these credentials is the first step.

Even if it could be passed in using --custom, there is no way to require the argument at runtime

[microsoft-github-policy-service]

Hello @Exorcism0666,

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any recent activity. It will be closed if no further activity occurs within 3 days of this comment.

Template: msftbot/noRecentActivity