TOPIC:

I recently allowed installation of Windows 10 Creators update on my development machine. It is now running Windows 10 Pro version 1703.

FlowHeater Server now fails on all tasks. The tasks run, but no records are written. All the tasks use File Monitoring. After running they all show the correct time stamp in the Last run column, and -1 in the Result column, and the task is highlighted in yellow. Also the After Execution - Move File action will fire only in the case of an error, and not in the case of success.

On my production machine, I have not yet allowed the Windows upgrade to install. It is running Windows 10 Pro version 1607. The exact same tasks run with no problems on this machine.

Has anyone else experienced this?

Hi Joe,

I know you are processing Excel files If you install the Windows Creators update windows perform a new installation and this just optain your installed applications and settings. Advanced or expert modifications are lost

I guess you just have to create the two desktop Folder again like discriped here: Flowheater Server Installation Fails

I have reviewed this thread https://flowheater.net/forum-en/server/819-flowheater-server-installation-fails

I did have to add these folders again after the update:
C:\Windows\SysWOW64\config\systemprofile\Desktop (only on 64 bit operating systems available)
and
C:\Windows\System32\config\systemprofile\Desktop
That did not fix it.


I recall that there was more to the fix than just adding the folders, but I don't recall the specifics. We spent several sessions working on it.

Hi Joe,

please try the follows.

First restart the machine and logon with the service user account and start one time MS Excel manually. Second logoff and logon with your usual user account and restart the FlowHeater Server Service.

Afterwards try to start a task. In case this also fails, please post the written log file.

The service user account is the same account as my usual account.
I have tried logging on and off and re-booting.
I thought I had posted this reply last week with the text from the error and from the log.
I will post those separately

This is the text from the error file:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: There is an error in XML document (36, 4). ---> System.Xml.XmlException: '', hexadecimal value 0x07, is an invalid character. Line 36, position 4.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, StringBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
at System.Xml.XmlTextReaderImpl.ParseCharRefInline(Int32 startPos, Int32& charCount, EntityType& entityType)
at System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars)
at System.Xml.XmlTextReaderImpl.ParseText()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlReader.ReadElementString()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderGetStatus.Read3_RunningTask(Boolean isNullable, Boolean checkType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderGetStatus.Read4_GetStatus(Boolean isNullable, Boolean checkType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderGetStatus.Read5_GetStatus()
--- End of inner exception stack trace ---
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)
at FlowHeater.Core.Server.Messages.BaseMessage.EIAQNeY0LxPsfgTIKSNT(Object , Object )
at FlowHeater.Core.Server.Messages.BaseMessage.DeSerialize(String xml)
at FlowHeater.Core.BaseWindow.xYGkykJzt5NUqpB7xgC(Object , Object )
at FlowHeater.Core.BaseWindow.SendReceiveNamedPipe(BaseMessage request)
at FlowHeater.Server.Forms.GUI.BEQyfkF5OkrObPFkUZa(Object , Object )
at FlowHeater.Server.Forms.GUI.timer1_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2098.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

---

FHServer
Assembly Version: 4.0.8.2
Win32 Version: 4.0.8.2
CodeBase: file:///C:/Program%20Files/FlowHeater%20Server%20V4/BIN/FHServer.exe

---

System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2093.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

---

FlowHeater.Core
Assembly Version: 4.0.8.2
Win32 Version: 4.0.8.2
CodeBase: file:///C:/Program%20Files/FlowHeater%20Server%20V4/BIN/FlowHeater.Core.DLL

---

System.ServiceProcess
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll

---

System.Configuration.Install
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration.Install/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.Install.dll

---

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2094.0 built by: NET47REL1LAST
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.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

---

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2098.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

---

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

---

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

---

5e2932d6-b0ff-45e4-9c95-324ee8de7eec
Assembly Version: 1.0.0.0
Win32 Version: 4.0.8.2
CodeBase: file:///C:/Program%20Files/FlowHeater%20Server%20V4/BIN/FHServer.exe

---

a63a2980-ab57-4f64-b5f7-6854d11e0284
Assembly Version: 1.0.0.0
Win32 Version: 4.0.8.2
CodeBase: file:///C:/Program%20Files/FlowHeater%20Server%20V4/BIN/FlowHeater.Core.dll

---

System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

---

Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

---

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

This is from the Server log:

2017-06-26 08:35:08.515016 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/772
2017-06-26 08:35:09.322930 [Info] (File Monitoring) : New file available: C:\A5Webroot\FreightZone\Posting\Uploads\TheMcGinnisLumberCompany.xlsx
2017-06-26 08:35:09.431005 [Info] (Worker 2) : Do Task: McGinnis Lumber
2017-06-26 08:35:09.436009 [Debug] (Worker 2) : Create TEMP path C:\Program Files\FlowHeater Server V4\Temp\FHTask_4a84a1fa-a698-4e21-839d-810d6d925341
2017-06-26 08:35:09.756727 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/1894
2017-06-26 08:35:09.767734 [Debug] (Worker 2) : Task [McGinnis Lumber] Executing step Step 1
2017-06-26 08:35:09.963363 [Debug] (Worker 2) : Set environment variables TMP/TEMP to C:\Program Files\FlowHeater Server V4\Temp\FHTask_4a84a1fa-a698-4e21-839d-810d6d925341
2017-06-26 08:35:09.981876 [Debug] (Worker 2) : Start new process : C:\Program Files\FlowHeater Server V4\Versions\x64\4.0.8.2\FHBatch.exe /ReadFileName C:\A5Webroot\FreightZone\Posting\Uploads\TheMcGinnisLumberCompany.xlsx C:\Import\FlowHeater\CustomerDefinitions\McGinnisLumber.fhd
2017-06-26 08:35:10.515730 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/2111

Hi Joe,

In the meanwhile, I´ve made some test with Windows 10 Creators Update and Excel 2016 like you try to perform. In all cases, the FlowHeater Server works like expected.

The posted XML error/exception message seems to me like the FlowHeater Definition (.fhd) file you try to execute is corrupt. Please try to open and execute this one manually with the FlowHeater Designer .

What happened if you just execute a little command script (.cmd) instead of FlowHeater Definition (.fhd). Note: Do not execute the FlowHeater Definition into the script! The script is just for testing purpose.

In case this works, the last thing you could try is to reinstall the FlowHeater Server on this machine.

I have done some testing as you suggest...

The FlowHeater Definition (.fhd) file is not corrupt. It runs flawlessly when executed manually in the FlowHeater Designer. It will insert records into the MySQL table on the write side. The same definition, when run via FlowHeater Server, produces the error "There is an error in XML document".

I made a simple .cmd file, and set up a task in FlowHeater Server to execute it with a File Monitor trigger. It runs flawlessly.

So the next step is to reinstall FlowHeater Server.

Should I uninstall FlowHeater Server completely, and then reinstall it, or should I install it without first uninstalling it?

Hi Joe,

Yes, please uninstall the FlowHeater Server first. For backup your currently configured settings or task you just have to save the FHServer.db file in the “C:\Program Files\FlowHeater Server V4\Data” folder.

Before you restore your settings please try the initial settings and create a task with your desired Excel -> MySQL file monitoring task.

I uninstalled FH Server, re-booted, then reinstalled. Still not working.
I am getting different behavior when processing an excel file. It no longer produces the "System.InvalidOperationException:"
The FH Server Log shows "Open method of Workbooks class failed"
The FH Definition can open the excel file, and the FH Server Service is runnning with the same logon.

Here is the complete text from the log:

2017-06-28 14:20:05.359161 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/617
2017-06-28 14:20:06.080982 [Info] (File Monitoring) : New file available: C:\A5Webroot\FreightZone\Posting\Uploads\TheMcGinnisLumberCompany.xlsx
2017-06-28 14:20:06.350171 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/1554
2017-06-28 14:20:06.468254 [Info] (Worker 2) : Do Task: McGinnis
2017-06-28 14:20:06.472757 [Debug] (Worker 2) : Create TEMP path C:\Program Files\FlowHeater Server V4\Temp\FHTask_7af06c22-50d2-47a5-96b2-7c6d403a1b55
2017-06-28 14:20:06.477265 [Debug] (Worker 2) : Task [McGinnis] Executing step Step One
2017-06-28 14:20:06.482764 [Debug] (Worker 2) : Set environment variables TMP/TEMP to C:\Program Files\FlowHeater Server V4\Temp\FHTask_7af06c22-50d2-47a5-96b2-7c6d403a1b55
2017-06-28 14:20:06.486266 [Debug] (Worker 2) : Start new process : C:\Program Files\FlowHeater Server V4\Versions\x64\4.0.8.2\FHBatch.exe /ReadFileName C:\A5Webroot\FreightZone\Posting\Uploads\TheMcGinnisLumberCompany.xlsx C:\Import\FlowHeater\CustomerDefinitions\McGinnisLumber.fhd
2017-06-28 14:20:07.350840 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/2432
2017-06-28 14:20:08.350504 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/1714
2017-06-28 14:20:09.361222 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/1714
2017-06-28 14:20:10.359386 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/1714
2017-06-28 14:20:11.355048 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/1714
2017-06-28 14:20:12.085036 [Debug] (ListenerNamedPipe) : DoRequestNotifyTaskStatus: TaskFinished=True, ID=7af06c22-50d2-47a5-96b2-7c6d403a1b55 Read=0, Fitter=0, Write=0
2017-06-28 14:20:12.090039 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=NotifyTaskStatus 683/703
2017-06-28 14:20:12.350720 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/2142
2017-06-28 14:20:12.442781 [Debug] (Worker 2) : Task [McGinnis], Step [Step One] standard output:
FlowHeater (R) Batch Modul (64 Bit): Version 4.0.8.2

ServerTask: 7af06c22-50d2-47a5-96b2-7c6d403a1b55
Definition: C:\Import\FlowHeater\CustomerDefinitions\McGinnisLumber.fhd

Start: 6/28/2017 2:20:07 PM
Open method of Workbooks class failed



2017-06-28 14:20:12.448284 [Error] (Worker 2) : Task [McGinnis], Step [Step One] error output:
Open method of Workbooks class failed


2017-06-28 14:20:13.350384 [Debug] (ListenerNamedPipe) : Client connected: DoRequest() RequestType=GetStatus 565/1307

Hi Joe,

I´m to be stumped. I send you a WebEx invitation to clarify this strange issue with remote hands.