When I attempt to view a posting in the forums I get the following error. Any idea how to correct this?

Error

--------------------------------------------------------------------------------
An unexpected error has occurred on this page.The system administrators have been notified.

The error occurred in:
http://stephen/ThePhileVB/WebModules...spx?TopicId=50

Error Message:
Code page translations are not supported for the text data type. From: 1252 To: 850.

Error Stack:
System.Data.SqlClient.SqlException: Code page translations are not supported for the text data type. From: 1252 To: 850.
   at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(Com mandBehavior behavior)
   at System.Data.SqlClient.SqlCommand.System.Data.IDbCo mmand.ExecuteReader(CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.FillFromCommand(O bject data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
   at Wrox.WebModules.Data.DbObject.RunProcedure(String storedProcName, IDataParameter[] parameters, String tableName) in C:\wrox\ThePhileVB\WebModules\Core\DBObject.vb:lin e 103
   at Wrox.WebModules.Forums.Data.Replies.GetReplies(Int 32 topicId, Int32 pageNumber, Int32 pageSize) in C:\wrox\ThePhileVB\WebModules\Forums\Forums.Data\R eplies.vb:line 87
   at Wrox.WebModules.Forums.Business.Topic.GetReplies(I nt32 pageNumber) in C:\wrox\ThePhileVB\WebModules\Forums\Forums.Busine ss\Topic.vb:line 150
   at Wrox.WebModules.Forums.Web.Topic.BindGrid() in C:\wrox\ThePhileVB\WebModules\Forums\Topic.aspx.vb :line 287
   at Wrox.WebModules.Forums.Web.Topic.Page_Load(Object sender, EventArgs e) in C:\wrox\ThePhileVB\WebModules\Forums\Topic.aspx.vb :line 144
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain()

I think 850 was used by MSDOS, if I'm not mistaken. And 1252 is the Windows code page. I am guessing you may have editted something from DOS, or maybe linux?

You can probably change the codepage by loading that page in notepad and saving it again.

On second thought, it looks like that is coming from your database. Maybe you entered a news item using a different browser than IE?

Or maybe your SQL Server has been set up in a non-standard way. It can be set for various cultures. Are you using SQL Server 2000 with a default install?

Eric

Eric

The only thing I have done is convert the project to VS2003. My SQL is a default install.

Which version of SQL Server are you using? Did you restore the database backup that came with the code download to make the DB, or did you run the SQL Script?

I'm using SQL Server 2000 and I restored the database. I wasn't aware that a script was available to create the database.

The script is obsolete - you don't want to use that. I just wanted to make sure you didn't use it.

You seem to have a setup problem with that database. Maybe you've got the collation property of the database set wrong (check with Enterprise Manager), or else the ASP.NET server has a different setting from the SQL Server.

Here's a general reference on the subject:
http://msdn.microsoft.com/library/de...taencoding.asp

This shows the possible values for Collation:
http://msdn.microsoft.com/library/de...ca-co_5ell.asp

This is what Microsoft will tell you if you call them:
http://support.microsoft.com/default...b;en-us;317956

The last line of the above article:
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

If you're not using SP3, you need to stop everything and upgrade to it right now. The SQL Slammer worm is a big threat to anyone not on SP3.

Check which service pack you're on:
http://vyaskn.tripod.com/sqlsps.htm

Eric

I had exactly the same error message on a new SQL installation. Service Pack 3 fixed it.

I'm ashamed of my self. I only had SP1 applied to this particular SQL server. I applied SP3 and now everything works. Thanks for all your input and help.