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 May 3, 2023 by Serenity Funeral Home of Southern Utah | Comments Off on Should Funeral Processions be Outlawed?
Posted under Funeral Procession, Funerals
The following is an online quote that I once read: “I’ve never understood the reasons behind the funeral procession. Anyone who’s spent any time driving has been caught by one. They’re hard to miss. A long line of cars with orange flags flying, their headlights on and their emergency flashers blinking. They run every light […]
