DA Server Not Appear in the SMC

7/31/2019 DA Server Not Appear in the SMC

1/12

DAServer Does Not Appear in the DAServer Manager of the System Management Console (SMC)

file:///C|/inetpub/wwwroot/t002331/t002331.htm[9/19/2011 10:35:14 AM]

Tech Note 576


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#: 002331

Created: March 2009

Updated: September 2011

Introduction

Sometimes, after successfully installing a Wonderware DAServer, the DAServer is not available in the DAServer Manager in the System

Management Console. This Tech Not ediscusses reasons why this may occur and how to correct issues that are causing this problem.

This problem can occur due to one or more of the following reasons.

Th e a cc o u n t u s e d d u r i n g t h e DASe r v e r i n s t a l l at i o n d o e s n o t h a v e l o c a l a d m in i s t r a t o r p r i v i l e g e s.

Par t o f t h e h i e r a r c h y i n t h e DASe r v e r M a n a g er i s m i s si n g .

Da t a Ex ec u t i o n P r e v en t i o n i s e n a b le d o n t h e c o m p u t e r . This setting can prevent the System Management Console (SMC) from

working properly.For XP, Server 200 3, and ear l ier OS.

For V ista, Window s 7, Server 2008 and la ter OS.

Th er e i s a p r o b le m w i t h t h e i n f o r m a t i o n e n t e r e d f o r t h e A r ch e s t r A n e t wo r k a c co u n t .

Tasks

This information lists a series of tasks you can complete to diagnose and fix the problems.

Verify the Login Account Used During the DAServer Installation is a Local Administrator

To determin e if a user is a local administrator

1. Open Cont ro l Pane l , then Ad m in i s t r a t i v e To o ls > Co m p u t e r M a n ag e m e n t .

2. In the Computer Management console, expand Local Users and Groups , then Groups.

3. Double-click Ad m in i s t r a t o r s to view the Administrators list. The account used to install your DAServer should be a member of this

group.
http://c%7C/inetpub/wwwroot/t002331/T000792.htmhttp://c%7C/inetpub/wwwroot/t002331/T000792.htm


2/12



FI GURE 1 : VERI FYTH E ADMI NI STRATOR ACCOUNT USED TO I NSTALL YOU R DASERVER

If this user is not an Administrator, the DAServer was not installed properly.

4. Log into an account with Local Administrator privileges, and uninstallthe DAServer.

Note : You may want to go through the rest of the tech note before re-installing the DAServer to make sure there are no other issues


3/12



that will prevent the DAServer from appearing in the SMC.

Verify that No Part of the Hierarchy is Missing from the DAServer Manager

1. Expand the DAServer Manager root in the SMC.

2. Under the DAServer Manager root you should see a group called Defau l t Group (Figure 2 below).

FI GURE 2 : DASERVER MANAGER DEFAULT GROUP

3. If the Defau l t Group is missing, highlight DAServer Manager and then right-click.

4. Click New > Node Group .


4/12



FI GURE 3 : CREATE NEW NOD E GROUP

5. Type Defau l t Group when prompted for a name.

6. Expand Defau l t Group . A node called Local should appear under the Defau l t Group root.

If the Local node is missing, highlight Defau l t Group .

7. Right click and select N ew > N od e.


5/12



FI GURE 4 : NEW NOD E

8. When prompted for a name, type Local.

9. Expand the new node. If there are no other problems, the newly-installed DAServer should now appear in the list. If the DAServer

is now working correctly, your work is complete and you do not need to read the rest of this Tech Note.

Verify that Data Execution Prevention is Disabled - Windows XP, Server 2003 and Earlier Operating Systems

Note : For more information on Data Execution Prevention, see Technot e 437 : Unab le to Open Logger under W indow s XP SP2 and

W in d o w s 2 0 0 3 SP1 .

To disable Data Execution Prevention, you must modify the boot . in i file. This is an operating system file that is usually hidden and read-

only. You can configure Windows Explorer to see the file location and to modify this file.

1. Open Windows Explorer and navigate to the C: drive. The boot . in i file should appear in the root directory of the C: drive.

2. If this file does not appear click the Tools menu and click Fo lder Opt ions . Click the View tab.

3. Select Sh o w h id d e n f i l e s an d f o l d e r s.

4. Uncheck Hid e p r o t e c t e d o p e r a t i n g s y s t e m f i l e s.
http://c%7C/inetpub/wwwroot/t002331/t002130.htmhttp://c%7C/inetpub/wwwroot/t002331/t002130.htmhttp://c%7C/inetpub/wwwroot/t002331/t002130.htmhttp://c%7C/inetpub/wwwroot/t002331/t002130.htm


6/12



FI GURE 5 : CONFIGURE W I N D O W S EXPLORER

5. Click OK . You should now be able to locate the boot . in i file.

6. Right-click boot . in i and click Proper t ies.

7. On the General tab make sure that Read-on ly is unchecked.


7/12



FI GURE 6 : CONFIGURE READ - ONLY

8. On the Secur i t y Tab make sure that the user you are logged in as has privileges to modify the file.

9. If you have made changes to the properties apply them.

10. Open the file using WordPad or Notepad. Look at the noexecute parameter in the last line in the file.

11. If this parameter is set to O p t I n , OptOut or AlwaysOn , change it to AlwaysOf f as shown in Figure 7 (below).


8/12



FI GURE 7 : / NOEXECUTE= ALWAYSOFF

12. Save the file, and restore the file attributes to their previous settings using Windows Explorer.

13. Restore the Folder Options to their previous settings.

These changes take effect when you restart the computer. However, the following task in the next section also requires a reboot.

Complete those steps before restarting the computer.

Verify that Data Execution Prevention is Disabled - Windows Vista, Windows 7, Windows Server 2008 and Later

Operating Systems

Beginning with Windows Vista, the boot . in i file no longer exists, so the procedure to configure DEP is different.

If DEP is enabled, you can manage the settings by doing the following:

1. On your desktop, right-click Computer and click Proper t ies.

2. Click Advanced System Settings.

3. Click the Per fo rmance Set t ing s button.

4. Click the Data Execut ion tab

To completely disable DEP as we need to do in this case, the boot parameters must be edited using Microsofts BCDEdit command lineutility.

1. Open a command prompt by clicking St a r t > R un , then type CMD and press enter.


9/12



2. To disable DEP (Always Off), type this command:

bcdedit.exe /set {current} nx AlwaysOff

3. If for some reason you need to re-enable DEP (Always On), type this command:

bcdedit.exe /set {current} nx AlwaysOn

4. These changes take effect when you restart the computer. However, the following task in the next section also requires a reboot.

Complete those steps before restarting the computer.

Note : If you disable DEP and you are not able to start Windows, run Windows in safe mode and enable DEP again, using the command

above. Start Windows in safe mode by pressing F8 during bootup.

Verify the Information for the ArchestrA Network Account is Correct

All computers that have ArchestrA-enabled software installed must be able to communicate with each other. Communication is enabled

through an ArchestrA-specific user account set up during the installation of an ArchestrA component on each computer.

You must use the same account on each computer that requires communication with other computers in an ArchestrA environment. The

account must be a part of the Local Administrators group on each computer and the password should not expire. It is not necessary to

log in as this account or to use this account to install Wonderware software.

To determine which account is used as the ArchestrA network account, use the Change Network Account Utility.

1. Click St a r t > A l l Pr o g r am s > W o n d er w a r e > Co m m o n > Ch a n g e N et w o r k A cc ou n t .


10/12



FI GURE 8 : CHANGE NETWORK ACCOUNT

If the password you typed in the Change Network account utility for this account is incorrect or too short, the DAServer Manager

or Log Viewer may not work properly.

Wonderware does not require the password to be a certain length; however, on some computers a password shorter than 8

characters can cause problems. You may need to make the password at least 8 characters if you are otherwise unsuccessful at

getting the DAServer to appear in the DAServer Manager.

2. If you have not uninstalled the DAServer by this point, uninstall it.

3. Re-type the password for the ArchestrA network account. This will cause the computer to reboot.

Re-install the DAServer

If you have made changes to the boot.ini file or to the ArchestrA network account, you should have uninstalled the DAServer and

restarted the computer by this point in the Tech Note. If you have uninstalled the DAServer, reinstall it at this time.

The DAServer should now appear in the DAServer Manager under the Local node.

If it still does not appear, add another node to the Defau l t Group in the DAServer Manager.

1. Highlight the Defau l t Group .


11/12



2. Right-click it and click New > Node .

3. When you are prompted for a name, type the computer's network name instead ofLocal.

FI GURE 9 : CREATEA NEW NOD E US INGI TS COMPUTER NAM E

4. Expand the node with the same name as the computer; the DAServer should appear in the list. Once it appears under the node

with the computer name, it should also appear under local .

If the DAServer does not appear in the DAServer Manager after following this procedure, contact Wonderware Techn ica l

Suppor t for assistance.

Click the following icon t o view t his f i le in .pdf format:

D. Schell-Stirland, D. Scott

Tech Notesare 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 Technica l Suppor t .

DAS D N A i h DAS M f h S M C l (SMC)
mailto:[email protected]:[email protected]://wdn.wonderware.com/sites/WDN/Pages/Tech_Support/TechSupport.aspxhttps://wdn.wonderware.com/sites/WDN/Pages/Tech_Support/TechSupport.aspxhttp://c%7C/inetpub/wwwroot/t002331/t002331.pdfmailto:[email protected]:[email protected]


12/12


fil ///C|/i t b/ t/t002331/t002331 ht [9/19/2011 10 35 14 AM]

For technical support questions, send an e-mail to w w suppor t@invensys .com .

Back to t op

2011 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.
mailto:[email protected]://c%7C/inetpub/wwwroot/t002331/T000792.htmhttp://c%7C/inetpub/wwwroot/t002331/T000792.htmmailto:[email protected]

DA Server Not Appear in the SMC

Documents

Transcript of DA Server Not Appear in the SMC