We have installed BaanIV c4 on Windows 2003 Enterprise edition as OS with backend MSSQL 2005. Installation went on successfully. But while running Baan standard sessions having Date field it gives error as -
'Error 205:Read row error'. How to solve this problem?

But while inserting data through GTM(ttaad4100) it dosent give any error.

There are some posts on this error (search for: error 205) that means "Read row error 205 on <table name> / Error 205 (Out of range) on select."

Look at your server event logs for more details to help determine the nature of the error. Since you mentioned that you have just installed Baan, the most probable cause is a mismatch in a domain/table definition somewhere.

We have checked for any mismatch between table/domain definition, but havent found any. We are getting the 'Error 205:Read row error ' for all the sessions in which date field is part of the index.

In the event viewer we are getting 3 error messages -
1. Fill column fdat table dbo.thratn907145 data error.

2. dbs_errno = 205, Error 205 occurred:
bshell date -2147483648 (-2147483648 days) is not supported. The valid supported range of dates are from 02/01/1753 (639907 days) to 31/12/9999 (3652059 days) [dd/mm/yyyy].
DBMS Input: Data out of range for R_GTEQ on dbo.thratn907145.
Flushed at \MSQL\msql_row.c : #244.

3. Error 205 (Out of range) on SELECT

Urgent help required

We are having BaanIV c4 with porting set 6.1c.07.13 on Operating system Windows2003 Entrp. Edn. R2 SP2 and database as MSSQL 2005 SP2

Hi

it means that you have wrong date fields in your table. Baan support until 31.12.9999 but msql not. As far as I know it only goes unteil 2079
So every table where are dates inserted, the import crashed. You have no other possiblity as to correct the data in your "old System" ex and import then again. It normaly happened when you are comming from Informix and switching to MSSQL, because Informix is not checking the correct date. Check the last imported row via ttaad4500 and search for it in you old system. Then go further until you find the wrong date. When the table is to big try it with a querry to find the wrong dates inserted.

Regards


Markus