System.TypeInitializationException: The type initializer for 'SearchPathItem' threw an exception. ---> System.Data.SqlClient.SqlException: Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1339; handshake=1917; ---> System.ComponentModel.Win32Exception: The wait operation timed out
--- End of inner exception stack trace ---
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.GetNewOpenConnection()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.GetWrappedConnection()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteReader(DbCommand command)
at funeralOne.Sql.CoreSettings.<>c__DisplayClass2_0.<GetByAccountId>b__0() in C:\azbuildagent\_work\368\s\funeralOne\Sql\CoreSettings.cs:line 20
at funeralOne.Cache.GetOrCreate(String key, Nullable`1 expirationTime, Func`1 createFn) in C:\azbuildagent\_work\368\s\funeralOne\Cache.cs:line 188
at funeralOne.Cache.GetOrCreate(String key, Func`1 createFn) in C:\azbuildagent\_work\368\s\funeralOne\Cache.cs:line 168
at funeralOne.Sql.CoreSettings.GetByAccountId(Nullable`1 accountId) in C:\azbuildagent\_work\368\s\funeralOne\Sql\CoreSettings.cs:line 18
at funeralOne.Sql.CoreSettings.<>c__DisplayClass5_0.<GetValue>b__0() in C:\azbuildagent\_work\368\s\funeralOne\Sql\CoreSettings.cs:line 84
at funeralOne.Cache.GetOrCreate(String key, Nullable`1 expirationTime, Func`1 createFn) in C:\azbuildagent\_work\368\s\funeralOne\Cache.cs:line 188
at funeralOne.Cache.GetOrCreate(String key, Func`1 createFn) in C:\azbuildagent\_work\368\s\funeralOne\Cache.cs:line 168
at funeralOne.Sql.CoreSettings.GetValue(Nullable`1 accountId, String name, String defaultValue) in C:\azbuildagent\_work\368\s\funeralOne\Sql\CoreSettings.cs:line 80
at funeralOne.Sql.CoreSettings.GetValue[T](Nullable`1 accountId, String name, T defaultValue) in C:\azbuildagent\_work\368\s\funeralOne\Sql\CoreSettings.cs:line 115
at funeralOne.WMS.Storage.ResourceHandler.SearchPathItem..cctor() in C:\azbuildagent\_work\368\s\funeralOne.WMS\Storage\ResourceHandler.cs:line 1459
--- End of inner exception stack trace ---
at funeralOne.WMS.Storage.ResourceHandler.SearchPathItem.UtilityLimitedDownload(String bucket, String path, Stream saveTo) in C:\azbuildagent\_work\368\s\funeralOne.WMS\Storage\ResourceHandler.cs:line 1475
at funeralOne.WMS.Storage.ResourceHandler.SearchPathItem.LoadFileStream(DateTime& lastModifiedUtc) in C:\azbuildagent\_work\368\s\funeralOne.WMS\Storage\ResourceHandler.cs:line 1595
at funeralOne.WMS.Storage.ResourceHandler.LoadRemoteFile(ResourceLoaderData data, String& cachePath, String& basePath) in C:\azbuildagent\_work\368\s\funeralOne.WMS\Storage\ResourceHandler.cs:line 139
at funeralOne.WMS.Storage.ResourceHandler.SearchFileStream(ResourceLoaderData data, String& cachePath, String& basePath) in C:\azbuildagent\_work\368\s\funeralOne.WMS\Storage\ResourceHandler.cs:line 829
at funeralOne.WMS.Storage.ResourceHandler.SearchFileGetContents(ResourceLoaderData data) in C:\azbuildagent\_work\368\s\funeralOne.WMS\Storage\ResourceHandler.cs:line 710
at funeralOne.WMS.Storage.ResourceHandler.SearchFileGetContents(String path, IWebsite childWebsite) in C:\azbuildagent\_work\368\s\funeralOne.WMS\Storage\ResourceHandler.cs:line 704
at funeralOne.WMS.Web.Handler.DynamicHandler.ProcessWebsiteResource(HttpContext context, String path) in C:\azbuildagent\_work\368\s\funeralOne.WMS\Web\Handler\DynamicHandler.cs:line 261
at funeralOne.WMS.Web.Handler.DynamicHandler.ProcessRequest(HttpContext context) in C:\azbuildagent\_work\368\s\funeralOne.WMS\Web\Handler\DynamicHandler.cs:line 136
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
- Please try refreshing the page and trying again.
- If the problem persists, please notify the website owner.
- The administrators of this website have been notified of this error.
Powered by the funeralOne F1Connect/2.271.0.0 Platform.
In our blog, we share resources and information that families in our community can use to cope with their loss or better understand their grief. We also write about ways we have been involved in the community. Check out our latest posts below.
Posted on June 4, 2024 by Serenity Funeral Home of Southern Utah | Comments Off on What is Aftercare?
Posted under Aftercare, Cremation, Death, Funerals
The term “aftercare” is used within the funeral profession to refer to the continued support and guidance received in the days, weeks, and months following the death of a loved one. Our assistance does not immediately come to an end following the funeral or memorial service – we continue to help and guide you in […]
Posted on August 17, 2022 by Serenity Funeral Home of Southern Utah | Comments Off on The Happiest Place on Earth…To Scatter Your Loved One’s Ashes?
Posted under Cremated Remains, Cremation
Did you know that some people consider Disney Theme Parks ideal locations for scattering their loved one’s cremated remains? Exploring this anomaly is an article published in 2018 by the Wall Street Journal authored by Erich Schwartzel, “Disney World’s Big Secret: It’s a Favorite Spot to Scatter Family Ashes.” Disney amusement parks attract millions of […]
Posted on July 28, 2022 by Serenity Funeral Home of Southern Utah | Comments Off on The Greatest Misconception in Pre-planning Your Final Arrangements
Posted under Cremation, Funerals, Pre-planning
What is the greatest misconception in pre-planning your final arrangements? Many people believe that pre-planning equates to paying the funeral home in advance. This is not the case – the funeral home receives money only after death occurs. When you prepay your final expenses, your funds are held in a life insurance policy until the […]
Posted on January 6, 2022 by Serenity Funeral Home of Southern Utah | Comments Off on Pre-planning Cremation: Where to Begin?
Posted under Cremation, Death, Pre-planning
A new year is upon us, and many individuals are interested in putting their affairs in order. Pre-planning your final arrangements is an excellent way to accomplish this resolution. As you begin the cremation pre-planning process, it is important to remember that you are not just planning for yourself. You are making arrangements and decisions […]
Posted on October 6, 2021 by Serenity Funeral Home of Southern Utah | Comments Off on When Death Occurs Away From Home
Posted under Cremation, Funerals, Travel
Few things in life are more stressful than dealing with the death of a loved one. But can you imagine a loved one unexpectedly dying while away from home? Most people would be completely unprepared if a death occurred during a vacation, business trip, or family visit. What would you do? Where would you begin? […]
