Official SEOW

Hi 4shades,
as Gross said, we still have SEDCS v.3.3.0 not running on ITA-SEOW server, the error is the same mentioned above by Badger:

************** Exception Text **************
System.BadImageFormatException: Could not load file or assembly 'Interop.ADODB, Version=2.8.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'Interop.ADODB, Version=2.8.0.0, Culture=neutral, PublicKeyToken=null'
at SEDCS.modDB.CloseDBConnection()
at SEDCS.basErr.checkDbConnect(Int32 item, Boolean addingError)
at SEDCS.basErr.checkError(Int32 item, Int32 whatError)
at SEDCS.basErr.SearchIfThereAreErrorsAndPostMessage(Int32 item, Boolean postMessageOnForm, String& str)
at SEDCS.frmMain.AddAndBuildDatabaseItem(Int32 item)
at SEDCS.frmMain.treeViewInitList()
at SEDCS.frmMain.frmMain_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.225 (RTMGDR.030319-2200)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
SEOW-DCS-V3.3.0
Assembly Version: 3.3.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///E:/Program%20Files%20(x86)/Scorched%20Earth%20Online%20War%20System/SEOW-DCS-V3.3.0.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

As Diego said, Microsoft .Net should be updated:
C:\Windows\Microsoft.NET\Framework\v4.0.30319

Please can you help us?
Thanks
Bye
Maraz

Same problem.

System.BadImageFormatException: Could not load file or assembly 'Interop.ADODB, Version=2.8.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'Interop.ADODB, Version=2.8.0.0, Culture=neutral, PublicKeyToken=null'
at SEDCS.basErr.checkDbCampaignStatus(Int32 item, Boolean addingError)
at SEDCS.basErr.checkError(Int32 item, Int32 whatError)
at SEDCS.basErr.SearchIfThereAreErrorsAndPostMessage(Int32 item, Boolean postMessageOnForm, String& str)
at SEDCS.frmMain.AddAndBuildDatabaseItem(Int32 item)
at SEDCS.frmMain.treeViewInitList()
at SEDCS.frmMain.frmMain_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.225 (RTMGDR.030319-2200)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
SEOW-DCS-V3.3.0
Assembly Version: 3.3.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/Scorched%20Earth%20Online%20War%20System/SEOW-DCS-V3.3.0.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

Guys,

It's not enough to just say it is not working, I need to know your operating system, library revisions etc.

I develop on XP32 and it works there with .NET 4.0. Badger has got his DCS working, and so has Hawk_5. Let's start collating success and failure with software environment.

Cheers,
4Shades

Well it's all magic to me, I thought you just knew No hurry 4Shades if and when you have time I will chat with you and find out how to properly report an issue .

I'm running windows 7 home



Since Badger got his going I just keep at it but unforutnately I don't seem to make any progress.

4Shades I know your busy don't worrry about this I'm sure that it will get resolved later. I'm not going to run a campaign for a while anyway.

IV/JG7_4Shades wrote:Guys,

It's not enough to just say it is not working, I need to know your operating system, library revisions etc.

I develop on XP32 and it works there with .NET 4.0. Badger has got his DCS working,

As far as I understood, Badger got his older DCS 3.2.22 working, but not latest DCS 3.0.0 (at least, this is what I understand from his post).

Maraz

Windows 2008 R2 server SP1.

Sedcs 3.2.22 is properly working, of course, using the old NetFrWork 2.0 interop dll. This is the Badger's case.
On the contrary Sedcs 3.3.0 is not yet working by the new dll though NetFrWork 4.0 seems installed (see the link above on my previous post).

other suggestions:
http://social.msdn.microsoft.com/Forums ... 380925531/

http://blogs.msdn.com/b/junfeng/archive ... 1#comments

A local installation on XP SP2 is perfectly working.

PS
@Maraz
in the meanwhile you can install the Sedcs 3.3.0 on your local pc pointing to the server database so you will be able to inizialize and analize the campaign for testings using the database and Mission Planner built up on the server.
Also the campaign could be manually handled hosting the mission as a simple coop mission until the problem will be solved.

After some more digging I think this problem is something to do with the deployment configuration. From what I can test here the DCS works fine for XP32 but fails for Vista64. I found a workaround that involves setting the application to be built explicitly for an x86 platform, but this workaround has screwed up something else.

Still working on it ...

Cheers,
4Shades

Have we told you how much we appreciate your work 4Shades

Thanks

WH_wolfhnd wrote:Have we told you how much we appreciate your work 4Shades

Thanks

+1

Maraz

Shades,

here some more testings I hope useful.

Sedcs 3.2.22 local installation (XP SP2) linked to remote database (W2008Server SE SP1 x64)
sedb32 series successfully connected
sedb33 series successfully connected

Sedcs 3.3.0 local installation (XP SP2) linked to remote database (W2008Server SE SP1 x64)
sedb32 series unsuccessfully connected
sedb33 series unsuccessfully connected

Sedcs 3.2.22 Server installation (W2008Server SE SP1 x64) linked to local database
sedb32 series successfully connected
sedb33 series successfully connected

Sedcs 3.3.0 Server installation (W2008Server SE SP1 x64) linked to local database
No connections at all, cannot run the application.

Does anybody tested the new "MP4public-patchv4.710-v4.756A.zip"??? I tested it on a friends pc and it gives errors and the page cant be loaded! Without the patch "MP4public-v4.710.zip" is working but also gives some errors above the startpage.

I put my old mp-configuration and mp-connection in. Maybe its because of that.. so i will put only the settings into the new files and see what happens

I used the also newest sedcs, newest database on a winxp 32bit machine. sedcs 3.3 could connect to the database. I used the newest version of xampp (newest version of php, etc.)

I will test it now on my pc to look it the errors happen here also.

@ PhilHP, 102nd server is running this configuration without probs.
Cheers,
Petr

IV/JG7_4Shades wrote:Hi Gross,

Have a look at http://wiki-seow-en.swil.fr/index.php/F ... forcements for information on new factory objects. Basically you just define new types of installations in the Industrial_Installations table.

Hi 4Shades, is there a way to see in the MP how much a Factory Area is Damaged?

I can see that the amount of damage is tracked in the database but I haven't found a way to show it in MP.
Thanks
Maraz

Hi Maraz,

Don't worry, there is a way!

In the tooltip for the factory plate it shows the current productivity of the plate, e.g. 10 points per hour. If the normal production rate for that particular plate is 50 points per hour, this plate is only operating at 20% capacity which means it is 80% damaged.

SEOW will automatically calculate all repair and damage updates, and will display the production rate of each plate or partial factory mission by mission in the MP.

Cheers,
4Shades