EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB19094: Automatic Deactivation of MicroStrategy Intelligence Server installation occurs every time after a machine reboot


Community Admin

• Strategy


Automatic Deactivation of MicroStrategy Intelligence Server installation occurs every time after a machine reboot.

SYMPTOM:
Strategy Server Activation is a licensing technology that ensures that installations of Strategy server products are authentic and have been legitimately licensed. Server Activation registers each Server Installation with Strategy and locks the installation to a specific machine. For more details regarding Strategy Server Activation, refer to the Strategy Licensing Site (https://licensing.Strategy.com).
 
User activates an installation containing Strategy Intelligence Server (and other Strategy servers) and this activation process is successful. However, the user finds that after the machine is rebooted, the following standard activation warning message is received (upon connectivity through Desktop, Web or License Manager) indicating that the installation has been deactivated:
 
Strategy's server products require activation within ## calendar days of installation. At least one server product has not yet been activated after installation and/or upgrade. These product(s) will remain functional for another ## days after which they will not restart. Please activate these products using License Manager or visit the activation web site at https://licensing.Strategy.com
The user is able to successfully re-activate the installation, however after the next machine reboot, the same situation is encountered.
 
CAUSE:
The most likely cause of frequent deactivations (which results in a prompt for re-activation each time) is a change in (or unavailability of) the unique machine identifier information. For a windows machine, the unique machine identifier used for activation is the Network Ethernet Card (NIC) MAC Address.
 
To troubleshoot the issue and determine the exact cause, the 'MAQueryEnvironment' diagnostic may be enabled as described in the following Knowledge Base techhnical note:
 
KB19037: What kind of diagnostics are helpful in troubleshooting issues pertaining to frequent deactivations of MicroStrategy servers
 
When the Strategy Intelligence Server starts-up, it check the validity of the unique machine identifier - it checks the MAC Address of the Network Ethernet Card (on a Windows machine) and compares the value to that of its current activation record. If this information does not match or if it cannot obtain the MAC address, the installation is deactivated.
 
In many environments, the Strategy Intelligence Server service is set to start automatically upon a machine reboot. This unfortunately may cause a "timing issue" such that Intelligence Server starts up "too soon", but it may not be enough time for the Network Ethernet Card to be "visible" and hence the deactivation occurs.
 
The 'MAQueryEnvironment' diagnostic can show evidence of the Network Ethernet Card being "not visible". Following is a snippet of this trace showing comparison between two scenarios:
 

  • When Intelligence Server starts-up and is able to obtain the MAC address of the Network Ethernet Card:
     
    2008-06-04 09:42:41.514-10:00 Enter 'CheckUniqueHostIdentifier' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\OsQuery.cpp(166)
    2008-06-04 09:42:41.532-10:00 Enter 'MatchHashedMacAddressWithIPHelper' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\MacAddressImpl.cpp(353)
    2008-06-04 09:42:41.566-10:00 Found MAC 00:15:c5:ff:a7:49, Hash is 4f80cfb3c47749c,
    2008-06-04 09:42:41.583-10:00 Leave 'MatchHashedMacAddressWithIPHelper' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\MacAddressImpl.cpp(353)
    2008-06-04 09:42:41.600-10:00 Leave 'CheckUniqueHostIdentifier' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\OsQuery.cpp(166)
  • When Intelligence Server starts-up upon machine reboot and is unable to obtain the MAC address of the Network Ethernet Card:
     
    2008-06-04 09:48:19.140-10:00 Enter 'CheckUniqueHostIdentifier' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\OsQuery.cpp(166)
    2008-06-04 09:48:19.203-10:00 Enter 'MatchHashedMacAddressWithIPHelper' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\MacAddressImpl.cpp(353)
    2008-06-04 09:48:19.250-10:00 Leave 'MatchHashedMacAddressWithIPHelper' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\MacAddressImpl.cpp(353)
    2008-06-04 09:48:19.265-10:00 Enter 'MatchHashedMacAddressWithNetbios' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\MacAddressImpl.cpp(184)
    2008-06-04 09:48:19.359-10:00 Leave 'MatchHashedMacAddressWithNetbios' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\MacAddressImpl.cpp(184)
    2008-06-04 09:48:19.375-10:00 Leave 'CheckUniqueHostIdentifier' near Z:\Tools\MARegistration\MAQueryEnvironment\MAQueryEnvironment\PrivateSource\Windows\OsQuery.cpp(166)

From looking at the snippets above, it is seen that the scenario of Intelligence Server start-up upon machine reboot is missing the following information in the diagnostic:
 
Found MAC 00:15:c5:ff:a7:49, Hash is 4f80cfb3c47749c
In one reported environment, the active Network Ethernet Card was on standby mode, so it took some time to be "available" after machine reboot.
 
ACTION:
Set the Strategy Intelligence Server service to not start-up automatically upon a machine reboot. This may be done by changing the 'Startup Type' to 'Manual' in Strategy Service Manager > Options > Service Startup, as shown on the screenshot below:
 

ka04W00000148VJQAY_0EM440000002BHQ.gif

 
Thereafter, start the Intelligence Server service a few minutes after the machine has completely rebooted giving enough time for the Network Ethernet Card to be "available."
 
Third Party Software Installation:
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 1, 2017

Last Updated:

June 1, 2017