Ahhh, that screen we all love to see. The beautiful red text contrasting against the white and yellow background. Truly a testament to Microsoft's design team.
Ok, all jokes aside. We all see the .NET server error screen from time to time. Although one of the more frustrating messages is a database connection error, even more so when the database you are connecting to was working only a moment ago... What changed!? 😩
This was my experience late one Friday afternoon, it's the end of the week, I can almost taste the refreshing beer to cap off a busy week. Well... First, I need to get this feature complete and pushed for our QA team to review!
So whilst the project builds, I go and make a nice cuppa ☕ (yes, I'm British), I come back to the computer and lo and behold... The site doesn't load anymore.
I see the line "System.Data.SqlClient.SqlException", so I check the connection string is correct, check if anyone else in the team is having issues on Slack, check with our IT team to make sure the database server is up. Everything is fine!
Around 30 minutes later I realise... My VPN connection dropped whilst I was AFK. 🤦♂️
Lesson learned: If you get network error, always check your VPN if you're using one.
Top comments (0)