midspace / midspace/SEToolbox

Possible Solution to application experiencing an error and had to shut down

Open
#178 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
156
Forks
62
PR merge metrics
No merged PRs in 30d

Description

Decided to post this just in case anyone else was experiencing this issue and nobody else had a solution.

So I had recently been experiencing issues where everytime I would try to launch SEToolbox, it would say "an error has been detected in the application that has caused the application to shut down." Trying other people's solutions failed to work, rebooting, uninstalling/reinstalling, repairing installation, running in administrator mode all failed to fix the issue. I finally found out how to view the application error log(I thought like some other programs the error log would be a txt file in the program's directory but actually it referred to the event viewer's log) and that's where I saw this
"System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.30.253.116:443"

It appeared that the port 443 access was being blocked. I ended up opening up eset internet security, went into the network setup, in the advanced firewall settings, and I edited the rules to allow in/out directions for SEToolbox at port 443 for both TDP/UDP protocols and now SEToolbox no longer displays the error and launches fine.

So maybe your firewall or internet security program or maybe even your router is possibly blocking or rerouting that port elsewhere.

SEToolbox Version: 1.191.20 Release 2
SE Version: 1.191.105

SEToolbox crashed

What were you doing with SEToolbox when it happened? Just launching the toolbox

Steps to Reproduce
  1. How did this issue get triggered? Launching SEToolbox
  2. Write all of the steps here.
    double click on SEToolbox or searching SEToolbox and launching the application.
SEToolbox Event Log
2019-06-30 23:48:37,162 [1] FATAL SEToolbox.Support.DiagnosticsLogging [(null)] - Unhandled Exception
Application: C:\Program Files (x86)\MidSpace\SEToolbox\SEToolbox.exe
CommandLine: "C:\Program Files (x86)\MidSpace\SEToolbox\SEToolbox.exe" 
CurrentDirectory: C:\Program Files (x86)\MidSpace\SEToolbox
SEBinPath: P:\Program Files (x86)\SteamLibrary\SteamApps\Common\SpaceEngineers\Bin64
SEBinVersion: 1.191.105
ProcessorCount: 16
OSVersion: Microsoft Windows NT 6.2.9200.0
Version: 4.0.30319.42000
Is64BitOperatingSystem: True
IntPtr.Size: 8
IsAdmin: False
CurrentUICulture: en-US
CurrentCulture: en-US
Times started total: 5
Times started since last reset: 5
Times started since game update: 5

Files:
2017-06-02T07:49:12.0000000-04:00	498,176	2014.2.17.1	HelixToolkit.Wpf.dll
2017-03-08T17:26:22.0000000-05:00	276,480	2.0.8.0	log4net.dll
2018-09-09T00:31:30.0000000-04:00	911,360	0.32.0.0	Octokit.dll
2019-06-18T17:56:48.0000000-04:00	1,327,616	01.191.20.2	SEToolbox.exe
2017-06-02T07:49:12.0000000-04:00	745		SEToolbox.exe.config
2019-06-18T17:56:42.0000000-04:00	62,976	1.0.0.0	SEToolbox.ImageLibrary.dll
2019-06-18T17:56:42.0000000-04:00	7,680	1.0.0.0	SEToolbox.ImageShaders.dll
2019-06-18T17:56:48.0000000-04:00	2,262,528		SEToolbox.pdb
2019-06-17T18:41:10.0000000-04:00	53,760	1.0.0.0	SEToolboxUpdate.exe
2013-03-09T16:25:10.0000000-05:00	39,936	2.0.20525.0	System.Windows.Interactivity.dll
2018-03-27T14:51:20.0000000-04:00	77,824	3.0.1.0	WPFLocalizeExtension.dll
2018-01-08T19:35:48.0000000-05:00	27,648	1.2.2	XAMLMarkupExtensions.dll

System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.30.253.117:443
   at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.Internal.HttpClientAdapter.<SendAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.Internal.HttpClientAdapter.<Send>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.Connection.<RunRequest>d__58.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.Connection.<Run>d__57`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.ApiConnection.<Get>d__8`1.MoveNext()
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at SEToolbox.Support.CodeRepositoryReleases.CheckForUpdates(Version currentVersion, Boolean dontIgnore) in D:\Development\GitHub\SEToolbox\Main\SEToolbox\SEToolbox\Support\CodeRepositoryReleases.cs:line 29
   at SEToolbox.App.OnStartup(Object sender, StartupEventArgs e) in D:\Development\GitHub\SEToolbox\Main\SEToolbox\SEToolbox\App.xaml.cs:line 65
   at System.Windows.Application.OnStartup(StartupEventArgs e)
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
---> (Inner Exception #0) System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.30.253.117:443
   at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.Internal.HttpClientAdapter.<SendAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.Internal.HttpClientAdapter.<Send>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.Connection.<RunRequest>d__58.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.Connection.<Run>d__57`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Octokit.ApiConnection.<Get>d__8`1.MoveNext()<---

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Support/CodeRepositoryReleases.cs at line 29 and the startup call in App.xaml.cs at line 65, using the supplied event log to trace the failed HTTPS update request. Determine how startup behaves when that request cannot connect, and verify that SEToolbox can still launch without masking other startup failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.