Luísa Rodrigues
8th August 2008, 17:48
I am doing a Baan 5.0c instalation in Blades system, and i get one error during Master CD baan 5.0c Instalation, in SP3 Tools SP2 appl. part.

I have already changed the tabledef file to have driver nível 2
MSQL_Level1=0

Event Type: Error
Event Source: Baan:(
Event Category: <Unknown>
Event ID: 1000
Date: 05-08-2008
Time: 17:21:08
User: SRV-DB7\baan
Computer: SRV-DB7
Description:
Env baan (H:\BAAN)
Prog dbserver_dll file \MSQL\msql_data.c # 504
Keyword TSS data
Username baan type S language 2
Process 0x5cc

dbs_errno = 205, Error 205 occurred:
TSS to Native conversion error (-3) on column 'mess' [OutLen=132 InLen=132]
Input string (hex): 0x55 0x70 0x64 0x61 0x74 0x69 0x6e 0x67 0x20 0x74 0x61 0x62 0x6c 0x65 0x73 0x9b 0x9c 0x9d 0x45 0x2e 0x2e 0x2e 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20
Flushed at \MSQL\msql_data.c : #1035.



*****

Event Type: Error
Event Source: Baan
Event Category: Bshell
Event ID: 1000
Date: 05-08-2008
Time: 15:32:13
User: SRV-DB7\baan
Computer: SRV-DB7
Description:
Env baan (H:\BAAN)
Prog bshell file bdb_fun.c # 1230
Keyword Table io error
Username baan type S language 2
Lasterror 997 (Overlapped I/O operation is in progress.)
Errno 0
bdberrno 205 (Out of range)
Message Error 205 (Out of range) on ttadv450000 in db_insert

Best regards

Luísa Rodrigues
8th August 2008, 19:08
No one have one idear what cause this erro???

Dieter
9th August 2008, 01:11
Hello Luisa,

the text of the input string is "updating tables@@@E--" (checked with ttstpisotable)

The "@@@" are three characters greater 0x7F (0x9b 0x9c 0x9d) which will most probably cause the trouble.

Suggestion: Delete the content of your $BSE/log directory

Run the process again

Check the logfiles (with ttstperrlog) if you could see more detailled information there. Most probably you will find an entry that shows you in which table and company this buggy record is located.

I hope that helps at least a bit.

Regards

Dieter

Luísa Rodrigues
11th August 2008, 12:43
Hello Dieter

Thanks for your help. I deleted $BSE/log directory but the error continues.
I know exactly in what table this error occurs, in in ttaad450 in mess field.
It is a char 132, and i think there is message with a hier size.

I have already changed in SQL structure, the table field type to char and varchar 250, but did't resolve.

Where can i Check the logfiles??
tstperrlog??? Where?? At this Baan installation moment, i don't have table definitions and data access :(

Best regards

Luísa Rodrigues
11th August 2008, 13:19
Note to this case:
I am installing Baan 5.0c thue a ILO hp Connection, so i mounted a drive CD in the Baan Server.
Do you think this can be a problem????

Luísa Rodrigues
11th August 2008, 14:08
Any one with a any idear???? :(

Luísa Rodrigues
2nd September 2008, 14:32
After install a different porting Set version, the error mantain.
Any one have any idear for this problem cause?:(

Best Regards

Andreas
3rd September 2008, 09:16
Hi Luisa,
i'm sorry to have no idea what causes this error, but i think you should get in contact with infor support for this.

Andreas

Luísa Rodrigues
4th September 2008, 14:11
Hello Andreas

thanks for your attention.

I have already reported this error to Support, but they are stiil reseraching, so i am tryisg a lot of thimgs to get a solution, you see.

Best Regards

Luísa

vinceco252
4th September 2008, 17:41
Luisa,

Unfortunately, I don't have a specific answer. I know that when I've run into situations like this, it has helped to take a step back and review the documentation carefully. Oftentimes I will find some small tasks/setup requirement that I have overlooked.

I know that's not much help, but I haven't seen this specific issue, so I don't have anything better at the moment.

Good luck!

Vince

dave_23
5th September 2008, 21:16
Your character set / collation type in SQL Server could be wrong. Or the import files could just corrupt (either on the CD, or when you xfered 'em)