Skip to main content
Solved

IFS Config builder for IFS10 crashes immediately

  • August 28, 2024
  • 4 replies
  • 101 views
M
Do Gooder (Partner)
Forum|alt.badge.img+7

Hello!

 

I’m supposed to build a new delivery for an IFS10 customer, but for some reason I cannot seem to open the IFS Config Builder 10 tool at all. I’ve tried on multiple different machines, but the issue seems to persist. I also tried to download the latest version from developer.ifs.com, but get the same error.

 

Opening the IfsConfigBuilder.exe immediately crashes, and no program is opened. I can see an error in Windows event logs as follows:

 

Faulting application name: IfsConfigBuilder.exe, version: 10.0.5.3, time stamp: 0x5e8424f3
Faulting module name: KERNELBASE.dll, version: 10.0.17763.6054, time stamp: 0x63366e2a
Exception code: 0xe0434352
Fault offset: 0x00126362
Faulting process id: 0x2448
Faulting application start time: 0x01daf91486e501c1
Faulting application path: C:\Program Files (x86)\IFS\IFSConfigBuilder10\IfsConfigBuilder.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 648c955f-89c1-431a-8e0c-aac40f905726
Faulting package full name: 
Faulting package-relative application ID: 

 

Application: IfsConfigBuilder.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.WebException
   at System.Net.HttpWebRequest.EndGetResponse(System.IAsyncResult)
   at System.Threading.Tasks.TaskFactory`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].FromAsyncCoreLogic(System.IAsyncResult, System.Func`2<System.IAsyncResult,System.__Canon>, System.Action`1<System.IAsyncResult>, System.Threading.Tasks.Task`1<System.__Canon>, Boolean)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at IfsConfigBuilder.MainWindow+<GetAsyncVersionFromFileContent>d__6.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at IfsConfigBuilder.MainWindow+<>c__DisplayClass1+<<checkVersion>b__0>d__3.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(System.Threading.Tasks.Task)
   at IfsConfigBuilder.MainWindow.checkVersion(System.String, System.String)
   at IfsConfigBuilder.MainWindow..ctor(System.String)
   at IfsConfigBuilder.App.AppStartup(System.Object, System.Windows.StartupEventArgs)
   at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1_0(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at IfsConfigBuilder.App.Main()
 

 

 

Best answer by Ben Monroe

Hi Mikko,

I think the problem is that the client is sending the TLS connection in TLSv1, which is quite old and being obsoleted. The server accepts connections from TLSv1.2 or higher. Please consider opening a ticket for a fix.

Unofficially and unsupported, you may try a .NET Framework configuration for TLS setting as follows.

Create a new text file “%ProgramFiles(x86)%\IFS\IFSConfigBuilder10\IfsConfigBuilder.exe.config”.​​​​

Set contents:

<configuration>
  <runtime>
    <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false" />
  </runtime>
</configuration>

Save file and restart IfsConfigBuilder.

Best regards -- Ben

View original
Did this topic help you find an answer to your question?

4 replies

B
Superhero (Employee)
Forum|alt.badge.img+14
  • Ben Monroe
  • Superhero (Employee)
  • 156 replies
  • August 28, 2024

Hi Mikko,

The exception details indicates it is failing while checking the version.

Can you please confirm that you can access the following URL?

https://ifsdevtools.blob.core.windows.net/ifs-dev-tools-versions/ifsconfigbuilder/version.txt

Also, do you have a f1tools.properties file in the same folder that contains IfsConfigBuilder.exe?

Best regards -- Ben

M
Do Gooder (Partner)
Forum|alt.badge.img+7
  • Mikko1234
  • Author
  • Do Gooder (Partner)
  • 20 replies
  • August 28, 2024

Hi,

 

yes I can access the URL:

 

And the f1tools.properties also seems to be fine:

 

B
Superhero (Employee)
Forum|alt.badge.img+14
  • Ben Monroe
  • Superhero (Employee)
  • 156 replies
  • Answer
  • August 29, 2024

Hi Mikko,

I think the problem is that the client is sending the TLS connection in TLSv1, which is quite old and being obsoleted. The server accepts connections from TLSv1.2 or higher. Please consider opening a ticket for a fix.

Unofficially and unsupported, you may try a .NET Framework configuration for TLS setting as follows.

Create a new text file “%ProgramFiles(x86)%\IFS\IFSConfigBuilder10\IfsConfigBuilder.exe.config”.​​​​

Set contents:

<configuration>
  <runtime>
    <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false" />
  </runtime>
</configuration>

Save file and restart IfsConfigBuilder.

Best regards -- Ben

M
Do Gooder (Partner)
Forum|alt.badge.img+7
  • Mikko1234
  • Author
  • Do Gooder (Partner)
  • 20 replies
  • September 6, 2024

Hi!

 

Thank you for the workaround, that seemed to work!

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings