5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS

Tech Note 1039

Tips for Resolving Demo Mode with Historian Client and WIS
All Tech Notes, Tech Alerts and KBC D documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information.

Topic#: 002877
C reated: May 2014

Introduction
This Tech Note provides tips to help understand why you might experience Demo Mode with Historian Client/Active Factory, and how Demo Mode can be
resolved.

Demo Mode can occur for several reasons on the new ArchestrA Licensing System. The method for license validation for these products varies based on your
installed license type. This Tech Note describes the different license types and provides troubleshooting tips for each type.

https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 1/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS

F IGURE 1: ACTIVEF A CTORY IN DEMO MODE

Application Versions
Wonderware Historian Client 10.1
Wonderware Information Server (WIS) 5.0

Note: ActiveFactory and Historian Client names are used interchangeably in this Tech Note.

Supported Feature Lines

Historian Client Desktop Version
https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 2/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS

License File Description Application

ActiveFactory
ArchestrA.lic Per Seat License
ActiveFactory_Pro

ArchestrAServer.lic (Requires ArchestrA License ActiveFactory_svrDev

Device License (Requires entry in Wonderware.opt file)
Server) ActiveFactory_Pro_svrDev

User Named License (Requires entry in Wonderware.opt ActiveFactory_svrUser

file) ActiveFactory_Pro_svrUser.

ActiveFactory_svrConc
Concurrent License
ActiveFactory_Pro_svrConc

ActiveFactory Web Version

License File Description Application

ActiveFactory
ArchestrA.lic Per Seat License
ActiveFactory_Pro

ArchestrAServer.lic (Requires ArchestrA License ActiveFactory_svrDev

Device License (Requires entry in Wonderware.opt file)
Server) ActiveFactory_Pro_svrDev

User Named License (Requires entry in Wonderware.opt ActiveFactory_svrUser

file) ActiveFactory_Pro_svrUser

ActiveFactory_svrConc
Concurrent License
ActiveFactory_Pro_svrConc

Order of Precedence
By design, Historian Client attempts to validate the license in this order. The first available license will be used.

1. ActiveFactory
2. ActiveFactory_svrDev
3. ActiveFactory_svrUser
4. ActiveFactory_svrConc
https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 3/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS
AF Web attempts to validate the license in this order:

1. ActiveFactory
2. ActiveFactory_Web_svrDev
3. ActiveFactory_ Web_svrUser
4. ActiveFactory_ Web_svrConc

Per Seat License (ArchestrA.lic)

Description
The per-seat license for ActiveFactory is compatible with all its components including the Web. The ArchestrA.Lic file is only supported with the license
ArchestrA License Manager installed. The ArchestrA License Manager is installed with Historian Client 10.1 and WIS 5.0 setup.

Possible Scenarios for Demo Mode

ISSUE

Client is using Trend with Remote Desktop

CAUSE

With ArchestrA.Lic, Terminal Services is not supported. You will immediately encounter demo mode. If you require the use of Terminal services with AF Trend,
you will need to use ArchestrAserver.lic and the feature line in the license must include TS_OK (Terminal Services).

RESOLUTION

Do not use Remote desktop.

Or

Use a Server-Based license and the feature line in the license must include TS_OK

ISSUE

Installed ArchestrA.lic using License Manager and not ArchestrA License Manager

CAUSE

If you deploy a managed app that contains the AF Trend control within a symbol, it will run successfully without having to install AF 9.2 on the platform you
deployed to. However, you will not have the latest ArchestrA License Manager nor additional retrievalstyle files installed. Once you attempt to install
ArchestrA.lic with the old license manager, it will convert the ArchestrA.lic file into wwsuite.lic.

Historian Client 10.1 will not support wwsuite.lic and is hardcoded to look for the archestra.lic file in the path c:\Program Files\Common Files\ArchestrA\License.

RESOLUTION
https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 4/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS
Install Historian Client and then reinstall ArchestrA.lic

Or

Manually copy ArchestrA.lic to C:\Program Files\Common Files\ArchestrA\License.

ISSUE

Demo mode when using a hardware key.

CAUSE

Multiple USB hardware keys are used on the same machine.

RESOLUTION

Consolidate all hardware keys into one key. There are known issues with having multiple hardware keys in one machine.

Server License (ArchestrAserver.lic)

Description
The server license for Historian Client is compatible with all components. In order to install this license, you must already have installed the ArchestrA License
Server, which is available on the Wonderware Information Server 5.0 and Historian Client 10.1 CDs.

Possible Scenarios for Demo Mode

ISSUE

You never added the ArchestrA License Server to ArchestrA License Manager.

CAUSE

If you are using Historian Client Desktop version, it will depend on ArchestrA License Manager to determine where the License Server is installed.

AF Web Components in WIS 5.0 acquire license information using the webservice http://Webserver/aaflexlicwebservice/aaflexlicwebservice.asmx. ArchestrA
License Manager is not required for thin clients.

RESOLUTION

1. Go to Start > All Programs > Wonderware > Common > ArchestrA License Manager.
2. Add the License Server if it does not exist. (Figure 2 below).

https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 5/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS

F IGURE 2: ADDING A LICENSE SERVER TO ARCHESTRA LICENSE MA NA GER

ISSUE

Client uses Trend with Remote Desktop.

CAUSE

When using Remote Desktop, the AF controls validate their license with the License Server by passing the interactive device and user name (i.e
ian.whitelaw@iomlkf6824l). In the log file snippet below, ian.whitelaw is the windows login and iomlkf6824l is the device name.

You can monitor all activity from the ArchestrAserver.log file on the License Server. The file is located at C:\Program Files\Common
Files\ArchestrA\License Server.

In Figure 3 (below), you can see how it first attempted to find if device name (iomlkf3824l) is in the Wonderware.opt file. In this case it was not found and
https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 6/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS
it is noted.

F IGURE 3: SAMPLE LOG FILE ARCHESTRASERVER>LOG

RESOLUTION

There are several rules to know before making entries in the Wonderware.opt file:

Make sure the Wonderware.opt file contains the correct user or device name. Consider users that are connected through Remote Desktop.
All user names and passwords must be in lowercase letters.
Do not include domain extensions, just user names.
IP Addresses can be used, except for ACP Thin clients. See the ArchestrA License Manager Readme for details. (Keep in consideration some thin clients
can add characters to the windows login.)
If you have a 5 user license, it will only read the first 5 users. You cannot list 10 users in the Wonderware.opt file and expect only 5 of them to be used
at a time.
After making any change to the Wonderware.opt file, you must restart the ArchestrA License Server service. To restart the service, go to the ArchestrA
License Manager, right-click on Server, then select Stop License Server. Then repeat and select Start License Server.

https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 7/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS

F IGURE 4: STOPPING A ND STA RTING THE LICENSE SERVER

ISSUE

Trend runs in Demo Mode when using on WIS or AFWeb portal nodes.

When using the web client components for AF, you can experience Demo Mode even if you have verified all users in the Wonderware.opt file and have even
verified that the license works using the AF desktop version.

CAUSE

AF Web components look for a valid license using the aaFlexLicWebService. This web service is installed with WIS. The link to this web service is
http://servername/aaflexlicwebservice/aaflexlicwebservice.asmx.

RESOLUTION

If you are experiencing Demo Mode, first attempt to visit this URL in your browser on the client (Figure 5 below).

https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 8/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS

F IGURE: 5 A A F LEXLICWEBSERVICE WEBSITE

If you do not see a similar screen, you must enable Anonymous Access to this webservice. Do the following:

1. Go to Start > Run, type inetmgr, then press Enter.

2. In the features view (Figure 6 below), expand the Server name in connections, expand Sites, expand Default Web Site.
3. Highlight aaFlexLicWebService. To the right under /aaFlexLicWebService Home – IIS, double-click Authentication.

https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 9/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS

F IGURE 6: IIS UI
4. Under the aaFlexLicWebService Authentication page, make sure Anonymous Authentication status is Enabled (Figure 7 below).

https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 10/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS

F IGURE 7: IIS UI AUTHENTICA TION VIEW

ISSUE

Trend runs in Demo mode when placing the WIS portal on a custom port (i.e. http://servername:8080/Wonderware)

CAUSE

When using the AF Web Client components, redirection to the aaFlexLicWebservice will fail on custom ports.

RESOLUTION

Historian Client/Active Factory client components do not support ports other than 80 or 433. It will fail to redirect.

https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 11/12
5/29/2014 Tips for Resolving Demo Mode with Historian Client and WIS
I. Whitelaw

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

For technical support questions, send an e-mail to [email protected].

Back to top

©2014 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 any information storage and retrieval system, without permission in writing from Invensys Systems, Inc. Terms of
Use.

https://wdnresource.wonderware.com/support/kbcd/html/1/t002877.htm 12/12