Debugging in Visual Studio 2010 Express

[jonathan.cronin]

When I launch the visual studio debugger from iX developer it takes me to the project conversion wizard, is this correct?

During conversion visual studio intellisense crashes. After conversion I get the error about .NET version 4 not being installed.

Upon retargetting the project to .NET 3.5 the project will not load giving an error message about outputCF already existing in the solution.

If i restart the debugger at this point the solution loads with 1 error and 8 warnings.

The error is: "A problem occurred while trying to set the "References" parameter for the IDE's in-process compiler. Error HRESULT E_FAIL has returned from a call to a COM component"

7 of the warnings are about the parent .cs files egTags.cs not being found in the project file.

There is one warnning about confilicts between different versions of the same depenent assembly.

This project works fine in iX developer and on an iX T60.

Has anybody had experiance of VS debugger problems converting projects?

Any help would be greatly appreciated.

Here is the output from the VS compiler

------ Build started: Project: outputCF, Configuration: Debug x86 ------
No way to resolve conflict between "System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" and "System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089". Choosing "System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" arbitrarily.
Consider app.config remapping of assembly "System.Transactions, Culture=neutral, PublicKeyToken=b77a5c561934e089" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_32\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Runtime.Serialization.Formatters.Soap, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Runtime.Serialization.Formatters.Soap\2.0.0.0__b03f5f7f11d50a3a\System.Runtime.Serialization.Formatters.Soap.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization.Formatters.Soap\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Runtime.Serialization.Formatters.Soap.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Web.Services, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Web.Services\2.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "UIAutomationTypes, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "3.0.0.0" [C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\UIAutomationTypes.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\UIAutomationTypes\v4.0_4.0.0.0__31bf3856ad364e35\UIAutomationTypes.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "Microsoft.VisualC, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "8.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualC\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualC.dll] to Version "10.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualC\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualC.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.EnterpriseServices, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Web.RegularExpressions, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Web.RegularExpressions\2.0.0.0__b03f5f7f11d50a3a\System.Web.RegularExpressions.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.RegularExpressions\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.RegularExpressions.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Configuration, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll] to Version "3.5.0.0" [C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll] to Version "3.5.0.0" [C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Printing, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "3.0.0.0" [C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\System.Printing.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Printing\v4.0_4.0.0.0__31bf3856ad364e35\System.Printing.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.DirectoryServices.Protocols, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.DirectoryServices.Protocols\2.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.Protocols.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices.Protocols\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.Protocols.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "PresentationFramework, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "3.0.0.0" [C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\PresentationFramework.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\PresentationFramework\v4.0_4.0.0.0__31bf3856ad364e35\PresentationFramework.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Configuration.Install, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Configuration.Install\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.Install.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration.Install\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.Install.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.ServiceProcess, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.ServiceProcess\2.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Security, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Security\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Security.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "WindowsBase, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "3.0.0.0" [C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\WindowsBase.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\WindowsBase\v4.0_4.0.0.0__31bf3856ad364e35\WindowsBase.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Runtime.Remoting, Culture=neutral, PublicKeyToken=b77a5c561934e089" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Runtime.Remoting\2.0.0.0__b77a5c561934e089\System.Runtime.Remoting.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Remoting\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Remoting.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Data.OracleClient, Culture=neutral, PublicKeyToken=b77a5c561934e089" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_32\System.Data.OracleClient\2.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Data.OracleClient\v4.0_4.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Core, Culture=neutral, PublicKeyToken=b77a5c561934e089" from Version "3.5.0.0" [C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Core.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "ReachFramework, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "3.0.0.0" [C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\ReachFramework.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\ReachFramework\v4.0_4.0.0.0__31bf3856ad364e35\ReachFramework.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Data.SqlXml, Culture=neutral, PublicKeyToken=b77a5c561934e089" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Data.SqlXml\2.0.0.0__b77a5c561934e089\System.Data.SqlXml.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Data.SqlXml\v4.0_4.0.0.0__b77a5c561934e089\System.Data.SqlXml.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Web, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_32\System.Web\2.0.0.0__b03f5f7f11d50a3a\System.Web.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Web\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "PresentationUI, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "3.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\PresentationUI\3.0.0.0__31bf3856ad364e35\PresentationUI.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\PresentationUI\v4.0_4.0.0.0__31bf3856ad364e35\PresentationUI.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Data, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll] to Version "3.5.0.0" [C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Data.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Data, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll] to Version "3.5.0.0" [C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Data.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Xml, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll] to Version "3.5.0.0" [C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Xml.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Xml, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll] to Version "3.5.0.0" [C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Xml.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "PresentationCore, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "3.0.0.0" [C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\PresentationCore.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_32\PresentationCore\v4.0_4.0.0.0__31bf3856ad364e35\PresentationCore.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Drawing.Design, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Drawing.Design\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.Design.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing.Design\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.Design.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "UIAutomationProvider, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "3.0.0.0" [C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.0\UIAutomationProvider.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\UIAutomationProvider\v4.0_4.0.0.0__31bf3856ad364e35\UIAutomationProvider.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.DirectoryServices, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.DirectoryServices\2.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Deployment, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Deployment\2.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Deployment\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "Accessibility, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\Accessibility\2.0.0.0__b03f5f7f11d50a3a\Accessibility.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Accessibility\v4.0_4.0.0.0__b03f5f7f11d50a3a\Accessibility.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Design, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "2.0.0.0" [C:\WINDOWS\assembly\GAC_MSIL\System.Design\2.0.0.0__b03f5f7f11d50a3a\System.Design.dll] to Version "4.0.0.0" [C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Design\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Design.dll] to solve conflict and get rid of warning.
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360,9): warning MSB3247: Found conflicts between different versions of the same dependent assembly.
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.Targets(160,9): error MSB3081: A problem occurred while trying to set the "References" parameter for the IDE's in-process compiler. Error HRESULT E_FAIL has been returned from a call to a COM component.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

[Ron L.]

I wrote an FAQ about Debugging in iX Developer that may help.
http://ixtalk.beijerelectronics.com/vie ... hp?f=9&t=6

There are def. some challenges with debugging. You may need to change the application to be a PC type temporarily for debugging and then change it back.

[wlederer]

I tried debugger as well. Ar first, found, that the default debug program is different than Ron wrote in the topic:
C:\Program Files\Common Files\Microsoft Shared\MSEnv\VSLauncher.exe
Why and what is the difference? I put the path advised by Ron:
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\VCSExpress.exe
clicked the debug button. The Visual Studio 2010 express started with the Conversion Wizard. If I allow to convert my project, will it work?
A week ago i had my project broken, after download the picture on HMI screen did not update but the previous version of the project were OK. Yesterday I had again suspicious behave.
Is the reason for this, my "playing" with programming or debugging?

regards, Wal

[Ron L.]

If you are not writing your own C# script, have some level of expertise using Visual Studio and C#, then I do not see a reason use the Debugger.

What is the issue that you are having in your project?

[wlederer]

Hi Ron, thank You for the answer. I do a project with T7A Beijer panel and Mitsubishi PLC FX3U. PLC controls a water treatment equipment for ships and the panel except usual functions, should save results of equipment operations and an information from a GPS sensor on different medias (USB, SD-card, SMS, printer, email..). Probably, the script programming is helpfull for the task?
I tried to write script to show flow of the process on HMI screen. Sometimes it worked OK, sometimes not. Debugger was launched to find out the reason, but without success.
Twice the project was broken. It was no error messages, but after changing a screen layout and downloading the picture on the HMI screen did not change at all, and I had to return to the previous versions. May be, some files were upgraded to the later version by Visual Studio 2010 Express and after that they became anaccessable for iX Developer?
How can I learn the debugger? Is it part of Visual Studio? Is the Express version of VS enough for the job, or do You recommend to get something more advanced?
Wal

[Ron L.]

I would recommend surrounding any script you write with try/catch blocks to make sure if any errors occur, you handle them and your application doesn't crash.

try {
//your code here
}
catch (Exception ex)
{
MessageBox.Show("error occured")
}

There's also thousands of C# and Visual Studio tutorials on the world wide web if you need some help in that area.
http://www.homeandlearn.co.uk/csharp/csharp.html

The Visual Studio debugger is only going to take you so far because you cannot debug the .NET Compact Framework 3.5 in it through iX. The code runs differently on the WinCE-based terminals than on your PC. You may see different behavior.

[wlederer]

Thank You,
how can I check what operating system is installed on the panel?

[Ron L.]

If it is an iX HMI Panel listed here
https://www.beijerelectronics.com/en/Pr ... r___panels
then its underlying operating system is Windows Embedded CE 8.0/6.0.

If it is an Industrial PC shown here
https://www.beijerelectronics.com/en/Pr ... anel___PCs
then it could have Windows XP Embedded, Windows XP or Windows 7 depending on the options for the PC panel.

[wlederer]

I would recommend surrounding any script you write with try/catch blocks to make sure if any errors occur, you handle them and your application doesn't crash.

try {
//your code here
}
catch (Exception ex)
{
MessageBox.Show("error occured")
}

There's also thousands of C# and Visual Studio tutorials on the world wide web if you need some help in that area.
http://www.homeandlearn.co.uk/csharp/csharp.html

The Visual Studio debugger is only going to take you so far because you cannot debug the .NET Compact Framework 3.5 in it through iX. The code runs differently on the WinCE-based terminals than on your PC. You may see different behavior.

Thank You Ron. The C# lessons are very helpful. Now I came to the chapter "Databases". A database program (like SQL Server Express or Access) is required to be installed. Actually, the SQL Server Express 2005 is already installed. But something is wrong with it. After start it does not show that it is running. Another program on laptop, WinCC flexible 2008 is installed and use the SQL Server Express. So, I am not sure if I should try to "fix" it. What do You recommend, install Access?

[Ron L.]

Sorry, your going beyond the realm of iX support here. If you try a google search of "sql server 2005 express installation guide", there is a lot of helpful information out there.