You are on page 1of 12

Tech Note 617

Resolving the Historian Bad Service Login Error


All Tech Notes, Tech Alerts and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.
Topic#: 002380
Created: July 2009

Introduction
In some cases logins and permissions differences can exist between the InSQL... Service Logins, Registered InSQL Server Properties and MS
SQL Server Server Roles. In this case, the Bad Service login error message appears, and your Historian will not start correctly.
This Tech Note provides step-by-step procedures to resolve the InSQL Bad Service Login error when starting your Historian.

Application Versions
Historian version 9.0 and later
Microsoft SQL Server versions 2000 and 2005
If you have the issue, the Historian SMC displays Bad Service login next to the InSQL Server name (Figure 1 below). ...the InSQL Service
logon is invalid. Please update the Server startup options appears in the status bar.

FiGurE 1: BAD SErViCE LOGiN MEssAGEs


If you click Status, you will only see Loading Please wait as shown in Figure 2 below.

FiGurE 2: LOADiNG...PlEAsE WAit MEssAGE

Procedure
Verify that the Management Console Windows Login Information area has the correct Domain/Login Name/Password.
Use this area to specify the Windows login account information that the Management Console uses to connect to the Configuration Manager. The
login must be valid on the Historian computer and must have local administrative permissions.
1. From the Historian SMC, right-click the InSQL Server name (BRIANN1 in this example) and click Edit InSQL Server Registration
Properties. The Registered InSQL Server Properties dialog box appears (Figure 3 below).

FiGurE 3 - REGistErED INSQL SErVEr PrOpErtiEs


Verify that the Built-in Administrators login is present.
1. Open the Microsoft SQL Server Management Studio, and navigate to Security Logins. You should see BUILTIN\Administrators (Figure
4 below).
2. Right-click on BUILTIN\Administrators, and clck Properties.
3. Verify that Server Roles includes public and sysadmin:

FiGurE 4: BUILTIN\ADmiNistrAtOrs LOGiN


Note: If BUILTIN\Administrators is not visible, or it has been disabled, you must create a Windows-Authenticated login with these permissions.
This account is necessary for Step 8 later in this Tech Note.
4. Verify that the SQL Server (MSQLSERVER) service is configured with Log on as option set to Local System Account:

FiGurE 5: SQL SErVEr (MSQLSERVER) SErViCE


5. Open Control Panel > Services.
6. Note the Status and Startup Type of every InSQL... service:

FiGurE 6: INSQL... SErViCEs


7. Stop and disable each of the InSQL services.

FiGurE 7: StOp

AND

DisAblE EACH INSQL SErViCE

FiGurE 8: INSQL SErViCEs DisAblED


8. Open the Change Network Account utility, and re-enter the User Name and Password.
9. Click OK.
10. Reboot the computer.

FiGurE 9: CHANGE NEtwOrk ACCOuNt UtilitY


11. Open Control Panel > Services and set the InSQL Services back to what they were, before you disabled them. Use the notes you provided
in Steps 5-6 above but DO NOT START ANY OF THE SERVICES INDIVIDUALLY.
12. Open the Historian SMC, and select Status. The Item and Module status panels should now appear similar to Figure 10 (below).

FiGurE 10: INSQL SMC StAtus


13. Start Historian by clicking Status > InSQL Server.

FiGurE 11: StArtiNG HistOriAN


B. Nguyen
Tech Notes are published occasionally by Wonderware Technical Support. Publisher: Invensys Systems, Inc., 26561 Rancho Parkway South, Lake Forest, CA 92630. There is also technical
information on our software products at Wonderware Technical Support.

For technical support questions, send an e-mail to support@wonderware.com.


Back to top
2009 Invensys Systems, Inc. All rights reserved. No part of the material protected by this copyright may be reproduced or utilized in any form or by any means, electronic or mechanical,
including photocopying, recording, broadcasting, or by anyinformation storage and retrieval system, without permission in writing from Invensys Systems, Inc. Terms of Use.

You might also like