Troubleshoot Information Server 2014 SP3 Email Authentication When PowerShell Works
Use Information Server's documented email-settings test, then compare its SMTP session with the successful PowerShell session. A message sent interactively from the same computer does not establish that Information Server presents the same identity or transport settings. For Information Server 2014 SP3, the available evidence does not identify the authentication failure's cause or a verified correction. Preserve the full error and obtain correlated mail-server evidence before changing configuration.
Table of Contents
- What the Successful PowerShell Test Establishes
- Apply the Documented Information Server Email Settings
- Compare the Two SMTP Attempts
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
What the Successful PowerShell Test Establishes
The reported Information Server test fails authentication, while a PowerShell message sent from the same computer succeeds. Ports 587 and 25 were tried. This demonstrates a successful path for that interactive test, not equivalence between the two applications' authentication and transport configuration.
Microsoft documents Send-MailMessage credentials and SSL selection as separate parameters. The supplied test did not specify UseSsl; the port number alone does not establish an equivalent encrypted application test. PowerShell command documentation. Do not repeat the supplied customer addresses or credentials in diagnostic searches.
Apply the Documented Information Server Email Settings
The 2014 SP3 manual provides this procedure:
- Log in to the Information Server web application as Administrator.
- Select Administration > E-mail settings.
- Enter the SMTP server name/IP, port and sender address.
- Click Apply to save the configuration.
- Enter a recipient under Test connection; ensure the configuration is saved.
- Click Send and record the result.
These settings configure the Scheduler's email connection. Information Server, section 3.4.4. The opened procedure does not establish a username/password configuration or a particular supported authentication mechanism; do not invent one.
Compare the Two SMTP Attempts
This is a proposed diagnostic comparison:
- Record the installed Information Server build and complete application error text.
- With the mail administrator, correlate the application test and successful PowerShell test by time.
- Compare the actual destination, port, sender, presented identity, transport negotiation and server rejection information where those records are available.
- Determine which concrete difference explains the rejection before changing either application or mail policy.
- Check any proposed corrective configuration against documentation applicable to Information Server 2014 SP3.
The expected result is a specific discrepancy supported by mail-server evidence, not an assumption that the password or firewall is wrong.
Verification
Verify both the built-in test and the actual scheduled report delivery after a supported corrective action is established. Confirm receipt of the intended report and attachment, not just an accepted SMTP connection.
Keep report generation, export to the required document format and email delivery as separate checks. A successful email test does not establish daily PDF generation. No messages were sent and no subscription was run for this article.
Limitations and Operational Precautions
The complete authentication response, installed update level and mail-server policy are unavailable. The central repair remains unresolved, and the opened manual does not independently establish the claimed authentication/encryption capability for the precise scenario.
Do not disable SMTP authentication, weaken transport security or expose passwords to make a test pass. Preserve the working application and mail configuration before approved changes. A relay or different mail endpoint would require its own supported and reviewed design; it is not prescribed as a verified workaround.
Engineer FAQ
Does PowerShell success prove the Information Server password is accepted? No; first establish which identity the application actually presents.
Does changing the port identify the cause? No; correlate the complete attempted session.
Does email-test success prove scheduled PDF delivery? No; verify the report subscription separately.
Technical References
- Siemens: SIMATIC Information Server 2014 SP3 System Manual, December 2017, A5E38560846-AD, section 3.4.4.
- Microsoft: Send-MailMessage, Windows PowerShell 5.1 parameter documentation.