|
|
Obituaries Section:
Wednesday, January 30, 2013
Harold E. Nehring
OBITUARY
WAMEGO- Harold E. Nehring, 74, of Wamego, Kansas, passed away on Jan. 29, 2013, at the Good Shepherd Hospice House in Manhattan, Kansas. He courageously lost his battle from a rare type of Leukemia.
Harold was born in 1938 on the family farmstead in rural Alma, KS and graduated from Alma High School. He entered the U.S. Army in 1955 where is also graduated from cooks and bakers school, and then was honorably discharged from the U.S. Army Reserves in 1963. Harold and his wife Ruth were married on July 4, 1958 and celebrated 54 years together.
Harold was in the food business many years, as well as being self-employed most of his life, including H. Nehring Refrigeration & HVAC; Kaw Processing Center, and Nehring Farms Meat Products (where he specialized in his Beef Jerky business). He later retired from Kansas State University in Facilities in 2002. Harold was a member of the Prairie View Community Church in Alma, Harold Johnson American Legion Post #172 in Wamego, the Masonic Lodge, Post #161 in Alma and then Post #75 in Wamego, and the Wabaunsee County Historical Society.
Harold was a man of many talents and interests, including his love of the farm, music, and playing his guitar. In the early 1960’s he was part of band called the Catalinas. Later he acquired the popular dance hall called ‘Liederkranz ‘ in Alma. He enjoyed fishing and hunting with his buddies, spending time reminiscing with family and friends. He loved countryside drives in the old stomping grounds south of Alma on Nehring Branch Road and keeping up with local history. He was an avid fan for both the K.U. Jayhawks and K-State Wildcats. His humor, quick wit and love of story-telling will be missed by many.
Survivors include his wife, Ruth (Senne) Nehring, of the home, three children, daughter, Janice Nehring (Raymore, MO), son, Ronald R. and Kelly Nehring (Wamego, KS), and daughter, Julie and Dee Whearty (Grandview, MO), three grandchildren, Zac Nehring (Wamego, KS), Chelsey Nehring (Wichita, KS) and Nathan Nehring (Wamego, KS), and four grand-dogs (Harley, Teena, Ruby and Zoey). He is also survived by his siblings, Dixie Smith and Eddie (San Antonio, TX), Ronald B. Nehring and Betty (Council Grove, KS), and Dianne Farabi (and Rich Butchko), (Dublin, OH). He was preceded in death by his father, Arnold B. Nehring (and wife Lorena) and his mother, Delma (Diel) Weidenbach (and husband Boyce).
Funeral services will be held at 11:00 a.m. Saturday, Feb. 2, 2013 at the Stewart Funeral Home of Wamego. Military burial honors and Masonic Rites will be presented at the funeral home. Mr. Nehring will lie in-state at the funeral home on Friday from 1:00 p.m. until 6:00 p.m. There is no formal visitation planned.
In lieu of flowers, memorial contributions are suggested to The Leukemia & Lymphoma Society, The Good Shepherd Hospice House, or Wamego Community Health Ministry, and may be left in care of the Stewart Funeral Home of Wamego, PO Box 48, 66547. Condolences may be left at www.stewartfuneralhomes.com. |
|
|
|
The Wamego Smoke Signal All Rights Reserved.
407 Lincoln St., Wamego, Ks. 66547 Voice:(785) 456-2602
Reproduction in whole or in part is strictly prohibited!
Published by Montgomery Communications, Inc.,
|
|
 |
|
|
Cannot open database "WamegoBanners" requested by the login. The login failed.<br>Login failed for user 'WamegoBanners'.
Server Error in '/' Application.
Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
|
Stack Trace:
[SqlException (0x80131904): Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.]
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +428
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
System.Data.SqlClient.SqlConnection.Open() +122
ASP.ABMBanner.getbanner() +2586
ASP.absolutebm_abm_aspx.page_load() +513
System.Web.Util.CalliHelper.ArglessFunctionCaller(IntPtr fp, Object o) +8
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +8681795
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
|
Version Information: Microsoft .NET Framework Version:2.0.50727.4234; ASP.NET Version:2.0.50727.4223
|
Cannot open database "WamegoBanners" requested by the login. The login failed.<br>Login failed for user 'WamegoBanners'.
Server Error in '/' Application.
Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
|
Stack Trace:
[SqlException (0x80131904): Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.]
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +428
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
System.Data.SqlClient.SqlConnection.Open() +122
ASP.ABMBanner.getbanner() +2586
ASP.absolutebm_abm_aspx.page_load() +513
System.Web.Util.CalliHelper.ArglessFunctionCaller(IntPtr fp, Object o) +8
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +8681795
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
|
Version Information: Microsoft .NET Framework Version:2.0.50727.4234; ASP.NET Version:2.0.50727.4223
|
Cannot open database "WamegoBanners" requested by the login. The login failed.<br>Login failed for user 'WamegoBanners'.
Server Error in '/' Application.
Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
|
Stack Trace:
[SqlException (0x80131904): Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.]
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +428
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
System.Data.SqlClient.SqlConnection.Open() +122
ASP.ABMBanner.getbanner() +2586
ASP.absolutebm_abm_aspx.page_load() +513
System.Web.Util.CalliHelper.ArglessFunctionCaller(IntPtr fp, Object o) +8
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +8681795
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
|
Version Information: Microsoft .NET Framework Version:2.0.50727.4234; ASP.NET Version:2.0.50727.4223
|
Cannot open database "WamegoBanners" requested by the login. The login failed.<br>Login failed for user 'WamegoBanners'.
Server Error in '/' Application.
Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
|
Stack Trace:
[SqlException (0x80131904): Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.]
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +428
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
System.Data.SqlClient.SqlConnection.Open() +122
ASP.ABMBanner.getbanner() +2586
ASP.absolutebm_abm_aspx.page_load() +513
System.Web.Util.CalliHelper.ArglessFunctionCaller(IntPtr fp, Object o) +8
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +8681795
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
|
Version Information: Microsoft .NET Framework Version:2.0.50727.4234; ASP.NET Version:2.0.50727.4223
|
Cannot open database "WamegoBanners" requested by the login. The login failed.<br>Login failed for user 'WamegoBanners'.
Server Error in '/' Application.
Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
|
Stack Trace:
[SqlException (0x80131904): Cannot open database "WamegoBanners" requested by the login. The login failed.
Login failed for user 'WamegoBanners'.]
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +428
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
System.Data.SqlClient.SqlConnection.Open() +122
ASP.ABMBanner.getbanner() +2586
ASP.absolutebm_abm_aspx.page_load() +513
System.Web.Util.CalliHelper.ArglessFunctionCaller(IntPtr fp, Object o) +8
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +8681795
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
|
Version Information: Microsoft .NET Framework Version:2.0.50727.4234; ASP.NET Version:2.0.50727.4223
|
|
