Please help with this error: Selected collating sequence not supported by the operating system.

Discussion in 'Databases' started by LANDM, Apr 12, 2006.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. Hi,

    I am having problems with an access database. The database have rows in chinese, spanish and english.

    I always get the following error:

    Server Error in '/' Application.
    Selected collating sequence not supported by the operating system.
    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.OleDb.OleDbException: Selected collating sequence not supported by the operating system.

    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:

    [OleDbException (0x80004005): Selected collating sequence not supported by the operating system.]
    System.Data.OleDb.OleDbCommand.ExecuteCommandTextErrorHandling(Int32 hr) +41
    System.Data.OleDb.OleDbCommand.ExecuteCommandTextForSingleResult(tagDBPARAMS dbParams, Object& executeResult) +174
    System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult) +92
    System.Data.OleDb.OleDbCommand.ExecuteCommand(CommandBehavior behavior, Object& executeResult) +65
    System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method) +112
    System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior behavior) +69
    System.Data.OleDb.OleDbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) +5
    System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304
    System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77
    System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +36
    XqWebSide.docc.Left.Page_Load(Object sender, EventArgs e)
    System.Web.UI.Control.OnLoad(EventArgs e) +67
    System.Web.UI.Control.LoadRecursive() +35
    System.Web.UI.Control.LoadRecursive() +98
    System.Web.UI.Control.LoadRecursive() +98
    System.Web.UI.Page.ProcessRequestMain() +750


    Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

    I have being reading about this error message and I have seen that it could be related to language not installed in the operating system. Could it be possible to enable chinese and spanish language support on the server?. I have also tryed setting language to 'General' in MDB file.

    Thanks.
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    Is your Access database created with an English version of MS Access?

    You can only connect to an Access DB created with Engish version of Access. You can still store other character in Access DB created with English version of Access.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  3. Check your MS Access Db field properties.

    When data type used by your web app. is different from backend Access Db might cause your web app. to throw this error.

    ie.
    In Web App.

    Dim userID As String

    In Access DB.

    Field Name: userId
    Field Size: Long Integer

    When you run any of the action queries such as Insert, Update, Delete....storing userID from your web app. into userId field of the backend DB, the error will be thrown..

    I have encoutered this error....


    Hope it helps![​IMG]

    J. L.
    Technical Support/IT Admin/MIS Developer
    Maxtop Enterprises Inc.
    http://www.maxtop.ca</CODE>
     
  4. Thank you, it works ;)
    Lucas
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page