South Surrey Scavengers Posted September 12, 2005 Share Posted September 12, 2005 I went back to edit one of my existing cache pages and all of a sudden the html code gives an error and an unrecognizable stack trace. When trying to fix it I stripped out all the code and just entered a single <p> between two paragraphs and checked the html box and even then I can't get the listing to save without an error. Then I even took out all html code so its just plain text with the html box checked but still I get the statement below. Does anyone know what's going on? 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: String or binary data would be truncated. The statement has been terminated. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [sqlException: String or binary data would be truncated. The statement has been terminated.] System.Data.SqlClient.SqlCommand.ExecuteNonQuery() +180 Groundspeak.Web.SqlData.SqlConnectionManager.ExecuteNonQuery(String sql, Database database) +148 Groundspeak.Web.SqlData.SqlGeocacheController.Save(Int64 CacheID, String Nickname, DateTime DatePlaced, Int64 OwnerID, Int64 ApproverID, Double Latitude, Double Longitude, String ContactName, Uri URL, Double TerrainLevel, Double DifficultyLevel, Int32 CountryID, Int32 StateID, Boolean IsHtml, Int32 SiteTypeID, String ShortDescription, String LongDescription, String EncodedHints, Int32 ContainerID, Boolean IsSubscriberOnly, String BackgroundImageURL) +1420 Groundspeak.Web.CustomWpt.Geocache._Save(Int64 CacheID, String Nickname, SimpleUser Owner, Int64 ApproverID, WptBase Wpt, String ContactName, DateTime DatePlaced, Uri URL, Double TerrainLevel, Double DifficultyLevel, Int32 CountryID, Int32 StateID, Boolean IsHtml, Int32 SiteTypeID, String ShortDescription, String LongDescription, String EncodedHints, Int32 ContainerID, Boolean IsSubscriberOnly, String BackgroundImageUrl) +127 Groundspeak.Web.CustomWpt.Geocache.Save() +132 Geocaching.UI.hide_report.UpdateCacheFromForm() +1876 Geocaching.UI.hide_report.btnSubmit_Click(Object sender, EventArgs e) +3559 System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain() +1292 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032 Link to comment
+Solitarian Posted September 12, 2005 Share Posted September 12, 2005 I just suddenly started getting that error while trying to seek caches based on zip code and then using the map. I got one map, then was unable to pan do to this error. Oddly, I was also unable to go to the forums off the sidebar menu. Looks like geocaching.com crashed, but luckily, forums.Groundspeak.com is still working. Link to comment
South Surrey Scavengers Posted September 12, 2005 Author Share Posted September 12, 2005 Looks like a problem with the website alright. I just tried to click on your name in the forum post and got an error as well. Link to comment
+strikeforce1 Posted September 12, 2005 Share Posted September 12, 2005 Yupp, SYSTEM OVERLOAD, AGAIN! Give it some time, and things should clear up, and be back to normal. SF1 Link to comment
+Prime Suspect Posted September 12, 2005 Share Posted September 12, 2005 There was a database error today. That might have been the cause of it. Link to comment
Jeremy Posted September 12, 2005 Share Posted September 12, 2005 The database issues were completely unrelated to the OP. The problem there is that the short description is too large to fit there. Normally it catches the length of the field before it sends it to the database but as the site now reformats html (properly) it may add several tags to bring it over the limit. Adjust your text and pare down the information in the short description. Link to comment
South Surrey Scavengers Posted September 12, 2005 Author Share Posted September 12, 2005 Yup, the short description must have been right at the limit before changing to html and the conversion added enough characters to put it over the limit. Thanks for the info. So, how do we know what the limit is (text or html)? Link to comment
Recommended Posts