Issue When logging on to the Report Manager or Report Builder to manage, create or install custom report packs, the following error is shown: User does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed Environment WebReports Cause This is a known issue with Microsoft Reporting Services when User Account Control (UAC) is enabled on the server. By default the local administrators are only given the role of "Content Manager", which does not allow for all operations. The easy solution is to disable UAC, but below is the solution for how to solve it without disabling UAC. For further reference, refer to the following discussion. Resolution 1. Launch Internet Explorer as administrator (right click the shortcut and click "Run as administrator"). 2. Open the Report Manager on the local server using "localhost" in the URL. E.g. if the URL is normally http://server_name/Reports_SQLEXPRESS you need to enter http://localhost/Reports_SQLEXPRESS 3. Click "Folder Settings" 4. Click "Edit" next to the "BUILTIN\Administrators" 5. Check all the options and click "Apply"

Issue When viewing a graphic using WebStation, the zoom controls are not visible in the toolbar. Only "Reset zoom" is shown. Environment WebStation Graphics Zoom Cause The method of zooming a graphic in and out has changed at StruxureWare Building Operation 1.7.1. Prior to this a toolbar was available, but this has now been removed. Resolution To zoom the graphic in and out, the mouse wheel (scroll) is used. The graphic can be positioned by dragging the graphic. On a touchscreen, zooming is achieved using the pinched fingers method. To reset the Graphic to a 1:1 ratio click "Reset zoom".

Issue When an Automation Server backup is restored, the programs or IO's linked to a time schedule does not show their correct states Environment Automation Server Backplane Function Block Time Schedule Cause More than one AS has been fitted onto the same backplane and this e.g. causes the Function Block program to malfunction. The result of this is that the FB program does not reflect the correct state of the time schedule binding, when a backup is restored.               Resolution The installation of multiple AS's onto the same backplane is not allowed.  Do not install more than one AS on a backplane. If you do, they will both try to drive the IO bus and will collide in doing so. This causes the Task Scheduler to lock up in the AS. Results will be unpredictable! To overcome this issue, make sure only one AS is fitted on the same backplane, and "warm-start" the AS.

Issue When opening a graphic or function block live view, you get the following error: Could not create TGML Invalid data Can not open file Environment Detected in versions: 1.6.1, 1.7.1 Runtime Compatibility Graphics Function Block Cause This happens during upgrade, and only in a multi server environment. The ES will be at one version, and the AS one version below. As SmartStruxure has runtime compatibility, this works. There is however currently an issue with how the files from the AS are cached. As a result, when trying to open a graphic located in an AS just after upgrading the AS, you get this error. Resolution Restart WorkStation after upgrading an AS

Issue BACnet Broadcast Device Table (BDT) on a BACnet Broadcast Management Device (BBMD) becomes corrupted after a server version upgrade, only if the BACnet BDT was taught from another BBMD The following upgrades have this issue v1.5 to v1.6, v1.6 to v1.7, v1.7 to v1.8 Product Line EcoStruxure Building Operation Environment BACnet Broadcast Device Table BBDT BDT Management BBMD Cause When a BDT is manually built (or BBMD first created), BDTE00001 is always set to the Server IP address. In the example this is 192.168.1.15 When the BDT is taught from another BBMD, the BDT is changed and BDTE00001 is modified. When a Server (Enterprise or Automation) is upgraded (V1.5-1.6, 1.6-1.7, 1.7-1.8), then BDT entry BDTE00001 is changed to it's own IP address. Thus the Servers BBMD BDT can be corrupted with the Server IP address appearing twice in the BDT Resolution The taught BDT can either be set manually, before the upgrade, so it does not get corrupted by the upgrade process or be corrected following the upgrade. Option 1: Change the BDT before the upgrade The BDT Entry BDTE00001 should be set to the IP address the Server that contains it. The BDT Entry (BDTE00002 in the simple example above) that held the IP address of the Server should be set to the value that was in BDTE00001. Option 2: Correct the BDT after the upgrade For the first Server being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries, Then manually reenter in all the BDT entries. For all remaining servers being upgraded Upgrade the Server Log into the Server and view the BDT from WorkStation Multi-select and delete all entries From the First Server BBMD do a teach Verify the BDT table is in the Server Below would be the first upgraded Server as option 2 or a corrected as option 1   NOTES Versions 1.8 and beyond include a fix so that the "BDT Teach" Mechanism does not allow the BDTE00001 to be changed. A hotfix will be available in V1.7 Upgrading to a fixed version will not correct the issue, one of the two resolutions above will still need to be completed.

Issue The StruxureWare Building Operation BACnet digital value is seen as being in alarm Product Line EcoStruxure Building Operation Environment BACnet Digital Value Alarm Cause Having created a BACnet Digital Value under the BACnet Interface / Application. When the digital value is "Enabled" (Active Text), the IN ALARM status flag is set. This causes the third party device to show it as being in alarm. Resolution From v3.0, EcoStruxure Building Operation is BACnet standard at protocol revision 14 so this is not an issue. The text below was written for earlier versions and is valid for v2.0 and earlier. It is not possible to disable the evaluation of intrinsic alarming on BACnet points (which updates the status flags and event state properties). Not updating status flags and event state (according to the alarm-value) was identified by the BACnet Test Lab as a compliance issue with the BACnet standard at protocol revision 6 – the revision SBO implements. The essence of the issue is that we are not allowed to have the intrinsic alarming properties, but not use them – updating the object state according to its configuration. The feature to disable intrinsic alarming (an alarm disable property) was introduced at a more advanced protocol revision (13), which is not currently not available for SmartStruxure. A possible workaround for the issue, if the value periodically changes between active and inactive: set the time-delay (which is measured in seconds) to a large value. If the delay is longer than the amount of time the value spends in what would be the alarm state, then evaluation is avoided. A value of 32,000,000 for example delays evaluation for a little more than a year. NOTE - make sure to set the time delay while status flag in-alarm is false, and event-state is normal, otherwise it would take a year to get out of the alarm state.

Issue After upgrading to version 1.7.1 or later, a performance issue is seen when reading BACnet values from BACnet/IP devices. The CPU usage on an Automation Server is continuously high. Product Line EcoStruxure Building Operation Environment Detected in version 1.7.1 Automation Server Enterprise Server BACnet/IP Cause A new "BACnet ReadPropertyMultiple Service" has been included from version 1.7.1. Data retrieval from devices that support ReadPropertyMultiple service and do not support the COV (Change of Value) service has been optimized. The resulting improved polling behaviour will particularly benefit graphics performance for ReadPropertyMultiple. If a site is upgraded to version 1.7.1 where this improved communication service gets used automatically, it is possible that the server CPU usage increases. This issue will only be seen if the third party device does not support COV subscriptions, does support ReadPropertyMultiple and a large number of values are being requested from the same device e.g. using bindings. This is a result of much more data being requested by the Server in the same time period.  From Release Notes version 1.7.1 3.4.4 Improved polling performance Data retrieval from devices that support ReadPropertyMultiple service and do not support the COV (Change of Value) service has been optimized. The resulting improved polling behavior will particularly benefit graphics performance for ReadPropertyMultiple.” Resolution Select the BACnet interface where the performance issue is seen Select the advanced properties for the interface Change the “Minimum polling interval for local IP networks (ms) to “3000” In case the BACnet interface is configured in an Automation Server, test other values in step 3 until the CPU usage is stabilized You can check the AS CPU usage, by dragging the CPU usage property to the watch window in WorkStation NOTE It is also worth setting the MSTP polling to 3000mS, to ensure third party BACnet Devices that do not support COV subscriptions, are not overloaded. Without this value set, it has occasionally been seen that Bacnet devices go offline or value readings stop updating the values.

Issue When connecting the RoamIO-2 service tool directly to a standalone BACnet b3 controller which is not connected to the MSTP network yet, the RoamIO-2 does not show the b3 controller on the screen. Environment RoamIO-2 Continuum SmartStruxure BACnet b3 controller Cause By default, the View option of the ROAMIO2 Bacnet Service Tool is set to view "By Network".  Resolution Connect the RoamIO2 service tool directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries. Click the green icon to connect. Now, it will show the b3 controller in the service tool.

Issue When logging in via WorkStation all is fine, but logging in via WebStation shows a blank initial screen (see below). Environment WebStation Cause The system has been configured with a user defined default workspace. The default workspace contains an 'ampersand (&)' in the name. Resolution Apply hot fix 1.6.1.28100 or remove the ampersand character from the workspace's name. NOTE: This issue exists in all versions of StruxureWare Building Operation prior to 1.8, as of the writing of this article only 1.6.1 had a hot fix available to solve the problem. The issue has been resolved in StruxureWare Building Operation version 1.8

Issue Unable to use a Feature of Power Monitoring Expert due to license limitation.    Environment Power Manager Power Monitoring Expert Cause Open the PME Management console Select Help>About You should see the active License Modules as shown below. You may or may not also see additional features that are part of the 90 day trial.   Resolution Contact your sales representative to purchase the additional licenses

Issue Attempt to commission b3 device fails with error 'Device other' AS trace log shows error 'Invalid device instance". EXTRACT FROM TRACE LOG 2015-09-24 20:40:23.135 [1241912384] nsp.pin.BACnet Commission Canceled - Invalid device instance (AsyncCommands) 2015-09-24 20:40:23.142 [1241912384] nsp.pin.BACnet Command continuum.command.Commission failed. BACnet error 0x0 (AsyncCommands) 2015-09-24 20:40:23.144 [1241912384] nsp.pin.BACnet Command continuum.command.Commission failed: Device_Other (0xa0003) (AsyncCommands) Environment AS BACnet MSTP Cause The AS has detected a b3 device with the same serial number in the hardware folder. Resolution Associate the device in the hardware folder with the device that you are trying to commission by dragging the device in the hardware folder and dropping it on the device under the BACnet interface that is being commissioned. Note that the device's model numbers MUST be exactly the same in order for the association to succeed.

Issue The Enterprise Server enters a restart loop filling the hard drive with crash dump (dmp) files Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause This happens due to corrupt backup sets from AS being present. To make a quick check if this is the issue, rename the following folder replacing x.x with the version you have installed. C:\ProgramData\Schneider Electric StruxureWare\Building Operation x.x\Enterprise Server\db_backup\ASArchives If the ES starts after that, identify the faulty backup sets as described below. Resolution Browse to the AS backup folder (see above in "Cause") Detect backup sets not looking correct e.g. having a size of 0 KB Delete these backup sets   From version 1.7.0 and forward, these backup sets are automatically removed

Issue Public Signals, Inputs and Outputs in a Xenta are not accessible through Webstation Environment Webstation Xenta Cause The public signals are currently not objects but properties on a Xenta Resolution 1. Right click the Menta program under the Xenta, and click "Properties"   2. View "Public Signals", "Inputs" and "Outputs" and change if needed by clicking the three dots (...) next to the signal

Issue After upgrading a site, "Server is not compatible" is shown when accessing Web Reports. Environment Web Reports Cause This message is usually shown when the client (Workstation or Web Reports) used is not the same version as the server (AS or ES) you are accessing. However, in some cases after upgrading a site, this message can be seen even though the server you are connecting to is in fact the same version as the client. This is because the version of the client is cached in the server. As described in the upgrade guide, the Web Reports agent should be stopped during upgrade of the ES. If the agent was not stopped during the upgrade, you can get in a state where this message is shown. Resolution The resolution is to simply restart the ES.

Issue System configured with an AS, a number of IO modules and several power supplies, everything works fine BUT when viewing the IO configuration in the IO Management Tool the AS appears in the wrong slot. In the screen shot below the AS reports that it is occupyng slot #10 instead of slot #1, slot #10 is physically occupied by a power supply. No address shifted or black listed devices are reported and everything works fine. Environment Automation Server WS Cause A pin has been bent or otherwise damaged during installation of the AS The system does not report any problem because in this particular case the address that the AS assumed corresponds to a power supply, because power supplies do not report the slot they occupy. Eventhough everything is operating normally, it is recommended that the issue be resolved by removing the AS and identifying the root cause of the problem which could be in the AS itself or in the TB where the AS sists. As seen above, the problem in this case was a bent address PIN on the AS itself, the problem was resolved by making the pin straight and re-inserting the AS in its terminal base. Resolution The problem was resolved by making the pin straight and re-inserting the AS in its terminal base.

Issue When using the cascade menu from the SmartStruxure demo database it doesn't work in Webstation using HTML5, but works in Workstation. Environment TGML Webstation HTML5 Cause There is an issue in the script controlling the menu Resolution Fix the menu script as follows 1. Edit the graphic containing the menu 2. Locate the script in the menu component 3. Edit the script 4. Locate line 171 (approximately) 5. Comment line 171 and 176 (approximately) as shown below 6. Save the graphic and open it in Webstation       Note - This is only extra information and not needed Another fix that will also work, is to correct the script as shown below, but the easiest and safest is to apply the change above

Issue Failed to establish connection with server. (HTTPS) 1.5 Server version not compatible with client (HTTP) 1.5 Failed to establish connection with server. (HTTPS) 1.6 Failed to access the server, a network error occurred. (HTTP) 1.6 Environment StruxureWare Building Operation 1.5 and newer Cause Attempting to log into WorkStation for Project and you either do not have the Project Configuration Server installed or the Project Configuration Server is not running. Resolution Reboot the machine. Check that the Project Configuration server service is running.  Note: One other possibility is that you have a different instance of Projects Configuration server already running from a concurrent installation. (Example: You are trying to log into Projects 1.8.1 but you already have Projects server 1.7.1 running). This will cause a Failed to establish a connection with the server error.

Issue After a specific date, trend log values are no longer transferred to the report server.  In the table tbEventLogs, the column NumberOfRecords continously shows over 50000 Environment Web Reports Cause For a currently unknown reason, at some point a mismatch between index sequence numbers and time stamps has occured, and therefore the same log values are attempted transferred over and over again. Resolution The reporting agent needs to be set up to read more records to get over trouble 1: Open the file "SE.WebReports.StruxureWareReportingAgent.exe.config" located in the reporting agent installation directory. Use notepad or similar. 2: Edit the line containing "numLogTimeRecordToRead"  changing the value 5000 to 20000 3: Restart the agent 4: Wait until the column NumberOfRecords in the table tbEventLogs shows a number lower than 20000 5: Change the value back from 20000 to 5000 in the config file 6: Restart the agent

Issue After having discovered a b3 device attempting to download results in a failure. Error details show device as being offline. Product Line EcoStruxure Building Operation Environment SmartStruxure Automation Server with b3 device on BACnet MSTP network Cause This issue can be caused by a missing serial number for the device. Resolution Check to see that the serial number of the device is set. This can be viewed by right-clicking the device and selecting Properties and then going to the Advanced tab. By default, the serial number is part of the Object ID and the BACnet name. You can extract the numeric portion then paste it into the Serial number field and then try to download again. The serial number can also be found on the tag on the device itself.

Issue Input points on BACnet devices displaying in a Graphic show the forced icon on the Graphic when the input is manually forced, not so for value objects such as Analog Value. Product Line EcoStruxure Building Operation Environment BACnet Automation Server Enterprise Server Cause The reason for this is that when a point such as an input is forced StruxureWare Building Operation automatically puts it out of service and when the input is unforced puts back in service, that is not the case for a value object. The screen shot below illustrates the problem, as seen, both the input point under a b3 (Ct1CwSTmp) as well as the analog value (CtCwSSpt) in the AS are forced but only the input is displaying the hand icon indicating the that object is forced. Resolution A work around is to create a PE Script program to set the out of service property to TRUE when the value is forced and to FALSE when the value is NOT forced. Please note that the program uses the value of priority 8 to determine whether the value object has been forced or not, if the Priority 8 is NOT NULL then the object has been forced, note that this presents a problem for binary objects as well as for the case where the analog object is forced to a value of ZERO as PE Script can't differentiate between NULL and zero. In the case at hand, the program is located in the Application folder under the BACnet interface of the Automation Server.