Rainbow Sentinel Setup Failed To Complete Successfully

[Gracia Bradshaw]

Ifare installing a single-user license, you should know that it requires the use of a sentinel key (during the program's operation). SuperPro Designer's installation script will automatically install the latest sentinel driver on your PC.

You should not plug in the sentinel protection key before the software installation process is completed. The proper time to insert the key is right before (or after) you attempt to start the application for the first time.

If the key is plugged in before its drivers are installed, it is possible that the subsequent installation of the drivers may not succeed, leading to failure of communication between the program and the key. If that is the case, you must re-install the sentinel drivers by explicitly running the "SentinelSetup.exe" program provided with your installation CD.

If you need to rerun the installation script for just the sentinel drivers, you can find it under the "Sentinel/Driver Installer" folder created in the Aux Folder of your installation. Also, the same installation program can be found at the top level of the installation CD ("SentinelSetup.exe"). Remember that you need to be an Administrator in order to be able to run this program successfully (otherwise the drivers will not be installed). Also, in some corporate environments, such execution may not be allowed to done remotely but you may have to log into the target machine (as Administrator) and then proceed with the (re)installation of the Sentinel Drivers.

Click over the prompt: "Sentinel SuperPro Product Downloads". After you've downloaded the zipped file behind this link ("Sentinel Installer Protection 7.5.0 (Installer Only)") expand it. The executable ("Sentinel System Driver Installer 7.5.0.exe") will launch the installation script. Make sure you re logged in as "Administrator"; better yet, right click over the file and select "Run as Administrator" to make sure you allow the executable full administrative privileges.

A copy of the sentinel driver installation package that was installed with your copy of SuperPro Designer has also been included on your installation CD (look for folder "Sentinel/Driver Installer"). The same file has also been copied on your PC in the "Sentinel" folder that will be found under the selected "Auxiliary Folder" (defaults to C:\Users\Public\Public Documents\Intelligen\SuperPro Designer\v13").

If the drivers have been successfully installed, but you suspect that the key may be damaged, you can plug in your key, and then run the "Advanced Medic" utility that has been supplied by the manufacturer of our keys (dongles). This utility is located in the "Sentinel/Advanced Medic" folder under the Aux Folder of your installation. It is also supplied under the same folder ("Sentinel") on your installation CD.

It's perfectly okay that the "Sentinel Keys Server Installation" shows with an "X". Next click on the "Acknowledge" button (make sure your key is plugged locally on the PC and preferably directly in a USB slot- not a USB HUB interface). If the key can properly be detected, then you should see the following screen:

Please note that un-installing the protected edition of the application (the one that requires a sentinel key) will NOT automatically remove the sentinel drivers from your environment. The reason this happens is to protect other applications possibly installed on your PC that may also utilize the same drivers but of course, communicate with a key provided by a different vendor. If you decide to remove the Sentinel Drivers from your system, you have two options:

2. Locate the program named "SentinelInstall.exe" on the installation CD of our application, or locate a similar program under the "Sentinel" folder of either the CD or the location selected as the Auxiliary Folder during the installation of the software, and run it from a command line with the "/u" as command argument.

after getting back on support and upgrading the older security dongle to the new usb version i installed V9.1 but it keeps asking for the scurity device, despite it already in the usb slot. i had installed the 2020 trial version before and uninstalled it when that expired. it seems to remember somehow that the expired 2020 trial is still installed and refuses to recognize either of my 2 usb security devices or even the older dongles.

it appears that the trial version is not fully uninstalled and browsing the registry there are remnant 2020 files everywhere. i am not sure how to completely uninstall this thing besides whatever the add/remove method did.

when installing 2020 the sentinel protection software gives an error code during it's install process but continues anyway and then 2020 isntalls itself. the problem is that the dongle will not be recognized and the usb dongle's drivers fail to install as well. so sentinel may be the culprit and i tried uninstalling it and even manually removing it's registry keys by searching for sentinel and rainbow keywords. even with this the sentinel install still throws that same error code during it's isntallation.

i know if i format the computer everything will be fine but i am desperately trying to avoid this since i want to work over the weeknd. 2020 tech support is closed and also sentinel tech support is closed too. ggrrrr!

finally got it working! cleaning the registry did not do anything. i installed sentinel driver first then halted the 2020 installation and rebooted the machine. all usb ports now detect the dongle with the exception of one, just refuses to instal drivers for it. but 4 usb ports is good enough.

This Readme combines information from Wonderware Application Server 3.0Service Pack 2 (SP2) with previous Readme files included withWonderware Application Server 3.0 and its prior service pack andpatches:

This Readme explains how to apply SP2 to WonderwareApplication Server 3.0 and its previous service pack and patches. ThisReadme lists all resolvedissues in Wonderware Application Server 3.0 and the service pack andpatches. It alsoincludes descriptions of any known product issues that remainunresolved and possible interim solutions.

This section describes the hardware and software requirementstoinstall Wonderware Application Server 3.0 SP2. Use the following linksfor information about the original hardware and software requirementswhen Wonderware Application Server 3.0 was released in August 2007.

Wonderware Application Server 3.0 SP2 does notsupport.NET Framework 2.0 SP1 or .NET Framework 3.5. WonderwareApplicationServer 3.0 SP2 only supports the versions of .NET Framework describedin the original Wonderware Application Server 3.0 Readme. WonderwareApplication Server 3.0 SP2 requires Microsoft .NET Framework 2.0 atversion CLR 2.0.50727.42, or .NET Framework 3.0.

Yes* implies that the update is possible as long as thesoftware isinstalled in a system with appropriate hardware and softwarerequirements. Software update is not supported where operating systemversions must be updated. If the operating system version must beupdated, the existing Application Server software version must beuninstalled first and the supported version installed after theoperating system is upgraded to the supported version.

All applications created from Wonderware Application Serverversion 2.0Patch 01 through Wonderware Application Server 3.0 SP1 can bemigrated directly to Wonderware Application Server 3.0 SP2.Applications created with Wonderware Application Server prior toversion 2.0 Patch 01 must be first converted to a version 2.0 Patch 01application, and then migrated to Wonderware Application Server 3.0SP2.

L00083820:After you upgrade to SP1 from Application Server 3.0 Patch 03, you areunabletoopen the object editor, and the SQL Server process on the GR node isconsuming the maximum working memory allocation. The SQL Serverdatabase and transaction log files are large for the Galaxy size. (SeeSR 24513634)L00083917:Multiple IDE connections, as well aslong check-in and check-out timescan causeaaGR to stop. In the SMC LogViewer, the CRLinker unknown error messageisconstantly generated. (See SR103113459)L00084012:When the AppEngine starts OnScan with deployed objects containingembedded ArchestrA symbols, the AppEngine shuts down and hangs in the"Shutdown failed" mode. (See SR19416250) L00084205: Afterthe Galaxy is upgraded to Application Server 3.0 SP1, theerror message "Unknown error0xC0000005 (c0000005) raised" appears in the SMC LogViewer. (SeeSR33810549) L00084206:The initial value of the UDA changes to NULL when the AppServer 3.0 SP1aaPkg file is imported. (See SR10415019) L00084362:Errormessage 'mscorlib: Exception has been thrown by the target of aninvocation.' appears in the SMC LogViewer, when the InBatch MaterialServerCOM library script functions are used in Automation Objects. (SeeSR23516503) L00084500:After 49.7 days, the OPCClient stops updating values.There are no error messages in the SMC LogViewer. (See SR24110024) L00084897:Customer'sSAP library script and the CreateObject script both work on ApplicationServer 2.1P02.The scripts do not work in Application Server 3.0 P02. (SeeSR24513402)L00084898:Ittakes 15 to 17 seconds for a platform scan to time out eventhough thescan period is set to 1000 milliseconds. This occurs on asystem that ison adomain that has an Active Directory, but does not have a domaincontroller. (See SR19713145) L00084899:When you create an instance of $OPCClient, it isassignedto the Area_001 objects not the default object.L00084955:Thewrong ArchestrA symbol may be shown in a window when a managed InTouchapplication is not gracefully shut down and synchronized with theGalaxyRepository. After the symbol is re-opened from the checked outpackage, theVERL canbe corrupted. L00084957:String values defined for UDA attributes in aUserDefined Object arelost when imported from the aaPKG file. L00085031:The wrong symbols are shown at run time upon deploychanges.L00085876:Thereis an inconsistent icon shown during configuration and run time of theIDE after upgrading from Application Server 3.0 version to ApplicationServer 3.0 SP2. Specifically,the icon representing objects that are deployed (both on the GalaxyRepository node and on remote nodes) are marked as "software upgraderequired" on the IDE. The same objects are shown "without softwareupgrade" required icon inside ObjectViewer and the SMC. L00087166:Whenyou try to export an InTouchViewApp, the following error messageappearsfrom the Microsoft Cursor Engine: "Out of memory. Not enough storage isavailable to complete this operation. (8007000e)" (See SR 30711041).

3a8082e126