cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

Recover project after unexpected restart

Recover project after unexpected restart

ChrisLarkin
Established Member

Hello,

A customer has experienced WebIQ designer perform a unexpected/unplanned restart. During which they lost any progress they had made with their project.

Is there any way to recover the project?

I've included appdata log.

They are running version 2.12 so no system log is available.

3 REPLIES 3

webiq-sk
Frequent Contributor

The reason is probably that the user is using WebIQ 2.11 Server on ctrlX with WebIQ Designer version 2.13:
[2023-01-26T16:58:58.872Z] [-sys-] visuals version: 2.13.0 edda402.32934
[2023-01-26T16:58:58.872Z] [-sys-] designer version: 2.13.0
[2023-01-26T16:58:58.927Z] [warn ] [SocketConnection] unable to check whether client is on local network interface
[2023-01-26T16:58:58.930Z] [-sys-] connect info: 2.11.3 release/2.11.3 (f3eb64e3) null
[2023-01-26T16:59:01.734Z] [error] Error retrieving license information: Backend does not know the API command 'connect.license.now'. This may be a bug. Please make sure you are using a matching version of WebIQ Server before reporting this.

This is not supported. The versions always have to match.

The solution would be to restore the HMI project from backup or the VCS.

Can you please define what "WebIQ designer perform a unexpected/unplanned restart" means? Can you please attach any screenshots from Windows Event viewer that illustrate this?

I will inform the customer to align their version of server and designer.

As for what does "WebIQ designer perform a unexpected/unplanned restart" mean.

Quote from user

"

While working within Designer, the whole application closed/disappeared from the screen and then reappeared as it would when you double click on desktop icon for the first time. All recent changes to project in the workspace were lost.

"

webiq-sk
Frequent Contributor

I have never heard of any such issue with WebIQ Designer. As such any event viewer logs from the exact time when it happened might be useful. However, the reason probably is the version mismatch as this is not supported.

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist