- Intouch Error Exception Caught For Viewinitialize Video
- Intouch Error Exception Caught For Viewinitialize Money
I have a website developed in ASP.Net 2.0 that is throwing the error
in the production environment. It was not throwing this error in development.
The source is 'mscorlib', and the stack trace says the error at
The only thing I've changed since my last upload to production is that I've started using Membership controls (Login, LoginView), and have added a few more stored procedures and tables, etc. The membership depends upon a custom provider I've written.
Anybody have a clue why this could be happening?
Joel Coehoorn317k9999 gold badges504504 silver badges739739 bronze badges
Donnie ThomasDonnie Thomas1,72988 gold badges3838 silver badges6464 bronze badges
8 Answers
I'd suggest checking for an inner exception. If there isn't one, check your logs for the exception that occurred immediately prior to this one.
This isn't a web-specific exception, I've also encountered it in desktop-app development. In short, what's happening is that the thread receiving this exception is running some asynchronous code (via Invoke(), e.g.) and that code that's being run asynchronously is exploding with an exception. This target invocation exception is the aftermath of that failure.
If you haven't already, place some sort of exception logging wrapper around the asynchronous callbacks that are being invoked when you trigger this error. Event handlers, for instance. That ought to help you track down the problem.
Good luck!
Greg DGreg D36.8k1313 gold badges7777 silver badges114114 bronze badges
This can happen when invoking a method that doesn't exist.
Brian Webster21k4141 gold badges132132 silver badges208208 bronze badges
Casey BurnsCasey Burns
I know its kind of odd but I experienced this error for a c# application and finally I found out the problem is the Icon of the form! when I changed it everything just worked fine.
I should say that I had this error just in XP not in 7 or 8 .
mohammad sepehrimohammad sepehri
abcabc
I just had this issue from a namespace mismatch. My XAML file was getting ported over and it had a different namespace from that in the code behind file.
Greg SipesGreg Sipes
This is may have 2 reasons
1.I found the connection string error in my web.config filei had changed the connection string and its working.
- Connection string is proper then check with the control panel>services>SQL Server Browser >start or not
Sameer BahadSameer Bahad
Got same error, solved changing target platform from 'Mixed Platforms' to 'Any CPU'
Jaime VasquezJaime Vasquez
This error occurs to me due to I have not set my Project as StartUp Project
When I set my current project to Set As Start-Up Project then it gone.
shaishav shuklashaishav shukla
Not the answer you're looking for? Browse other questions tagged asp.netexceptionmscorlib or ask your own question.
Hello everyone,
Sometimes when I open my computer up from sleep mode I get this error. I also noticed that sometimes my laptop freezes to the point where I must force a restart and after logging back in I receive the same notification. The solutions I saw online mentioned a couple of programs that were badly written Trojans and to uninstall them, but when I went through the steps looking for them my computer did not have those particular programs to delete. My friend recommends to just wipe the computer and start all over, but I really am hoping it does not come down to that because I don't want to have to install all of my drivers again. Below is the wall of text I get from the error. Any help would be greatly appreciated!
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quick, the application closes immediately.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: '.', hexadecimal value 0x00, is an invalid character. Line 10, position 1. (C:UsersUserAppDataLocalMSISCM.exe_Url_zv0ikcohnhzptbjtykvepncdk0ijftla13.16.12025.0user.config line 10) ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 10, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars)
at System.Xml.XmlTextReaderImpl.ParseText()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlTextReaderImpl.Skip()
at System.Configuration.XmlUtil.StrictSkipToNextElement(ExceptionAction action)
at System.Configuration.BaseConfigurationRecord.ScanSectionsRecursive(XmlUtil xmlUtil, String parentConfigKey, Boolean inLocation, String locationSubPath, OverrideModeSetting overrideMode, Boolean skipInChildApps)
at System.Configuration.BaseConfigurationRecord.ScanSectionsRecursive(XmlUtil xmlUtil, String parentConfigKey, Boolean inLocation, String locationSubPath, OverrideModeSetting overrideMode, Boolean skipInChildApps)
at System.Configuration.BaseConfigurationRecord.ScanSections(XmlUtil xmlUtil)
at System.Configuration.BaseConfigurationRecord.InitConfigFromFile()
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(Object sender, InternalConfigEventArgs e)
--- End of inner exception stack trace ---
at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(Object sender, InternalConfigEventArgs e)
at System.Configuration.Internal.InternalConfigRoot.OnConfigRemoved(InternalConfigEventArgs e)
at System.Configuration.Internal.InternalConfigRoot.RemoveConfigImpl(String configPath, BaseConfigurationRecord configRecord)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
at System.Configuration.SettingsBase.SetPropertyValueByName(String propertyName, Object propertyValue)
at System.Configuration.SettingsBase.set_Item(String propertyName, Object value)
at System.Configuration.ApplicationSettingsBase.set_Item(String propertyName, Object value)
at MSI.SCM.SCMII.SetECOtoEC()
at MSI.SCM.SCMII.MainForm_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
All patches bring with key sensitivity settings and filter programming to recreate each original patch response. This collection includes a quality set of 63 Drum Kits for the NN-XT Reason Sampler and Combinator module. Free cool drum fills. C) Bundles: that include a pack of collections and libraries from several synths. Thus in order to save disk space there was no need to sample more layers.Compatibility chartRFL filesPropellerhead Reason 6 or any later version.Note for Reason Essentials versionsAll NNXT patches are fully compatible but some Combinator patches won't load properlly because they use modules that are not present in those simplified versions.Minimum system requirementsPC SystemsRunning Windows 7 or any laterMac SystemsRunning OSX 10 or any laterCPUIntel/Amd dual core or moreRam1GB or moreDisk Space2GBOlder systems that could run Reason 4 (or later) will work as well. You can also load more than 3200 samples with the Redrum module.
at MSI.SCM.SCMII.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2110.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
SCM
Assembly Version: 13.16.12025.0
Win32 Version: 13.016.12025.0
CodeBase: file:///C:/Program%20Files%20(x86)/SCM/SCM.exe
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2110.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2110.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2102.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
WPFOSD
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/SCM/WPFOSD.DLL
I am migrating an application away from JBoss JMS to ActiveMQ, but I am nothaving much luck. The application, migrated away from JBoss, will run under
Tomcat 6 as a webapp. I have everything functioning except JMS.
So far I have done the following:
Copy the Web App whole from where it lived under JBoss's embedded Tomcat and
move it under a standalone Tomcat webapp directory. (Plus make necessary
changes for things to work, add JAR files previously pulled from JBoss but
obviously not including JBoss JMS JAR files.)
Copy activemq-all-5.1.0.jar plus geronimo-jms_1.1_spec-1.1.1.jar plus
geronimo-jta_1.0.1B_spec-1.0.1.jar plus
geronimo-j2ee-management_1.0_spec-1.0.jar plus commons logging into my web
applications WEB-INF/lib directory.
Create the following jndi.properties in my web apps WEB-INF/classes
directory:
java.naming.factory.initial =
org.apache.activemq.jndi.ActiveMQInitialContextFactory
java.naming.provider.url = vm://localhost
queue.MyRequest = Test.MyRequest
topic.MyMessage = Test.MyMessage
And I know this jndi.properties file is being found and parsed because if I
deliberately misname the queue or topic, I get a different and earlier
exception.
My goal is to run the JMS broker within my webapp, thus avoiding an
unnecessary extra process and service to manage. I am obviously missing
something, but so far in my searching I cannot find what else I need to
configure to get this to work. The application in question does not use
Spring or XBeans, so I would prefer to avoid these configuration methods.
Unfortunately, most examples either use the standalone broker or Spring or
XBeans.
I try to initialize JMS with the following class, instantiated via 'new
TestJMSSetup()' from my startup servlet, and I get the Exception mentioned
in the subject above. The code below is simplified from code that works
with JBoss JMS, at least as of JBoss 3.2.7. The simplified code and the
full code fail with the same exception at the same line --
qcf.createQueueConnection(USER_NAME,PASSWORD). Note that if I instead call
qcf.createQueueConnection() I get the exact same exception.
Can anyone help identify what is missing here? Or point me to a web page or
other documentation that spells out how to get an ActiveMQ broker fully
running within Tomcat, making use of the ActiveMQ JNDI for lookup?
Thanks!
Eddie
My code is below, and the exception I get is below that.
package test;
import java.util.Properties;
import javax.jms.*;
import javax.naming.*;
import org.apache.log4j.Logger;
public class TestJMSSetup {
protected static final Logger LOG = Logger.getLogger(TestJMSSetup.class);
public static final String NAMING_CONTEXT_FACTORY =
'org.apache.activemq.jndi.ActiveMQInitialContextFactory';
public static final String CONNECTION_FACTORY = 'ConnectionFactory';
public static final String JMS_QUEUE_NAME = 'MyRequest';
public static final String JMS_TOPIC_NAME = 'MyMessage';
public static final int NEVER_EXPIRE = 0;
public static final String USER_NAME = 'testuser';
public static final String PASSWORD = 'testpassword';
public static final String MESSAGE_LENGTH = 'MsgLen';
protected final InitialContext jndi;
Intouch Error Exception Caught For Viewinitialize Video
private final JMSTopicServer jmsTopicServer;private final JMSQueueServer jmsQueueServer;
public TestJMSSetup() throws Exception {
try {
// Initialize JNDI
LOG.info('setting up JNDI..');
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, NAMING_CONTEXT_FACTORY);
env.put(Context.PROVIDER_URL, 'localhost');
jndi = new InitialContext(env);
// Initialize, then start JMS
LOG.info('initializing JMS..');
jmsTopicServer = new JMSTopicServer();
jmsQueueServer = new JMSQueueServer();
LOG.info('starting connections..');
jmsQueueServer.start();
jmsTopicServer.start();
LOG.info('started connections');
} catch (Exception e) {
LOG.error('TestJMSSetup exception', e);
throw e;
}
}
/**
* Handle incoming messages (from our client).
* @param msg The message to handle
*/
public void handleMessage(final String msg) {
try {
jmsTopicServer.publishMessage(msg);
} catch (Exception e) {
LOG.error('handleMessage() Exception', e);
}
Intouch Error Exception Caught For Viewinitialize Money
}/**
* This inner class handles all JMS Topic communication. After we receive
a
* message from our client, the topic server is used to publish this
* message to all receivers.
*/
private class JMSTopicServer {
private final TopicConnectionFactory tcf;
private final Topic jmsTopic;
private volatile TopicConnection tConnection = null;
private volatile TopicSession tSession = null;
private volatile TopicPublisher publisher = null;
public JMSTopicServer() throws Exception {
tcf = (TopicConnectionFactory)jndi.lookup(CONNECTION_FACTORY);
jmsTopic = (Topic)jndi.lookup(JMS_TOPIC_NAME);
}
protected void start() throws JMSException {
LOG.info('creating Topic connection ...');
tConnection = tcf.createTopicConnection(USER_NAME, PASSWORD);
tSession = tConnection.createTopicSession(false,
Session.AUTO_ACKNOWLEDGE);
publisher = tSession.createPublisher(jmsTopic);
publisher.setTimeToLive(NEVER_EXPIRE);
publisher.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
LOG.info('starting Topic connection ...');
tConnection.start();
LOG.info('started Topic connection');
}
protected void stop() {
try {
tConnection.stop();
tSession.close();
tConnection.close();
} catch (Exception e) {
LOG.error('stop() caught exception', e);
}
}
public void publishMessage(final String message) throws JMSException {
ObjectMessage bytesMsg = tSession.createObjectMessage();
bytesMsg.setObject(message);
publisher.publish(bytesMsg);
}
}
/**
* This inner class handles all JMS Queue communication. We receive
requests
* intended for the our client on this Queue and forward them to our
client
* for processing.
*/
private class JMSQueueServer {
private final QueueConnectionFactory qcf;
private final Queue jmsQueue;
private volatile QueueConnection qConnection = null;
private volatile QueueSession qSession = null;
private volatile QueueReceiver qReceiver = null;
public JMSQueueServer() throws Exception {
qcf = (QueueConnectionFactory)jndi.lookup(CONNECTION_FACTORY);
jmsQueue = (Queue)jndi.lookup(JMS_QUEUE_NAME);
}
public void start() throws JMSException {
LOG.info('creating Queue connection ...');
// NEXT LINE THROWS THE EXCEPTION *****
qConnection = qcf.createQueueConnection(USER_NAME,PASSWORD);
qSession =
qConnection.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
qReceiver = qSession.createReceiver(jmsQueue);
qReceiver.setMessageListener(new JMSQueueListener());
LOG.info('starting Queue connection ...');
qConnection.start();
LOG.info('started Queue connection');
}
public void stop() {
try {
qConnection.stop();
qReceiver.close();
qSession.close();
qConnection.close();
} catch (Exception e) {
LOG.error('Exception caught in stop()', e);
}
}
public class JMSQueueListener implements MessageListener {
public void onMessage(final Message msg) {
try {
BytesMessage bytesMsg = (BytesMessage)msg;
byte[] queueRequest = new
byte[msg.getIntProperty(MESSAGE_LENGTH)];
bytesMsg.readBytes(queueRequest);
String message = new String(queueRequest);
LOG.info('Take action with the message we received: ' + message);
// CODE WOULD GO HERE
} catch (Exception e) {
LOG.error('onMessage() encountered exception: ' + e.getMessage(),
e);
}
}
}
}
}
I get the log messages:
2008-06-18 17:50:13,524 -0500 INFO [TestJMSSetup] - initializing JMS..
2008-06-18 17:50:13,524 -0500 INFO [TestJMSSetup] - starting connections..
2008-06-18 17:50:13,524 -0500 INFO [TestJMSSetup] - creating Queue
connection ...
2008-06-18 17:50:13,540 -0500 ERROR [TestJMSSetup] - TestJMSSetup exception
javax.jms.JMSException: Could not create Transport. Reason:
java.io.IOException: Transport not scheme specified: [localhost]
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
at
org.apache.activemq.ActiveMQConnectionFactory.createTransport(ActiveMQConnectionFactory.java:237)
at
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:250)
at
org.apache.activemq.ActiveMQConnectionFactory.createQueueConnection(ActiveMQConnectionFactory.java:192)
at test.TestJMSSetup$JMSQueueServer.start(TestJMSSetup.java:148)
at test.TestJMSSetup.(StartupServlet.java:138)
--
View this message in context: http://www.nabble.com/%22Transport-not-scheme-specified%22-exception-trying-to-initialize-JMS-tp17994225p17994225.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The key to managing the issue is understanding it. The kind of errors I'm discussing in this article fall into two distinct categories: runtime errors that result from assumptions you made in code that didn't cover all the bases; and ones that result from the unforeseen failure of dependencies. Let's first look at assumptions made in code. Here's a simple page with a form and a bit of code to process the form's values when it is submitted. The code takes the numbers entered into each box and divides one by the other:
There's hardly any code here so what could go wrong? Well, if the user doesn't enter anything into the second textbox, a
DivideByZeroException
will be raised when the form is submitted. The same will happen if they enter text there (or, of course, zero). You can add some validation to ensure that the second text box contains a number greater than zero, and that's pretty easy with the Web Pages validation helpers. And that should take of that, shouldn't it? What if the user entered an HTML tag into one of the boxes? That will result in an HttpRequestValidationException
A potentially dangerous Request.Form value was detected from the client..
You validation helpers are of no use in this situation. They don't even get a chance to run before the exception is raised. Did you ever think that someone might enter HTML into a box intended for numbers? Probably not - but users have a million ways to surprise you.
Here's another code snippet:
This is a typical example of taking a value from the query string and passing it into a SQL command which gets executed against the database. What could go wrong here? If there is no matching id, the
book
variable will be null, so any attempt to reference its properties will result in a RuntimeBinderException
Cannot perform runtime binding on a null reference
You can mitigate against this by checking to see if the
book
is null before you start to work with it:However, what if someone clicks a link to your site that includes some extra stuff on the end like this:
http://www.yourdomain.com/book?id=1</strong>
The result will be another
HttpRequestValidationException
. You might wonder how your url would ever get into such a state. Well, it's actually all too easy for this kind of thing to happen as people paste your link into another place and the processing system mangles it up to include some HTML. You have no control over how your urls are treated by other people or systems, but if you ever look at the logs for any site, you might be surprised at the range of additions that get appended to requests - most of them innocent, but some of them designed to probe security weaknesses in your web application. The other type of error results from the failure of an external component. SQL Server deadlocks will raise exceptions. A remote mail server might not be online or a DNS lookup might fail. Changes in permissions on directories on the web server resulting from an operating system update.. All of these will result in a yellow screen of death.
So what should you do? You could wrap everything up in
try-catch
blocks. However, the standard advice is to only use try-catch
if you can provide a meaningful route to recovery for the user. What you shouldn't do is There is nowhere for the code to go if the query string is tainted with HMTL. Not only that, but there is no record that anything went wrong.
Custom Error Page
Assuming that you aren't going to shield your entire code base with
try-catch
blocks, you are still left with the fact that ASP.NET error pages are not user friendly. What you should do is to provide your own custom error page instead. You should create a static HTML page for this. You don't want to use one of the ASP.NET page types tied to a layout or master page in case the error occurs somewhere in the layout page. Then your visitors will be presented with a different type of ASP.NET error page - one with a description that says An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.
Once you have created your error page, you need to tell your application to use it. You do this in your web.config file by adding a
<customErrors>
section to the <system.web>
section. Here's the default web.config file from a WebMatrix site with the <customErrors>
section added:The
mode
property is set to On
(with a capital O - a lower case o will result in a configuration error). If an unhandled exception arises in your code, the user will be redirected to your error.htm page. That may not be what you want when you are working on the application as you need to see the description of any errors that arise so you can fix them. But you don't want to have to remember to keep switching custom errors on and off. What you can do instead is to set the mode to RemoteOnly
, which will result in the custom error pages being displayed to remote users, and detailed errors being displayed to requests made from the same machine that the web server is running on - i.e. your development box.Exception Logging Modules And Handlers (ELMAH)
So now you have protected your users from the glare of a YSOD. However, when users contact you to say that they get an error page while browsing your site, how do you know what went wrong? Ideally, you need some way to log details of any exceptions that get raised. You can write a component to do that, or you can use one that's already been written, tested and tried out in thousands upon thousands of existing ASP.NET web sites. A great candidate is the open source ELMAH, which has enjoyed over 1.5M downloads via Nuget alone. If you are using the Nuget integration in WebMatrix, search for 'elmah' and install from there:
If you are using Visual Studio, invoke the Package Manager Console from Tools » Library Package Manager » Package Manager Console and at the
PM>
prompt, typeOnce the package is successfully installed, your web.config file look different and the handlers and modules that form the basis of Elmah are registered. Out of the box, Elmah logs to memory, which is ok for testing, but not for deployment where app restarts will result in the memory being cleared. Elmah will log to a variety of locations including email and databases - SQL Server full version and Compact are both supported, as are Sqlite and even Access. Here's a web.config which has been altered during installation, and then had a couple of lines added (highlighted) to show how to configure logging to a SQL Compact database:
If you want to log to a SQL Server database, the
errorLog type
property will be Elmah.SqlErrorLog
instead:If the database specified in the connection string does not exist Elmah will create one when Elmah logs its first error. Elmah will add one table - ELMAH_Error, to which it will log details of the exception it caught:
The AllXml field contains full details of any error in XML format, which includes not just the error message itself, but all of the
Request.ServerVariables
values to help with trouble shooting. This is especially useful for identifying mangled URLs that may appear somewhere else on the web so that you can take some remedial action.Summary
The purpose of this article was to explain the importance of configuring a custom error page for your ASP.NET Razor Web Pages application to protect your users against unsightly default error pages. It also demonstrated that no matter how carefully you code, unforseen circumstances can lead to your application raising exceptions. The article also introduce Elmah for logging details of your errors and showed how easy it is to configure for use with a SQL Compact or SQL server database.
Last revision: 4/26/2017
In This Document |
About This Readme
This Readme provides information about important resolved and known issues for Wonderware® Application Server 2017 Preview.
For information about new features, hardware and software requirements, product compatibility, installation and upgrades, and user documentation, see the Wonderware® System Platform Readme, which is located in the root folder of the Wonderware System Platform installation media.
Readme files from previous releases of Wonderware Application Server are posted to the Global Customer Support (GCS) Product Hub. You must log in to access the GCS Product Hub.
Resolved Issues
This section describes important resolved issues. The following list is not a comprehensive list of all resolved issues.
Original Change Request | Related Change Requests | Description |
L00128537 | When pairing Galaxies in an environment with a case-sensitive SQL Server installation, the Cross-Galaxy Server Primary node name would not consistently populate on the remote machine automatically . | |
L00138741 | SR 51610008: Changes to DIObject template attributes were not reflected in galaxy browser. | |
L00138831 | L00142463 | SR 103136837; SR 103141617: Licensing did not count items that were IO auto-assigned. |
L00139092 | L00139485 | SR 103137442; SR 52311919 : Using Block Read, DWord and unsigned long data type values were incorrectly read by OPCClient objects. |
L00139101 | SR 40217591: Alarms and events were not being logged from areas running under one engine. | |
L00139108 | L00137401 L00136956 L00141524 | SR 48910970; SR 19912528; SR 103134978: The feature pane was not shown when the Attributes tab of the Object Editor was selected. |
L00139152 | SR 14414018: When a second OPC UA Client was added, it was flagged as a duplicate and could not communicate with the OPC UA Server. | |
L00139226 | L00134995 L00137254 | SR 48910783; SR 40710064; SR 103135777: Remove 'Everyone' share permissions on all Wonderware share names. |
L00139461 | SR 48911012: When a string attribute value was overridden, a space was not allowed in the middle of the string. | |
L00139476 | L00144872 | SR 103137996; SR 42410532: Localized alarm messages could not be not exported. |
L00139489 | L00141262 | SR 48911221: Communication loss occurred every 10 minutes between paired galaxies in an MGC setup in an Azure Cloud environment. |
L00139603 | SR 51310999: During a Galaxy dump, the IDE hung and the dump file that was created did not have any content. | |
L00139638 | L00140378 | SR 54810118: Red error messages were logged during galaxy backup, although the. CAB files generated were good. |
L00139652 | When objects containing Field Attributes were imported to Wonderware Application Server versions 2014R2 Patch 01 and 2014R2 Service Pack 1, and had three-level hierarchies (grandparent, parent, and child relationships) and overwriting objects having only two-level hierarchies (parent and child relationships), various issues were sometimes observed (errors in the Logger; some inherited field attributes were displayed twice, some inherited attributes were not displayed, or the attributes tab would not display any information). | |
L00139813 | Warnings were logged from the ViewAppCategory while deploying InTouchViewApp with an aaHistClientTrend control. | |
L00139850 | SR 103137218: The CEM engine terminated abnormally and a warning message appeared in the logger. The CEM meter license state appeared as undefined. Oct 4, 2014 - When you defragment (a.k.a. Defrag) your computer (technically a hard disk drive), Windows places all the fragments of all the files in their. Aug 23, 2012 - This will start the defrag process manually and you'll see that Windows 8/10 does two passes to relocate fragmented data on the hard drive. A program that you can reach from any hard drive's Properties dialog box is the Windows 8 Disk Defragmenter. Returning file fragments to their proper places. Apr 20, 2013 - The Disk Defragmenter feature has been renamed as 'Optimize Drives' under Windows To defragment your hard drive under Windows 8: Click. How to defrag hard drive windows 8. Jump to Optimizing a Drive - Windows analyzes the level of fragmentation on your drive. If you have more than one hard drive, you'll need to do this for. | |
L00139967 | L00140030 | SR 10512511: A memory leak occurred when an AppEngine hosted a Redundant DIObject that accessed IO strings. |
L00139978 | SR 52311395: A memory leak was causing the system to stop operating. | |
L00140036 | SR 40710078; SR 40710064: System speed was slower after upgrading to 2014 R2 P01. | |
L00140237 | L00140412 L00141161 | SR 51010768; SR 51010812; SR 12613764: Discrete attributes unexpectedly went into UNACK_RTN state, and then lost ACK status upon failover. |
L00140241 | SR 39911259: The BindTo API retrieved only the value and quality properties, but not timestamp, for an indirect variable. | |
L00140291 | L00140384 | SR 103138843: When a published Managed InTouch application was migrated from WindowMaker to Wonderware System Platform 2014 SP1 without migrating the Galaxy first, any graphics called by the ShowGraphic() method were no longer present in the application. |
L00140512 | SR 19912465; SR 103137244: User was unable to browse the Galaxy from Taglinker after upgrading to WSP 2104R2 SP1. | |
L00140517 | L00142444 | SR 48911112; SR 103141258: Attributes resolved to incorrect references. |
L00140605 | L00139755 | SR 48911074; SR 48911137; SR 103138064: It was not possible to configure OPCUAClient Service to allow communication with an eATM OPC UA Server, and the Galaxy Browser was unable to browse the items in the OPC UA Server. |
L00140623 | SR 103139134: Pokes to read-only items in a DI Object resulted in errors in the Logger. | |
L00140701 | L00144353 | SR 103139279; SR 22111428: Changes to parent template attributes overwrote attribute descriptions in derived templates when a containment relationship existed. |
L00140717 | SR 103138982: When loading Galaxy objects from a dump file, some of the objects were created without an associated Security Group. | |
L00140813 | SR 48110075: The value of a a field attribute pointing to an attribute would remain as initializing after failover to the Backup Engine, unless the field attribute was shown in graphics. This did not occur when running on the Primary AppEngine. | |
L00140991 | L00141485 L00142049 L00142070 L00142368 | SR 56510199; SR 34211548; SR 103141273; SR 19819220: The initial graphic call up for an InTouch application window was very slow due to the time needed to resolve external attribute references. |
L00140993 | L00141156 | SR 38910512: After migrating a Galaxy, the CPU utilization rate increased to a higher than normal level. |
L00141232 | When Substitute References was used to update an expression on an ArchestrA Graphic object, the parentheses around the custom property were missing in the new expression. This stopped the expression from working at run time. | |
L00141248 | L00143327 | SR 52313212; SR 51311349: Automation objects were inserted into the intouchviewapptemplate_allsymbols table after importing an object into the Galaxy. |
L00141285 | SR 55110167: Redundant AppEngines could be active simultaneously, on both the primary and backup Winplatforms. | |
L00141367 | SR 45711460: A user working on a node other than the GR node was not able to publish managed applications to a mapped network drive if the user did not have full permissions, and the following warning was logged: CreateDisplayFilesForInTouchForExport -> C:Program Files (x86)ArchestrAFrameworkBinaaDCM.msm not found. | |
L00141741 | L00143316 | SR 103139220; SR 24413334: When a forced failover was done several times, the values in an InTouch application stopped updating. |
L00141827 | L00141845 | SR 103140728: If an attribute with I/O linked to an OPC UA client was created after deploying the OPC UA client, its quality would not update from bad. |
L00142079 | L00142455 | SR 54810222: An alarm with an assigned priority that was not mapped to an Alarm Severity level resulted in Severity 1 warnings being logged in the Historian. The expected behavior is for an unmapped alarm to be displayed as a Severity 0 alarm with no historization. |
L00142128 | SR 103141003: Failed logon attempts were being counted multiple times by the operating system, which resulted in user accounts being locked too early. | |
L00142166 | SR 37114322: When data quality was bad, the OPCClient used the timestamp from the local computer instead of using the KepServer OPC Server timestamp. | |
L00142587 | L00140660 | SR 103141224: When a Field Attribute was converted to an attribute, the State Alarm default setting changed from false to true. |
L00142250 | SR 24516917: When objects containing graphics were imported back into a Galaxy, the graphics did not import with the objects. | |
L00142328 | SR 55110542: Communication was lost between the PLC and existing instances when derived objects were migrated to a newer base template. | |
L00142627 | SR 41910256: Delays in authenticating user that was a member of many security groups caused writes to attributes to fail. | |
L00142659 | SR41910263: When an attribute with a bad IO reference was written to, the write was reported as successful. | |
L00142779 | SR 17115299; SR 103139220: An AppEngine had a memory leak, which continually consumed resources until out of memory. | |
L00143316 | L00141741 | SR 24413334; SR 103139220: After a failover, some attributes remained in 'initializing' state when viewed in the Object Viewer. |
L00143327 | ||
L00143435 | SR:22210313: When logging in to InTouch and starting a Terminal Server session, the login name was occasionally displayed instead of the user's full name. | |
L00143785 | L00144000 | SR 54810298: When an InTouch application that contained symbols with .NET controls (such as Alarm Objects, Trend Objects, or SQL Grids) was published from the ArchestrA IDE, the .NET controls were stored in a .tmp folder under C:WindowsTemp and not automatically deleted after publishing. |
Known Issues
This section describes known issues that remain in Wonderware Application Server 2014R2 SP1 (version 4.1.12).
CR | Description | ||||||||
L00123504 | Unexpected and misleading errors can appear in the logger while migrating particularly large galaxies because the transaction log for the galaxy database has reached its maximum allocated size. Example error: 'Error 80040E2F: Description 'Violation of PRIMARY KEY constraint 'PK__#0489BFA__6B888F1106720818'. Cannot insert duplicate key in object 'dbo.@checked_in_non_relative_unbound_elements_to_bind'. The duplicate key value is (15767, 25329, 420, 1),'. Example error: 'Query returned more than one row'. You can do the following steps to remove restrictions on the size of the galaxy database transaction log:
| ||||||||
L00129132 | Application Server does not support the FIPS (Federal Information Processing Standards) security policy option in Microsoft Windows.The Federal Information Processing Standards are United States Government standards that provide a benchmark for implementing cryptographic software. If your system has FIPS enabled, you should disable it. The security setting for FIPS is listed under Security Settings> Local Policies> Security Options> System cryptography, or as part of Group Policy. | ||||||||
L00131542 | The status of the OPC Client Proxy block read connection is different in Object Viewer than in Log Viewer. After deploying an OPC client proxy object, the script attempts a block read, which results in the following error in the Log Viewer: 'aaBlockReadRuntime2 - Read Transactions are not allowed if the object is in Disconnected State,' even though the connection status of the OCP client proxy in Object Viewer shows it is connected. | ||||||||
L00132251 | SR 103131984: The EngineFailureTimeout attribute displays as 10000 ms in the AppEngine object editor but consistently displays as 30000 ms after deploying the AppEngine object. This occurs because the Application Server run time overrides any value less than 30000. | ||||||||
L00132965 | If a Galaxy includes certain EOM related templates, the Galaxy migration operation will fail. Ensure that these objects (both templates and instances) are removed from the Galaxy before upgrading the software. These objects are no longer supported and will not allow the Galaxy to migrate. Remove the following templates, along with any derived templates and instances:
| ||||||||
L00133194 | Importing a FieldReference package exported from Application Server 3.1 SP2 P01 to a Galaxy created under Wonderware System Platform 2014 R2 with the <FieldReference>.PV.LogDataChangeEvent attribute value set to True will trigger a software error message. To avoid this issue, first import the most recent FieldReference package into the new Galaxy, and then import the exported package. The FieldReference package path is: C:Program Files (x86)ArchestrAFrameworkBinFieldReference.aaPKG | ||||||||
L00134029 | Importing an aaPKG from Wonderware Application Server 2014 to Wonderware Application Server 2014 R2 that has already been imported once, updated on the older version, then re-imported to the newer version, does not update any UDA History descriptions that might have been configured on the older version. As a workaround, you can delete the object instance on the newer version machine, then re-import. The updated attributes will then appear in the Galaxy on the newer version of Application Server. | ||||||||
L00134193 | Under certain circumstances, you may receive an error message when using I/O auto assignment and you press the Validate References button in the IO Device Mapping view. This can happen if the IDE is running on a deployed remote platform. Instead of validating the references, the error message 'Please deploy the platform object to validate the references' is displayed, even though the local and remote platforms are deployed. Workaround: Restart the IDE on the remote platform and then validate the references again. | ||||||||
L00134322 | The ASBGRBrowsing service is used for browsing objects and attributes on the local Galaxy, as well as for browsing in multi-galaxy environments. If you undeploy the ASBGRBrowsing service, browsing in the local Galaxy will result in error messages. | ||||||||
L00134383 | When a saved script is renamed in the Object Editor, the script's contents appear to have been removed and the script editor is grayed-out. As a workaround, save and close the object, then reopen it. The script's contents will once again be displayed in the editor. | ||||||||
L00134390 | When an existing Galaxy created from Base_InTouch.cab is migrated to Wonderware System Platform 2014 R2, $Sequencer and $SQLData objects are created that did not exist in the non-migrated Galaxy. As a workaround, manually delete the added objects from the migrated Galaxy. | ||||||||
L00134493 Horticulture included in cassowary enclosure for sale. | OPCClient DI objects have a naming limitation when used with the I/O assignment feature. I/O auto assignment uses the syntax <DI Object.ScanGroup>.<Field Reference>. However, to fulfill the OPC hierarchical path, a port and device must also be specified; for example, <DI Object.ScanGroup>.<PortName>.<DeviceName>.<Field Reference>. Workaround: Use the Object.Attribute Override column in the IO Device Mapping view to add additional OPC parameters to field references. Manually adding these parameters in the Object.Attribute Override column will result in a fully qualified I/O reference which includes all required parameters. If bulk edits are required, you can copy and paste between the IO Device Mapping view and Microsoft Excel. Refer to Application Server User's Guide for important information about editing I/O references in Excel. Note the caution about sorting references while editing. | ||||||||
L00138642 | Attempts to pair two nodes (multi-Galaxy pairing) failed on two Galaxies, upgraded from Baktun, which were not previously paired. Errors and Warnings are logged while configuring the MGC after upgrade from Baktun PO3 to Apollo R2 SP1. Workaround: Restart the watchdog service if errors are logged after launching the Multi Galaxy Configuration window (Galaxy > Configure > Multi-Galaxy). | ||||||||
L00139257 | A warning message 'Galaxy Restore: SQL Exception: 80043C32: Description '[Microsoft] [ODBC SQL Server Driver] [SQL Server] The user or role' NT AUTHORITY SYSTEM 'does not exist in this database.' is logged when creating a galaxy. Reason and Workaround: You cannot restore a Galaxy to a language locale that that differs from that of the Galaxy's origin. For example, if a Galaxy is created using a computer configured for English (language locale 1033), it cannot be restored using a computer configured for German (language locale 1031). You must use the same language locales when moving Galaxies, and objects within Galaxies, to different computers. | ||||||||
L00139425 | Errors from the BRO may occur while upgrading a Galaxy Repository Node from Application Server 2014 R2 or 2014 R2 P01 to Application Server 2014 R2 SP1. These errors are related to the ViewEngine process and occur only during the upgrade process. There is no impact on functionality and the error messages can be safely ignored. Sample log error messages (these will be highlighted in red): 4003 12/14/2015 11:55:49 AM 6264 7256 Error BRO ViewEngine_001 - CBaseRuntimeObject::SystemSetAttribute - Caught unknown exception. 4004 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 3910 FILE CBaseRuntimeObject.cpp LAST ERROR 0 4005 12/14/2015 11:55:49 AM 6264 7256 Error BRO ViewEngine_001 - CBaseRuntimeObject::BuildFullPrimitiveNames() - BuildName returned false 4006 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 364 FILE CDeploymentPrimitive.cpp LAST ERROR 11001 4007 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVALID HRESULT LINE 393 FILE CDeploymentPrimitive.cpp hResult 80001f40 4008 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVALID HRESULT LINE 466 FILE CDeploymentPrimitive.cpp hResult 80001f40 4010 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001 4011 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001 4012 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001 4013 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001 4014 12/14/2015 11:55:49 AM 6264 7256 Error BaseRuntimeComponentServer INVARIANT FAILED LINE 692 FILE CBaseRuntimeObject.cpp LAST ERROR 11001 4015 12/14/2015 11:55:50 AM 6264 7256 Error ViewEngine_001.aaEngine Could not perform operation -- unexpected exception. Unexpected failure (8000ffff) caught at line 239 in FsEngine.cpp (in ). 4016 12/14/2015 11:55:50 AM 6264 7256 Error ViewEngine_001.aaEngine WinMain exiting error code 8000ffff Workaround: No workaround is necessary. There is no loss of functionality either during the upgrade process, or after the upgrade process completes. | ||||||||
L00139639 | When using Enhanced Security Mode (ESM), restoring a CAB file results in an unusable Galaxy if the BUILTINAdministrators group has the sysadmin role. Workaround: Log into SQL as a user with sysadmin privileges, and run the following script on the unusable Galaxy database. Replace the italicized text inside the angle brackets with the name of the restored Galaxy and with the database host name, respectively. ALTER AUTHORIZATION ON DATABASE::<name-of-galaxy> TO [<db-server-host-name>aaGalaxyOwner] | ||||||||
L00139679 | Bootstrap intermittently does not start on a Windows 7 32-bit remote node after upgrading Wonderware System Platform from version 2014 R2 to version 2014 R2 Service Pack 1. It has been observed that after restarting the remote node, Gdiplus.dll, a Windows system file, was missing from C:WindowsSystem32. If you have a recent version of the Gdiplus.dll installed before upgrading, greater than version 6.1, this issue does not occur. Workaround: After upgrading the run-time node on the 32-bit system, repair the installation again before redeploying the remote platform. | ||||||||
L00139830 | MDT AutoSave for System Platform (A4SP) does not work if Wonderware Application Server is configured to run in 'Enhanced Security Mode'. MDT A4SP version 3.0 still leverages SQL Server SysAdmin privileges. Support for this functionality will be added to A4SP version 3.01, with availability planned for the end of the first quarter of 2016. Please contact MDT Software for additional details at MDT Software Support. | ||||||||
L00139852 | GRAccess does not support Enhanced Security Mode in the following scenarios:
We recommend not using GRAccess to perform these operations. | ||||||||
L00141283 | Multi-node Application Server implementations in Windows workgroup environments are not advised; use domain-based network management instead. For multi-node installations in a workgroup environment, operations that require inter-node communications may not function correctly. These include:
However, if everyone permissions are enabled for anonymous, this issue does not occur. Workarounds: Either enable everyone permissions for anonymous users (method 1), or switch to domain-based networking (method 2).
| ||||||||
L00141660 | In a system with two GR nodes, attempting to connect from the IDE on one node to a Galaxy on the second GR node does not succeed, and the IDE shuts down. Workaround: Pair the GR nodes before trying to connect to the Galaxy on the other node. See 'Working with Multiple Galaxies > Setting Up a Multi-Galaxy Environment' in the Application Server User Guide for information about configuring multi-Galaxy pairing. | ||||||||
L00144613 | When Application Server has been installed/upgraded to Wonderware System Platform 2017, and the ArchestrA Network User account is a local user (not a domain account), an OPCClient object cannot read from a DA Server on a remote node running Windows Server 2008 SP2. This issue is confined to environments where a DA Server is running under the Local System Account on a Windows Server operating systems prior to the 2008 R2 release. Windows Server 2008 R2 and later are not affected by the issue. Workarounds: If networking is via a Windows workgroup, the only workaround you can use is to enable everyone permissions for anonymous users.
If networking is domain-based, you have a choice of two workarounds. First option (domain-based networking only):
Second option (domain-based networking only): On the DA Server node, specify that the DAServer process runs as a domain user account.
| ||||||||
624132 | On some monitors, the ArchestrA IDE shortcut menus are displayed partially off-screen, making them difficult to read or make a selection. Workaround: This workaround is documented on a Microsoft Community forum and is summarized below: (see https://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/context-menu-going-left-not-right/a09e42df-fdd0-45fc-a501-7e5e145a22b3?auth=1) Note: This workaround is applicable to all supported Windows and Windows Server operating systems.
| ||||||||
772561 | When a scaling factor of 125 or 150 percent is chosen in Windows 10, and then use the selection tool in the Graphic Editor, the selection box appears with a offset from the pointer. | ||||||||
773741 | Warning messages appear in the SMC log file when migrating an application created with Wonderware System Platform R2 SP1 to Wonderware System Platform 2017. These messages are in response to symbol functionality present in the application created with Wonderware System Platform R2 SP1 that is not available with a Wonderware System Platform 2017 ViewApp. | ||||||||
775165 | In some instances, when an object’s owned graphic is embedded inside another graphic, and the contained name of the object is changed, the Graphic Editor may display “Graphic not Available”, but at runtime the graphic will be displayed correctly. | ||||||||
777023 | After changing the attribute overrides of a deployed DI object, with more than 20,000 attributes, the attribute validation will fail, even though attribute syntax for the remaining attributes beyond 20,000 is correct. Workaround: Re-deploy the DI Object to clear up this problem. | ||||||||
779110 | If two or more symbols are linked to an object template from which an instance has been created, and overrides are configured for those symbols via Object Wizard options, then the symbol overrides may not appear correctly at run time. Workaround: Open the affected template, make a small change, then save and check in the template. This will re-propagate the changes correctly. | ||||||||
782071 | When reverting an override for the EngUnits or Description setting of an object that does not have an initial value for these settings, the setting value does not revert to the expected value. | ||||||||
783145 | In a galaxy with a large number of layouts, symbols, and miscellaneous objects (assets, area nodes, display controls, etc.), using arrow keys in the layout toolbox to select items from the asset search results causes a long delay in showing the content view, and causes warning messages to be logged in the System Management Console. | ||||||||
785665 | Under certain circumstances, when migrating a CAB file from an older galaxy that contains ArchestrA Graphics and utilizes the Historical Trend control to Wonderware System Platform 2017, the migration may stall at some point and fail to complete. No error message will be displayed. Workarounds: The workaround varies, depending on the Wonderware System Platform version that you are migrating to WSP 2017: Migrating from WSP 2014 or WSP 2014 P01: Copy the following HistorianClient-2014 binaries from C:Program Files (x86) Common FilesArchestrA to C:Program Files (x86)ArchestrAFrameworkbin. Note: If the same computer is upgraded to WSP 2017, the 2014 binaries can be taken from the WSP 2014 installation CD.
Migrating from WSP 2014 R2:
Migrating from WSP 2014 R2 P01 or WSP 2014 R2 SP1: You can directly migrate these CAB files to WSP 2017. No intermediate steps or actions are needed. Migrating through intermediate versions to WSP 2017: If you migrate CAB file to a version lower than WSP 2017, and then migrate the CAB file to WSP 2017, you must re-import the Historian Client controls in the intermediate version, before you migrate the CAB file to WSP 2017. See the following two examples: Example 1: CAB file migration path: 2014 or 2014 P01 > 2014 R2 > 2017:
Example 2: CAB file migration path: 2014 R2 > 2014 R2 SP1 > 2017:
Migrate the CAB file to WSP 2017. | ||||||||
789337 | After deploying an engine with about 25,000 IO, the objects are not set on-scan, and a timeout warning is logged for each object. Workaround: After the deployment fails, restart the AppEngine on-scan. To avoid the problem, you can set the NMXMsgMxTimeout attribute for the WinPlatform object from the default value of 30 seconds (30,000 msec) to 60 seconds or more. You can also set the value of the attribute by changing the Message Timeout parameter (General tab > Message Exchange). Note: Setting the engine off-scan and then on-scan again will not work; you must restart the engine. | ||||||||
792077 | After upgrading the Galaxy Repository node to Wonderware System Platform 2017, and migrating existing galaxies to Wonderware System Platform 2017, the logger shows warning for ProcessRealtimeClerk. This does not affect functionality. You can successfully connect the IDE to migrated galaxies, and successfully redeploy the GR node without errors. All nodes will operate normally. | ||||||||
792311 | SQL Server, and programs that call into it from Wonderware System Platform 2017, periodically (about every five minutes) spike their usage of physical and virtual memory, which degrades system performance. | ||||||||
794197 | While installing the Application Object Toolkit (AOT), under certain conditions during the “Updating the system” step, the following error may be displayed by Visual Studio: “The Add-in ‘AOT Editor’ failed to load or caused an exception. Error number: 80131604.” Workaround:
| ||||||||
794573 | If the System Platform IDE is minimized, and a popup editor (for example, the Layout editor) is active, if the IDE displays a modal window, such as a Save dialog, you cannot select the IDE from the taskbar to move it and the modal window in front of the popup editor. Workaround: Move the other editor out of the way. | ||||||||
794579 | If you start the System Platform IDE, but then the watchdog is restarted or otherwise loses connection to IOMBLS service before any of the popup editors, such as the Layout, Screen Profile, or ViewApp editor, has been opened, the Toolbox of the popup does does not work. This happens because the toolbox is trying to use the prior connection to the IOMBLS. Workaround: Restart the IDE. | ||||||||
795918 | An ASBService warning message is logged if Wonderware Application Server is uninstalled while a galaxy is deployed. Workaround: Undeploy any deployed galaxies before uninstalling Application Server. | ||||||||
798129 | When an instance has multiple levels of containment, not all contained objects are automatically assigned to the Simulator. Workaround: Manually assign instances to the Simulator that are not automatically assigned. |
Documentation Issues
There are no known documentation issues for Wonderware Application Server 2017.
Item | Location of Change | Existing Documentation | Change |
Avantis | Industry Software Suites | OASyS | SimSci | SimSuite | Skelta | Wonderware |
Copyright © 2017 Schneider Electric Software, LLC. | Contact Us |