Important Details - Electrolux



SidekickKnowldedgeKnowledge baseRev 1.2 - DATE \@ "MMMM d, yyyy" \* MERGEFORMAT February 25, 2016Contents TOC \o "1-3" \h \z \u Important Details PAGEREF _Toc444156996 \h 4KB0001.: SidekickPC Default Update Dialog Parameters PAGEREF _Toc444156997 \h 4KB0002.: New 982 service kit coding rule for cooking board PAGEREF _Toc444156998 \h 5Update : 982 service kit coding for alphanumeric ANC codes PAGEREF _Toc444156999 \h 6General Issues PAGEREF _Toc444157000 \h 8KB0004.: Disabling Symantec Antivirus PAGEREF _Toc444157001 \h 8KB0005.: How to Start or Stop Services in Windows PAGEREF _Toc444157002 \h 11KB0006.: Miscellaneous problems caused by the antivirus - The Sidekick setup program quits abnormally PAGEREF _Toc444157003 \h 14KB0007.: AVIRA Antivirus PAGEREF _Toc444157004 \h 15Database Update Issues PAGEREF _Toc444157005 \h 18KB0008.: Database Update Issues: Cannot connect to the web service PAGEREF _Toc444157006 \h 18KB0009.: Database Update Issues: Remote web service connection error: WSE910 PAGEREF _Toc444157007 \h 20KB0010.: Database Update Issues: - "Hashes are different" PAGEREF _Toc444157008 \h 21KB0011.: Database Update Issues: - "FOREIGN KEY constraint” PAGEREF _Toc444157009 \h 22KB0012.: Database Update Issues: - "UPDATE PROCEDURE FAILED. The operation has timed out” PAGEREF _Toc444157010 \h 23KB0013.: Database Update Issues: - “The Update Procedure has not been correctly initialized” PAGEREF _Toc444157011 \h 24KB0014.: Database Update Issues: - The update does not start or it hangs or stops after a while. PAGEREF _Toc444157012 \h 25KB0015.: Could not load file or assembly ‘Microsoft.ApplicationBlocks.Updater,Version 2.0.0.1…’ PAGEREF _Toc444157013 \h 26Setup and Automatic Update Issues PAGEREF _Toc444157014 \h 26KB0016.: Setup Issues: Setup failed - no package <sqlncli.msi> PAGEREF _Toc444157015 \h 26KB0017.: Setup and Activation Issues: SQL Server 2005 Express Install Errors 29503 or 1067 PAGEREF _Toc444157016 \h 27KB0018.: Setup and Activation Issues: SQL Server 2005 Express - error during installation on Windows XP Service Pack 3 PAGEREF _Toc444157017 \h 28KB0019.: Setup and Activation Issues: “The system administrator has set policies to prevent this installation” error message, while installing MSXML 6.0 MSXML 6.0 PAGEREF _Toc444157018 \h 29KB0020.: Setup and Activation Issues: MSXML 6.0 problems: cannot install SQL Server PAGEREF _Toc444157019 \h 30KB0021.: Setup and Activation Issues: “An instance with the same name is already installed on this computer” error message, while installing SQL Server PAGEREF _Toc444157020 \h 31KB0022.: Setup and Activation Issues: “The SQL Server service failed to start” error message, while installing SQL Server PAGEREF _Toc444157021 \h 32KB0023.: Setup and Activation Issues: SidekickPC installation fails under MS Windows Vista PAGEREF _Toc444157022 \h 33KB0024.: Setup and Activation Issues: SidekickPC installation fails while creating the database PAGEREF _Toc444157023 \h 34KB0025.: Setup and Activation Issues: SidekickPC installation fails with “SQL Server 2005 or later is required to install this application” message PAGEREF _Toc444157024 \h 35KB0026.: Setup and Activation Issues: SidekickPC installation succeeds but the program issues an unexpected exception with Microsoft.Web.Services3 assembly when you start the update PAGEREF _Toc444157025 \h 36KB0027.: Upgrade to SidekickPC 3.4: the application failed to initialize properly [only for Windows XP O.S.] PAGEREF _Toc444157026 \h 37KB0028.: ERROR 1001 Sqlcmd Error: Connection failure. SQL Native Client is not installed correctly PAGEREF _Toc444157027 \h 41KB0029.: Windows 10 compatibility PAGEREF _Toc444157028 \h 42Note 1: Preliminary step for Windows10 (the same as Windows 8\8.1) PAGEREF _Toc444157029 \h 42Note 2: The Windows 10 operating system no longer supports Microsoft SQL Server 2008 R2 Express. PAGEREF _Toc444157030 \h 42Programming ERRORS PAGEREF _Toc444157031 \h 44KB0001.: Board electronic programming procedure – technical information PAGEREF _Toc444157032 \h 44SidekickPC programming procedure steps PAGEREF _Toc444157033 \h 44Boot firmware variant for cooking (Ram Loader) PAGEREF _Toc444157034 \h 44Electronics that implement boot loader PAGEREF _Toc444157035 \h 45Common programming errors with electronics that implement boot loader PAGEREF _Toc444157036 \h 45Failure (NO_BOOTACTIVATION_SELECTION) PAGEREF _Toc444157037 \h 45Failure (BOOTACTIVATION_SELECTION_FAILED) PAGEREF _Toc444157038 \h 45Failure (BOOTACTIVATION_SELECTION_ERROR) PAGEREF _Toc444157039 \h 45KB0002.Dish care - Programming ERROR The programmed firmware (P100R112) does not match.. PAGEREF _Toc444157040 \h 47KB0003.Dish care - Programming ERROR: Object reference not set to an instance of an object PAGEREF _Toc444157041 \h 49KB0004.Dish care - Programming ERROR: Error verifying the result of the board programming procedure. Offending Memory Location: 0000H in Memory Bank 0 PAGEREF _Toc444157042 \h 49KB0005.Fabric Care - Programming ERROR: Error reading memory from the electronic board. PAGEREF _Toc444157043 \h 51KB0006.All - Programming ERROR: Cannot connect to the electronic board (with no boot loader) PAGEREF _Toc444157044 \h 53KB0007.: Oven – ATTENTION! Visual Cooking Update (VCU) workaround for programming PAGEREF _Toc444157045 \h 55KB0008.: Hob – UIs programming for hob with more than one user interfaces PAGEREF _Toc444157046 \h 56USB Driver Issues PAGEREF _Toc444157047 \h 58KB0009.: Diagnostic operation error – Unable to load DLL ‘DirectMacs.dll’ PAGEREF _Toc444157048 \h 58The operating system cannot run. PAGEREF _Toc444157049 \h 581.To Check the Driver version installed PAGEREF _Toc444157050 \h 582.Uninstall old driver from the PC PAGEREF _Toc444157051 \h 603.Update driver PAGEREF _Toc444157053 \h 62KB0010.: Diagnostic operation error – Unable to load DLL ‘DirectMacs.dll’ PAGEREF _Toc444157054 \h 65The specified module could not be found. PAGEREF _Toc444157055 \h 65KB0011.: SidekickPC "The system cannot find the file specified" during the installation of the AMI device [only for Windows XP O.S.] PAGEREF _Toc444157056 \h 66License Activation Issues PAGEREF _Toc444157057 \h 67KB0012.: Cannot activate the software license PAGEREF _Toc444157058 \h 67KB0013.: License activation Errors: PAGEREF _Toc444157059 \h 701.The specified module could not be found. (HRES 0x8007007E) PAGEREF _Toc444157060 \h 702.Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)) PAGEREF _Toc444157061 \h 703.Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED)) PAGEREF _Toc444157062 \h 70Important Details: SidekickPC Default Update Dialog Parameters Name and Password for accessing the local database are always SidekickPCUserThey are the same for all users!Password is case-sensitive(local)\SQLEXPRESSSidekickPCInsert your personal User Name and Password here that you receive by e-mail.Password is case-sensitive? Name and Password for accessing the local database are always SidekickPCUserThey are the same for all users!Password is case-sensitive(local)\SQLEXPRESSSidekickPCInsert your personal User Name and Password here that you receive by e-mail.Password is case-sensitive?: New 982 service kit coding rule for cooking boardAugust 4, 2014To solve the pending issues on the data flow for Spare Operations concerning cooking electronic boards, a new Service Kit coding scheme for the Food Preparation product line has been approved. The Service Kit Code (SKC) identifies the code of the kit for a configured electronic board, for direct replacement on a specific appliance model (PNC/ELC).At the moment the new rule is applied only for new kit codes for Food Preparation product line.The Spares Documentation team has started using the new service kit codes since 19th May 2014.All cooking boards coded before 19th May 2014 use the old 973-982 rule (this rule is still valid also for all others product lines)New 982 kitThe new 982 service kit code is a 13-digit code. It is defined according to the following convention:PrefixANCTDS check digit982561 21 65-416982 prefix: it is a fixed prefix (3 digit)ANC: it is the Article Number Code that identifies the variant software of the board (9 digit)TDS check digit: It consists of a single digit computed automatically by an algorithm from the other digits in the sequence input. It is used for error detection. (1 digit)See examplePNC: 949596300 ELC 00 – split user interface induction boardsBoard w. E.TaffelANCSeniorityResulting kitUI left561 21 65-41do not care982561 21 65-41 / 6UI middle561 21 65-34do not care982561 21 65-34 / 1UI right561 21 65-26do not care982561 21 65-26 / 7The benefits from new 982 coding are:Significant reduction in the number of service kit code; a 982 service kit code can be used for different appliance;The service kit prefix is fixed - no dependencies on ANC seniority. It is possible to update the list of spare boards at a later time;Significant reduction of IT architecture complexity to populate the central database: since the kit code embeds the original factory ANC code, it is no longer necessary the automatic software procedure that exports all information about electronic boards from factory bill of material system (COPICS). This means that the central database can be updated only with a lookup in the Technical Documentation System database (TDS). Update : 982 service kit coding for alphanumeric ANC codesSeptember 1, 2015Due to the fact that soon the ANC codes will start with alphanumeric character for electronics (i.e. A03726202) and the Technical Documentation System operates only on the digits, the Spares Operation team introduced a translation mechanism that converts automatically A to a prefix number.So if the ANC for electronics is: A03726202, the new 982 service kit code will be a 15-digit code:PrefixANC PrefixANCTDS check digit98214003 7262-025982 prefix: it is a fixed prefix (3 digit)ANC Prefix: it is the prefix that correspond to the first character of the ANC code A => prefix 140 (3 digits) ANC: it is the Article Number Code that identifies the variant software of the board, except the first char A (the latest 8 digits of the ANC code)TDS check digit: It consists of a single digit computed automatically by an algorithm from the other digits in the sequence input. It is used for error detection. (1 digit)97X kitThe 97X kit is always a 15-digit code.PrefixPNCELCcheck digit973 to 982XXXXXXXXXXXX973 to 982: reserved prefixes in TDS are from 973 to 982. This means that each PNC/ELC can define up to 10 different configured boards. PNC: the Product Number Code that identifies the appliance modelELC: the Engineering Level Code that identifies the appliance modelCheck digit: It consists of a single digit computed automatically by an algorithm from the other digits in the sequence input. It is used for error detection.The actual value of the prefix within the same PNC/ELC depends on the numeric value of the ANC of the board used in production. The SKC prefix is assigned in ascending order with respect to the ascending order of the ANC. In other words, the lowest prefix (973) is assigned to the board with the lowest ANC. See examplePNC: 94959 60 88 ELC 01 – split user interface induction boardsBoard w. E.TaffelANCSeniorityResulting kitUI right561 21 65-34197394959 60 88-01 / 4UI left561 21 65-35297494959 60 88-01 / 3General Issues: Disabling Symantec AntivirusYou should keep Symantec Endpoint Protection running at all times, but occasionally you may have to disable it in order to install other programs.To disable Symantec Endpoint Protection, open Symantec Endpoint Protection and then click Change settings from the left menu bar.Click Configure Settings next to Antivirus and Antispyware Protection. Click the File System Auto-Protect tab and uncheck the box labeled Enable File System Auto-Protect. Click OK.Click Configure Settings next to Proactive Threat Protection. Uncheck the boxes labeled Scan for trojans and worms and Scan for keyloggers. Click OK.Important: It is imperative that you reenable Symantec Endpoint Protection once you are done installing programs that required you to disable it. To reenable:Open Symantec Endpoint Protection and then click Change settings from the left menu bar.Click Configure Settings next to Antivirus and Antispyware Protection. Click the File System Auto-Protect tab and check the box labeled Enable File System Auto-Protect. Click OK.Click Configure Settings next to Proactive Threat Protection. Check the boxes labeled Scan for trojans and worms and Scan for keyloggers. Click OK.: How to Start or Stop Services in WindowsServices are a computer program or process that runs in the background and provides support to other programs. This will show you how to start or disable a Windows 7 service of your choice. You must be logged in as an administrator to start or disable Services. To Start, Stop, and Disable Services in "Services" Window Open the Control Panel (icons view), click on the Administrative Tools icon, click on Services, and go to step 3 below OR Open the Start Menu, type services.msc in the search box, press Enter, and go to step 3 below. (See screenshot below) OR Open the Start Menu, select Run and type services.msc then click on OKRight click on the service you want to disable or start and click on Properties. (See screenshot below) Startup type must be set to Automatic and click Apply (See screenshots below step 6) Click on the Start button if the Service status is Stopped and you want start the service. Click on the Stop button if the Service status is Started and you want to stop the service. Click on OK. (See screenshots below) : Miscellaneous problems caused by the antivirus - The Sidekick setup program quits abnormallySome antivirus software may detect false “positives” when you upgrade, install or use the software. If this happens, the antivirus prevents SidekickPC installation, update, and operation.For this reason, you are STRONGLY SUGGESTED to disable antivirus software during installation or upgrade phase. However, even this action may not be sufficient.In general, to solve this issue once and for all, you should add SidekickPC software to the “exception list” of the antivirus.Please remember that some antivirus may be configured with disabled notifications. In this case, you may experience a bad operation of the software without getting any information from the antivirus.You should enable the notification feature of your antivirus.The Sidekick setup program quits abnormallyThe antivirus software may prevent the setup from completing the installation. This happens because the antivirus prevents from copying the executable files of the program to the installation folder.One symptom of this problem is that, after the setup the desktop icon is not created.In addition, you cannot find the SidekickPC.exe file in the installation folder (by defauilt C:\Electrolux\SidekickPC).WHO IS AFFECTEDSome Avira users. Other antivirus software may cause the same problem.SOLUTIONIf SidekickPC entry is present in Control Panel “Programs” applet, uninstall SidekickPC;Disable the antivirus;Run again the setup.: AVIRA AntivirusAvira Antivirus could detect SidekickPC.exe as a malware.Avira reports that in the package is present the malware TR/Dropper.Gen.In this regard, the SidekickPC Ver 3.0.0.0 has not been checked with all the antivirus packages. As a consequence, you may find this type of problems also with other antivirus.This is actually something called a "false positive" (i.e. not a true indication the presence of a malware) due to the fact that SidekickPC 3.0.0.0 uses a mechanism of obfuscation of the DLLs that the scanner of Avira detects as malicious software.WHO IS AFFECTEDAvira users.SOLUTIONYou can add exceptions in Avira Scanner and Guard Exceptions.Double-click the red Avira icon in the taskbar next to the system clock.And then click the "Extras" menu and select the "Configure AntiVir” command.Click the "Expert Mode" check-box in the upper left corner to enable "Expert Mode."Click the "plus" sign next to "Guard" in the left column.Double-click "Scan" and select "Exceptions".Click the "Browse" button (button with three dots). Navigate to and click the program folder of the program or application for which you want to make an exception to Avira scanning. You should choose the executable file of SidekickPC that by default is C:\Electrolux\SidekickPC\SidekickPC.exe. Click "OK".If necessary you need to launch SidekickPC application and then add also the corresponding process as “obmitted”.Click the "Add" button to create a new exception of the process:Click the "plus" sign next to "Scanner" in the left column. Double-click "Scan" and click "Exceptions".Click the "Processes" button and then select the SidekickPC.exe application.Click "OK". Click the "Add" button. Click the "Apply" button and then "OK" to close the Avira window.Database Update Issues: Database Update Issues: Cannot connect to the web service This is a systematic error that may occur whenever you start an update or you press the Test Connection button in the Update dialog box. The error may consist in an error or timeout message.Most likely reasons of this problem: Incorrect parameters specified in the Internet Settings dialog box. A firewall or antivirus software prevents SidekickPC from correctly interacting with the remote web service. SolutionEnsure that the Internet Settings dialog specifies correct values; In a firewall or antivirus is running, disable the function that blocks the web access in SidekickPC. According to the experience collected so far, both the McAfee and the ESET NOD32 Antivirus are able to interfere with the web access in SidekickPC. Other antivirus application are probably able to prevent the proper operation of SidekickPC. The following section briefly describes how to change the configuration of ESET NOD32 Antivirus so that it lets SidekickPC properly work. The following steps refer to version 3.0.650.0 and may differ among the different version of this software: Ensure that ESET NOD32 Antivirus is activated. Activate it if necessary. This program interferes with SidekickPC even if it not activated; Open the management console, go to the Setup section and select Toggle Advanced mode: Select the “Enter entire advanced setup tree” command: In the selection tree at the left side of the dialog, select Web Access Protection >> HTTP >> Web browsers.Locate the SidekickPC.exe program in the “Internet browsers” list. You should click the option box related to SidekickPC until you exclude it from content filtering. In other words a red cross should appear in the box as the following figure shows: Press OK to complete the setup of the antivirus. : Database Update Issues: Remote web service connection error: WSE910 When this problem occurs the update aborts at the very beginning of the update with the following error: When this error occurs, please try pressing the “Test connection” command button, in the Update dialog, located at the right side of the web URL. Please check if the error dialog: shows the “Incoming message does not meet security requirements”: Most likely reasons of this problemThis is a security issue caused by the date and time set in your PC. For security reasons, the web service does not allow connections to clients if the time difference between the server and the client is greater than 24 hours (86400 seconds). The date/time of the web server is set to the standard Central European Time (CET). Solutionquit SidekickPC; if necessary, set the correct date and time in your PC (you can use your local time); fix the URL you specify to reach the web service; finally, restart Sidekick. : Database Update Issues: - "Hashes are different" This error may occur during a FULL update. ReasonThe reason of this error is because the FULL update procedure occurs while the server runs another scheduled task related to the full update. The scheduled task in the server occurs daily at about 21.00 (9.00 PM) CET and it consists in the preparation of the files that are transferred to the client during the FULL update. When a FULL update occurs while the server changes the files for the FULL update itself, a "Hashes are different" error occurs and the update fails. When the connection line is very slow, it is likely that it starts before 9.00 PM and it ends after the server has changed the files. WorkaroundAvoid starting a full update that ends after 9.00 PM CET. With a slow connection, in Europe, start the update in the morning or in the evening after 9.30 PM CET to be sure it completes on time. This problem will be solved as soon as possible. It will not be necessary to update the SidekickPC software to fix this problem. : Database Update Issues: - "FOREIGN KEY constraint” This error may occur during an INCREMENTAL update. ReasonThis error occurs because the previous INCREMENTAL update happened while some changes to the service data occurred at the same time. In the web server there is a software bug that incorrectly sets the “last update time” at the end of the update. Instead the “last update time” should refer to the beginning of the update. WorkaroundRun a FULL update instead of an INCREMENTAL update. This problem will be solved as soon as possible, starting probably from version 2.0. It will not be mandatory to update the SidekickPC software to fix this problem. : Database Update Issues: - "UPDATE PROCEDURE FAILED. The operation has timed out” This error occurs only with INCREMENTAL updates when you are using a very slow internet connection. The error occurs during the “synchronization of deleted records” step (step #4). In order to allow the synchronization of the deleted records, SidekickPC and the web server exchange files that are rather big. The exchange of big files may cause timeout errors. WorkaroundNone. Try incrementing the value of “Connection timeout” in the Update dialog. If the error is systematic, run a FULL update instead of an INCREMENTAL update. This problem will be solved as soon as possible. It will be mandatory to update also the SidekickPC software to fix this problem. : Database Update Issues: - “The Update Procedure has not been correctly initialized” This error occurs very sporadically with INCREMENTAL updates. The reason is still unknown. WorkaroundIf you repeat the update, the procedure succeeds. : Database Update Issues: - The update does not start or it hangs or stops after a while. This error may occur with certain proxy settings, while executing the update from within the Electrolux intranet. This is an issue in network or proxy settings. WorkaroundFirst of all, please ask your IT administrator for help. As a quick workaround, you can try using the following Internet Settings: The above options should work fine in most cases within the Electrolux intranet. : Could not load file or assembly ‘Microsoft.ApplicationBlocks.Updater,Version 2.0.0.1…’Setup and Automatic Update Issues: Setup Issues: Setup failed - no package <sqlncli.msi> This is a known problem in SQL Server 2005 installation procedure. This issue is described in detail here: HYPERLINK "" \h workaround First of all, the automatic installation procedure of SidekickPC employs a setup of SQL Server Express where all components are extracted in advance. This allows removing the SQL Server Native Client component before SQL Server 2005 installation by issuing the following command: msiexec /x "%cd%\SqlExpress\Setup\sqlncli.msi" /passive : Setup and Activation Issues: SQL Server 2005 Express Install Errors 29503 or 1067 This is a known problem in SQL Server 2005 installation procedure. This issue is described in detail here: HYPERLINK "" \h HYPERLINK "" \h 4163-bde2-ccb460298b54/ Manual workaround Run SQL Server 2005 Express setup and on the first page uncheck ‘Hide advanced configuration options’ box. Proceed up to the dropdown list (on the page ‘Service Account’) says ‘Network Service’ and change its value to ‘Local Service’. The last thing to do is to modify Authentication method from ‘Windows authentication’ to the ‘Mixed Mode’ authentication and provide a strong password below. After that complete the installation process. : Setup and Activation Issues: SQL Server 2005 Express - error during installation on Windows XP Service Pack 3 This is a problem in the installation procedure of SQL Server 2005. The problem occurs in Windows XP Service Pack 3 with a language different from English, as the following link describes: HYPERLINK "" \h AutoInstall workaround Before the installation of SQL Server 2005 installs Microsoft XML Core Services 6.0 Service Pack 1: ‘msiexec /i "%cd%\msxml6_x86.msi" /quiet’ : Setup and Activation Issues: “The system administrator has set policies to prevent this installation” error message, while installing MSXML 6.0 MSXML 6.0This is a known problem in SQL Server 2005 installation procedure. This issue is described in detail here: HYPERLINK "" \h HYPERLINK "" \h 485f-8785-ffddb5038399/ HYPERLINK "" \h and here: Manual workaround Before SQL Server 2005 installation, use the Windows Installer Cleanup Utility (available here: HYPERLINK "" \h HYPERLINK "" \h ) to remove the installation configuration for MSXML 6.0 Parser. : Setup and Activation Issues: MSXML 6.0 problems: cannot install SQL Server This is the problem of SQL Server 2005 installation. The problem caused by the fact that MSXML 6.0 is not correctly installed. As a consequence, the installation of SQL Server fails. Symptomgo to Control Panel and open the ‘Add or Remove Programs’ applet. The MSXML 6.0 Parser software appears like installed. However it is not possible to remove or up update it. Manual workaround Before SQL Server 2005 installation, use the Windows Installer Cleanup Utility (available here: ) to remove the MSXML 6.0 Parser entry. : Setup and Activation Issues: “An instance with the same name is already installed on this computer” error message, while installing SQL Server This is a problem in SQL Server 2005 installation/remove procedure. The problem is caused by dirty registry settings from a previous installation of SQL Server, as the following link explains:: HYPERLINK "" \h Manual workaround This workaround consists in cleaning registry settings. Click on the Start menu, choose Run and type ‘regedit’ Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server Remove ‘SQLEXPRESS’ from the ‘REG_MULTI_SZ’ value named ‘InstalledInstances’ Delete the subhive named ‘MSSQL.1’ Delete the subhive named ‘SQLEXPRESS’ Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Instance Names\SQL Delete the value named ‘SQLEXPRESS’ Delete the folder ‘%ProgramFiles%\Microsoft SQL Server\MSSQL.1’ AutoInstall workaround To work around the problem ‘AutoInstall.cmd’ executes a custom utility that cleans dirty registry settings in case of need, before running the SQL Server 2005 installation: ".\SQL 2005 Detection.exe" -DETECTONLY –CLEANDIRTYREGISTRY : Setup and Activation Issues: “The SQL Server service failed to start” error message, while installing SQL Server This is the problem of SQL Server 2005 installation. The problem could be in the NETWORK SERVICE account, under which SQL Sever service runs by default. There are two possible reasons: The NETWORK SERVICE account does not exist The NETWORK SERVICE account exists but it has no Full Control permission on the Protect folder. Manual workaround Manually change permission settings for NETWORK SERVICE. Please remember that in other languages the term “NETWORK SERVICE” is translated (for example in Italian it is displayed as “Servizio di rete”). Open ‘My Computer’. Type ‘C:\Documents and Settings\NetworkService\Application Data\Microsoft’ in the address bar, and then press ‘ENTER’. Right-click the ‘Protect’ folder, and then click ‘Properties’. In the ‘Properties’ dialog box, click the ‘Security’ tab. Under ‘Group or user names’, determine whether NETWORK SERVICE is listed. If NETWORK SERVICE is not listed, follow these steps to add this account: Click ‘Add’ to show the ‘Select Users or Groups’ dialog box. Click ‘Locations...’, select your computer name in the ‘Locations’ dialog box, and then click ‘OK’ to return to the ‘Select Users or Groups’ dialog box. Type NETWORK SERVICE in the ‘Enter the object names to select’ box, and then click ‘Check Names’. Click ‘OK’ to close the ‘Select Users or Groups’ dialog box. Click NETWORK SERVICE under ‘Group or user names’, and then click to select the ‘Allow’ check box for ’Full Control’ under ‘Permissions for NETWORK SERVICE’. Click ‘OK’ to close the folder ‘Properties’ dialog box. Click ‘Retry’ in the error message dialog box to continue to install SQL Server Express Edition or SQL Server Express Edition with Advanced Services. SidekickPC Setup workaround Starting from version 1..1.2, the SidekickPC setup program, if necessary, creates the NETWORK SERVICE account and grants it all necessary permissions. : Setup and Activation Issues: SidekickPC installation fails under MS Windows Vista This problem occurs because the SidekickPC installer runs without full administrative privileges. It could be the consequence when you run ‘AutoInstall.cmd’ with a double click and then SideckickPC fails to access Windows registry. Manual workaround It is necessary to run the setup by right-clicking the file and selecting the “Run as administrator”. : Setup and Activation Issues: SidekickPC installation fails while creating the database This problem occurs because SidekickPC installer tries to create SidekickPC database, when ‘SidekickPC.mdf’ file already exists in the file system. It could be the consequence of uninstalling SQL Server without physically deleting the SidekickPC.mdf’ file from the file system. SidekickPC Setup workaround Starting from version 1..1.2, the SidekickPC setup program, if necessary, deletes the SidekickPC.mdf’ and SidekickPC.ldf’ files from the Data folder of SQL Server, before creating the SidekickPC local database. : Setup and Activation Issues: SidekickPC installation fails with “SQL Server 2005 or later is required to install this application” message This problem occurs because the ‘SQL 2005 Detection.exe’ utility fails because of problems in registry or WMI. Manual workaround Manually install SQL Server 2005 before running SidekickPC setup. : Setup and Activation Issues: SidekickPC installation succeeds but the program issues an unexpected exception with Microsoft.Web.Services3 assembly when you start the update This problem occurs because WSE 3.0 runtime was not installed properly during automatic setup procedure. It is also not possible to install WSE 3.0 runtime manually because of dirty registry settings. (Accompanying error message: ‘Install error 1327 Invalid Drive’.) This problem described here: Manual workaround Manually change registry settings with ‘regedit’: If necessary quit SidekickPC From the ‘Start Menu’, click ‘Start’ then click ‘Run’. The ‘Run’ dialog box opens. Type ‘regedit’, and then click ‘OK’. The ‘Registry Editor’ opens. In the ‘Registry Editor’, locate the following registry keys: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders In the right pane, verify the values in the ‘Data’ column of each entry. If any value contains a drive that is not correct for your computer, right-click the entry and select ‘Modify’. Type the correct drive letter in the ‘Value’ data field, and then click ‘OK’. Close regedit Manually install WSE 3.0 by double clicking the “Microsoft WSE 3.0 Runtime.msi” file that you can locate in the WSE3_0 folder in the SidekickPC installation set. You can also download the WSE 3.0 setup procedure from the internet. After this manual fix it is not necessary to re-install SidekickPC, just start it again. : Upgrade to SidekickPC 3.4: the application failed to initialize properly [only for Windows XP O.S.]DescriptionThe application SidekickPC failed to initialize properly.SymptomsAfter the upgrade to SidekickPC 3.4, when you launch SidekickPC nothing happens.ONLY Windows XP Home\Professional and Vista O.S. could be affected.CauseFrom SidekickPC 3.4 version, the software is targeted to .NET framework 3.5 SP1.In Windows XP Home\Professional and Vista O.S.: Microsoft .NET Framework 3.5 is not an integrated O.S. component.Microsoft .NET Framework 3.5 is missing component that SidekickPC 3.4 requires to run successfully.Resolution1. Click here HYPERLINK "" \h to download and install Microsoft .NET Framework 3.5SP1. Click Download Remove first check box and then click No thanks and continue Save the file in a temporary folder on your machine. If you are unable to download Microsoft .NET Framework from the microsoft web site, the components is also available in the Full SetupSidekickPC Full Installation Set: HYPERLINK "" \h Installation StepsDouble click dotnetfx35 file Accept the terms anc click Install > Click Exit.2. When Microsoft .NET Framework 3.5 SP1 has finished, it could be necessary to restart the computer.3. Open SidekickPC to see if the issue is resolved.: ERROR 1001 Sqlcmd Error: Connection failure. SQL Native Client is not installed correctly: Windows 10 compatibilityNote 1: Preliminary step for Windows10 (the same as Windows 8\8.1) This step that must be done manually when installing SidekickPC on Windows 8\8.1\10 before launching the AutoInstall.cmd file. This step cannot be automated and consists in enabling the .NET 3.5 Framework (if necessary):Open the Control Panel and click on “Programs”Click on “Turn Windows features on and off”Make sure that “.NET Framework 3.5 (includes .NET 2.0 and 3.0)” is selected as in the following picture:A reboot will be forced right before the installation of SQL Server 2008 R2.SidekickPC uses the Microsoft SQL Server 2008 R2 Express software. This software is automatically installed with the SidekickPC FULL setup procedure.Once your PC has rebooted, please re-launch AutoInstall.cmd and the installation will complete.When performing a new installation of the SidekickPC software on a Windows 10 system, a warning displays indicating that Microsoft SQL Server 2008 R2 is not compatible with Windows 10. Note 2: The Windows 10 operating system no longer supports Microsoft SQL Server 2008 R2 Express. The setup and the programs appear to operate with no known issues; however, a compatibility issue with SQL Server 2008 R2 has been identified and periodically, a warning message may be posted in the Windows 10 Action Center indicating an incompatibility.Programming ERRORS: Board electronic programming procedure – technical informationElectrolux boards (generally the latest ones) contain two distinct pieces of firmware (the software that provides the low level control for the board): the functional firmware and the boot firmware. Functional firmware: firmware that is active during the normal functioning of the electronic board. Boot firmware: the first firmware which executes (before the functional firmware) whenever a system is initialized. The main function of boot firmware is to initialize the board and then to "boot" (load and execute) specific activities. The boot firmware is stored in a protected area of micro-controller ROM so that, in case of failures during functional firmware programming, the boot is always available to make other attempts. A protected area cannot be erased and reprogrammed unless using specific tools.SidekickPC programming procedure stepsStep 1. BOOT ACTIVATION: the application informs all the physically connected boards (generally in our case only one board is connected) that an interaction is starting: the system sends a Boot Activation Message. Step 2. BOARD SELECTION: the application notifies all answering boards about the board it wants to interact with by sending the Board Selection Message.Step 3. BOARD EXECUTION ACTIVITIES: the application communicates with the selected board executing specific activities (i.e. programming)Step 4. BOARD RESET: the application resets all the connected boards Boot firmware variant for cooking (Ram Loader)In the case of cooking electronic boards based on Renesas micro-controllers of the family R8C, the smallest protectable area was too large. For this reason the boot is built into the functional firmware and, therefore, is not protected.After boot initialization, the functional firmware calls a special function that loads into RAM the boot executable without resetting the micro-controller. From then on, the procedure is the same. This solution is normally referred with the term RAM Loader.Electronics that implement boot loaderWashing MachineENV06 electronics (EWM1100, EWM2100, EWM2500, EWM3500) EWM09, EWM10, EWX11, EWX13 Washer DryerEWD10, EWX11Tumble DryerENV06 electronics (EDR2000)EDR10, EDR12DishWasherPB100Fridge and FreezerERF1600ERF2003Oven and Hob All user interfaces supported by SidekickVCU, Omega, HexagonRaven, KiteC, Kingfisher, FalconQC, Pelican, Crystal (Toucan)All future electronics will implement boot loader!Common programming errors with electronics that implement boot loader Failure (NO_BOOTACTIVATION_SELECTION) Cause: step 1, boot activation message is received, but no answer from the boardFailure (BOOTACTIVATION_SELECTION_FAILED) Cause: Boot activation (Step 1) success, but Board Selection (step 2) failedFailure (BOOTACTIVATION_SELECTION_ERROR) Cause: the system sends the boot activation message but it is not received (it occurs at the beginning of boot activation procedure Step 1)Possible solution Sometimes it can be resolved just disconnect the appliance cable for 60 seconds (remove power supply from the board and reset the board) and then reconnect again.This operation needs to discharge possible capacitors that can keep active the microcontroller during the boot activation procedure! Dish care - Programming ERROR The programmed firmware (P100R112) does not match..False failure while programming Dish Care PB100 boards.The procedure for verifying the result of the programming procedure will report a false failure for Dish Care boards PB100.SymptomsThe message will be as follows:Programming ERRORThe programmed firmware (P100R112) does not match with the expected firmware (P100R121) - expected firmware is the one stored in the DBN.B. Firmware identifier (P100R***) could be different. It depends on selected PNC and firmware mounted in the spare part used.CauseThe error is caused by a bug in the programming algorithm (verify procedure). ResolutionThe error message is wrong because the programming procedure has completed successfully and the board can be installed in the appliance.After programming error appears, disconnect for a few seconds the board connector in order to remove power supply from the board, then reconnect the board and try to execute a verify (or try again the programming procedure).Example PNC 911434342 02The programmed firmware must be P100R121The spare part mounted the firmware P100R112As you can see FirmwareID just programmed is the expected one (P100R121) The Verify Only procedure will end without errors.Who is affectedAll SidekickPC 3.4 users trying to programming PB100 boards!We are working on fixing the bug. The bug fix will be available soonDish care - Programming ERROR: Object reference not set to an instance of an objectMarch 6, 2015Failure while programming PB100 boards.The programming procedure will report a failure for Dish Care boards PB100.SymptomsWhen configuring the board an error message may occur:After a second attempt a second error message occurs:CauseThe error is caused by a bug in the programming algorithm for PB100. ResolutionDue to the fact that it is a blocking problem, the only workaround to this issue is the recovery of the board using Electrolux internal application that provides a deeper control on the programming procedure.Please contact Sidekick support team for the details!The bug fix will be available soon as possible.Who is affected?All SidekickPC 3.4 users.Dish care - Programming ERROR: Error verifying the result of the board programming procedure. Offending Memory Location: 0000H in Memory Bank 0March 20, 2015False failure while programming Dish Care PB300 boards.The procedure for verifying the result of the programming procedure will report a false failure for Dish Care boards PB300.SymptomsThe message will be as follows:CauseThe error is caused by wrong programming algorithm settings inside the database. ResolutionThe error message is wrong because the programming procedure has completed successfully and the board can be installed in the appliance.If you disable the Additional Verify, the programming procedure ends without error and the board is correctly programmed!!?Who is affectedAll SidekickPC 3.4 users trying to programming PB300 boards!The problem must be fixed by R&D departmentFabric Care - Programming ERROR: Error reading memory from the electronic board.Updated : February 3, 2015 DATE \@ "MMMM d, yyyy" \* MERGEFORMAT February 25, 2016False failure while programming some fabric care boards.The procedure for verifying the result of the programming will report a false failure for some fabric care platforms (actually the platforms where can occur this problem are EDR12832, FIXED (EWX13611 ??????? NOT FIXED!))EWD10931 914605703 00NOT FIXED!SymptomsIf you have enabled the additional board programming check by means of the Additional Verify command (see the Options menu), when configuring the board an error message may occur:CauseThe additional verify allows activating an extra configuration step (verify) after the board programming procedure.This failure will happen if you have enabled the Additional Verify option.The error is caused by a problem in the verify procedure. ResolutionIf you disable the Additional Verify, the programming procedure ends without error and the board is correctly programmed!!?Who is affected?All SidekickPC users (both previous and next version 3.4) trying to programming EDR12832, EWX13611 , EWD10931 boards (with the additional verify enabled)!How to fix it:We are working on a solution. The issue fix will be available soonAll - Programming ERROR: Cannot connect to the electronic board (with no boot loader)CauseIf the same error occurs during programming of different boardsThe selected COM Port is not associated to the AMI module.The Appliance Mini Interface (AMI) module or the Target Cable Connector does not work.The Secondary Power Switch in AMI module is in the OFF position while trying to configure a standalone board. If the error occurs with a specific electronic board only:The Appliance Cable does not provide good electric contacts between the module and the appliance board. The Module Connector or the Board Connector may be faultyYou are trying to use the wrong cable for the appliance or board to service.You are using the wrong connector on the target board.The appliance board is faulty.ResolutionIn order to verify the installation of the USB drivers, the correct operation of the plug-and-play features and to find out the number of the Virtual COM Port that has been set up:[WinXP] right click on My Computer then select Properties >> Hardware >> Device Manager. [Windows 7] right click on Computer then select Properties >> Device Manager. When the interface module is connected and the USB driver are correctly installed, the Device Manager should display two entries showing the name of the interface module, one under “Ports (COM & LPT)” and the other under “Universal Serial Bus controllers”: Once the driver is installed, you can find the Virtual COM Port, which was created by the USB driver, looks in Ports(COM &LPT).The Virtual COM Port number may change on different computers, when you install additional devices, or when you switch the USB connection to a different USB port.If you do not see a Virtual COM Port under Ports (COM &LPT), try to uninstall the drivers that accompanied your adapter and reinstall them. See Appliance Interface Modules USB Setup.pdf available in the USB driver folder (SidekickPC application folder)A yellow exclamation point next to the Appliance Mini Interface device in Device Manager could appear if Windows has identified a problem of some kind with that device.: Oven – ATTENTION! Visual Cooking Update (VCU) workaround for programmingWhen a standalone Vision Cooking Update (VCU) board is attached to the PC for programming, the display is black and the communication is not working (the board is in a loop resetting).Symptom: If you start the configuration when board is resetting, you will receive BOOTACTIVATION errors or sometimes the special board detection procedure could be wrongly start (see HYPERLINK \l "_:_Hob_–" KB0008)Cause: the "touch board" is not connected. Workaround: As a work-around, disconnect the board then reattach it to the PC, and touch the touch connector pins for approx. 5 sec. with your finger, to simulate the presence of the touch board Then, the firmware really wakes up, the F239 alarm appears and the board will communicate. Programming ERROR: Failure (NO_BOOTACTIVATION_SELECTION) CauseElectrolux boards (generally the latest ones) provides facilities for advanced interaction through a firmware plug-in architecture: pieces of executable code are dynamically injected into the micro-controller RAM and executed. The board contain two distinct pieces of firmware: the functional firmware and the boot (saved in a protected area of microcontroller). These 2 pieces of firmware are mutually exclusive: when one is active the other is dormant and vice versa.During the programming procedure the interaction are:1. The application informs all the physically connected boards (generally in our case only one board is connected) that an interaction is starting (Boot Initialization) 2. The application selects one of the boards (Board Selection)3. The application communicates with the selected board executing specific activities 4. The application resets all the connected boards If something goes wrong in step 1/2, this is the 'general' meaning of the Boot activation error message.ResolutionSometimes it can be resolved just disconnect the appliance cable for 60 seconds (for removing power supply from the board) and then reconnect again.This operation needs to discharge possible capacitors that can keep the microcontroller active during the initialization procedure! Only when F239 alarm appears on the display, start the configuration!: Hob – UIs programming for hob with more than one user interfacesAn hob system implements a multi-point communication, that means there is a bus connecting multiple boards (i.e., a set of boards attached to the same bus where interactions happen with one board at a time by selecting the board by its protocol address).You can have more than one HUIs (1, 2 and possibly 3) for example. The communication protocol identifies each HUI1, HUI2 , HUI3 board by its protocol address.When a technician orders a not configured electronic, it is normally pre-programmed by supplier with a firmware/configuration that could be for HUI1 or HUI2 or HUI3 (we suppose it is been programmed for HUI1).If the technician needs to configure the single board outside the appliance with a software for HUI2 it will not work because the programming algorithm tries to select HUI2 (as specified in the selected software). The spare board will correctly activate the boot firmware (RAM loader) but, due to the fact that HUI2 is selected, it will think that we want to talk with another board and the programming procedure will fail.For the above reason, the board detection below will appear:The board has not been recognized because the system tried to select HUI2 instead of HUI1By clicking next, the user will be asked to detach and reattach the board for resetting it:By pressing “Next”, a procedure will try to detect the attached board: At this point a board detection is executed and when the board is detected (HUI1) then the correct board settings (HUI1 address) for the configuration procedure will be prepared. The user will then click “Exit” to retry configuring:The user will be presented with the standard Configuration form:USB Driver Issues: Diagnostic operation error – Unable to load DLL ‘DirectMacs.dll’ The operating system cannot run.This error occurs after that you have started a diagnostic session.It is caused because in the PC are installed OLD version of USB driver (v.2.1.6.0).WHO IS AFFECTEDAll SidekickPC 3.0 users that have installed old version of USB Driver are affected.SOLUTIONTo Check the Driver version installedConnect the USB with AMI interfaceOpen Device Manager by clicking the Start button- Run and type the following command:devmgmt.mscORright-clicking on Computer icon and selecting Manage from the menuIn the tree, expand Universal Serial Bus controller,select Appliances Mini Interface and right-click on PropertiesIn Appliance Mini Interface Properties window, select Driver TabDrivers version compatible with SidekickPC 3.0 are v. 2.4.6.0 and v. 3.0.0.0Uninstall old driver from the PCUse FTDI CDM Uninstaller utility ,that it is available as a free download from the HYPERLINK "" Utilities section of the? HYPERLINK "" FTDI website (CDM Uninstaller 1.4 - Windows Device Driver Uninstaller).Supported Operating Systems:CDM Uninstaller is currently supported on the following operating systems:Windows XPWindows XP 64bitWindows VistaWindows Vista 64bitWindows 7Windows 7 64bitTo begin with, download the CDMUnistallerGUI.zip file from the FTDI website. The .zip file will contain the executable used to run the application; extract the file CDMUninstallerGUI.exe from the .zip folder and place it in an appropriate location on your system.To run the application, simply double click on the .exe file.Removing a DriverThe figure below shows the window displayed upon running the application. The Vendor ID and Product ID text boxes allow the user to enter a 4 character hex value specifying the device that they wish to remove. All installed device drivers can be viewed from within the Windows Device Manager. FTDI default Vendor ID is 0x0403, the custom Appliance Mini Interface Product ID is: 0xF741. Press Add.To create an uninstall log file, check “Generate uninstall log file” prior to removing the device. This will create a text file outlining all operations that were attempted during the removal process that will be saved in the same directory as the .exe file:To remove the device(s) click on the ‘Remove Devices’ button. The ‘Remove’ button will remove the currently selected item and the ‘Clear’ button will remove all the devices from the device window.A message box will confirm successful removal from the system and the device will be removed from the device window. Error MessagesIf there are no devices specified within the device window the following message will appear. Make sure that at least one device has been specified within the window by using the ‘Add’ button.If after attempting to remove a device the application was unable to find any devices matching the Vendor ID and Product ID the following message box will appear. In this situation make sure that the details that you have entered are indeed correct by checking with the windows device manager.The Vendor ID and Product ID must be a unique combination, if an attempt is made to add the same device twice the following message box will appear.Update old driver from the PC:Connect the USB with AMI interfaceonce you connect the interface module to the PC, the driver is not automatically installed.As a consequence you should manually update the entry generated into the Device Manager.Open Device Manager by clicking the Start button- Run and type the following command: devmgmt.mscORRight click on Computer then select Properties >> Device Managerright-clicking on Computer icon and selecting Manage from the menuexpand In the tree, expand Universal Serial Bus controller Right-click on Appliance Mini Interface and select Update Driver Software… from menu Select Browse my computer for driver software Point to the location of the USB drivers (default path is C:\Electrolux\SidekickPC\USB Drivers) then press Next Select Let me pick from a list of device drivers on my computerThe system identifies the correct driver; check “Always trust software from Electrolux Italia S.p.A.”, in order to simplify further installations of software from Electrolux, and click Install:Select the Appliance Mini Interface device on the list then press Have Disk…Just press Close to complete the installation of the USBPress Browse and point to the location of the USB drivers then press OK Just press Next to complete the updating of the USB driverPress Close: Diagnostic operation error – Unable to load DLL ‘DirectMacs.dll’ The specified module could not be found.This error occurs after that you have started a diagnostic session.It is caused because in the PC are not installed USB driver.WHO IS AFFECTEDAll SidekickPC 3.0 users that have not installed USB Driver are affected.SOLUTIONSee HYPERLINK \l "_Update_driver" KB0034 – 3. Update driver : SidekickPC "The system cannot find the file specified" "during the installation of the AMI device [only for Windows XP O.S.]DescriptionEN: AMI driver installation ends with the messages: "An error occurred during the installation of the device.The system cannot find the file specified." IT: Errore "Impossibile trovare file specificato" durante l'installazione del driver AMI SymptomsDuring the installation wizard of the AMI driver, you get an error at the end of the procedure. CauseWindows XP has a bug that it cannot properly detect new hardware by *.inf files, if the RunOnce registry key is missing for the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersionThis key is often used by installers to execute post-reboot programs, but sometimes they accidentally delete this key. ResolutionGo to Start ? Run and enter "regedit."Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceWith CurrentVersion Highlighted, go to the Edit menu and select New ? KeyName the key RunOnceThe RunOnce key should now exist underneath the CurrentVersion key.Once the key exists,restart the PCLicense Activation Issues: Cannot activate the software license This is a problem in software license activation that may occur on PCs running “Symantec Endpoint Protection” version 11.0, or a similar product. Antivirus blocks activation/deactivation of the Nalpeiron software license. Manual workaround Temporarily disable Symantec Antivirus. To disable Symantec Endpoint Protection, open Symantec Endpoint Protection and then click ‘Change settings’ on the left menu bar. Click ‘Configure Settings’ next to “Antivirus and Antispyware Protection”. Click the ‘File System AutoProtect’ tab and uncheck the box labeled “Enable File System Auto-Protect”. Click ‘OK’. Click ‘Configure Settings’ next to ‘Proactive Threat Protection’. Uncheck the boxes labeled ‘Scan for trojans and worms’ and ‘Scan for keyloggers’. Click ‘OK’. Important: you should re-enable Symantec Endpoint Protection once you are done installing programs that required you to disable it. To re-enable: Open Symantec Endpoint Protection and then click ‘Change settings’ from the left menu bar. Click ‘Configure Settings’ next to ‘Antivirus and Antispyware Protection’. Click the ‘File System Auto-Protect’ tab and check the box labeled ‘Enable File System AutoProtect’. Click ‘OK’. Click ‘Configure Settings’ next to ‘Proactive Threat Protection’. Check the boxes labeled ‘Scan for trojans and worms’ and ‘Scan for keyloggers’. Click ‘OK’. : License activation Errors: The specified module could not be found. (HRES 0x8007007E) Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))DescriptionThe software activation does not work properly.SymptomsDuring software license activation by means of the License Manager dialog, you can receive various errors Here a few error messages that can occur:The specified module could not be found. (HRES 0x8007007E)Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))CauseSidekickPC uses Windows Management Instrumentation (WMI) for gathering system configuration data from your system. If WMI is not working properly, it could cause certain information to be reported incorrectly during license activation process. WMI is a part of the operating system. To work properly, WMI relies on the WMI service. This service must be running and properly configured for your environment.?To check of your system's WMI status, you can use this procedure:Click Start and then select RunEnter wmimgmt.msc in the Open: dialog box and click OKRight click WMI Control (Local) and select PropertiesIf WMI is working properly, you will see "Successfully connected to <local computer>".If WMI is broken, you will see one or more error messages in the rmation gathered by WMI is stored in a collection of system files called a repository. If repository data becomes corrupt, WMI might not function properly.?ResolutionThe errors are addressed by the suggested hotfixes for WMI related issues on Windows platforms that improve the stability of the Windows Management Instrumentation repository.Install latest hotfixes for WMI as they can help prevent issue from recurring. XP HYPERLINK "" Windows Vista HYPERLINK "" (Windows XP) Re-registering the WMI components The .DLL and .EXE files used by WMI are located in %windir%system32\wbem directory. If you are running a 64-bit system you might also need to check for .DLLs and .EXE files in %windir%\sysWOW64\wbem.You might need to re-register all the .DLL and .EXE files in this directory. To re-register the WMI components, Copy this into Notepad as save as re.registerWMI.cmd in a temp directory (C:\temp) @echo onRegsvr32 %SystemRoot%\System32\wbem\wmidcprv.dll cd /d %windir%\system32\wbemfor %%i in (*.dll) do RegSvr32 -s %%ifor %%i in (*.exe) do %%i /RegServernet stop winmgmtnet start winmgmt:EndClick Start, Run and type CMD and type the following commands: C:\temp\re.registerWMI.cmdPress EnterThis message box may appear:Click OK, and waitThe Windows Management Instrumentation Tester window may appear, this is normal and we can go ahead to Close it (Exit).If the above doesn’t work, then(Windows XP) Rebuilding the WMI Repository Copy this into Notepad as save as fixwmi.cmd in a temp directory (C:\temp) @echo on cd /d c:\temp if not exist %windir%\system32\wbem goto TryInstall cd /d %windir%\system32\wbem net stop winmgmt winmgmt /kill if exist Rep_bak rd Rep_bak /s /q rename Repository Rep_bak for %%i in (*.dll) do RegSvr32 -s %%i for %%i in (*.exe) do call :FixSrv %%i for %%i in (*.mof,*.mfl) do Mofcomp %%i net start winmgmt goto End :FixSrv if /I (%1) == (wbemcntl.exe) goto SkipSrv if /I (%1) == (wbemtest.exe) goto SkipSrv if /I (%1) == (mofcomp.exe) goto SkipSrv %1 /RegServer :SkipSrv goto End :TryInstall if not exist wmicore.exe goto End wmicore /s net start winmgmt :Endthen Click Start, Run and type CMD (for Vista and newer, Run from elevated command prompt)Type c:\temp\ fixwmi.cmd and press EnterRepair process should take few minutes to complete. (Windows Vista, Windows 7)You can run winmgmt /verifyrepository from an elevated command prompt.If repository is found to be inconsistent, type: Winmgmt /salvagerepositoryIf the above doesn’t work, then run: Winmgmt /resetrepositoryNote this will reset repository to the initial state when the O.S. was first installed HYPERLINK "(v=vs.85).aspx" (v=vs.85).aspx: ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download