The string being written to the field has exceeded it's length. Firstly it isn't critical because it is the activity table. I suspect you may have an issue with the ip addrees field as this was probably not designed for ipv6. That'll cater for the first 2 errors. The other one just ignore it. I've seen it plenty of times even on a system that is working perfectly.

It may be the crm version field is to short. 
Extract  the statement and then match them up to the values, have the table schema open and then see which value is greater then then allowable length. You can ignore dates. 

Hey Vega, thanks for the reply, I wanted to find out how exactly I can go about fixing the error in the activity table. Which field is most likely the source of the error

Hey Darren, thanks for the reply, which statement should I extract and how can i go about extracting it.

you want everything from "(insert" to "15')" run this in SQL (in a tran) as it should fail. When reformat the SQL so the values line up with the columns. Then have the schema open and then locate the likely fields dates and int's can be ignored, on the first pass. You should find one field value that is to big for the target field.

If you don't have any SQL knowledge then get help from someone that does.

Thanks for this, i found that the field in question was the acty_IPAddress field in the activity table. the error comes up every time an IPv6 address is used. I tried increasing the column size but I got this error from MSSQL

Any ideas on how I can save the changes?

Yes, in SQL management studio, go to Tools -> Options and find the following and make sure that box is ticked.

Personally whenever I install SQL or when I get onto a SQL installation, it's the first option I change. There are others I would alter but this is the most important.

Yande

If you have not already done so, please can you log this as a case with your local Sage office - this is a change that should be very easy to make in future versions of Sage CRM.

Use Alter Table to make the change.

Thanks so much, I have managed to fix the problem

Completely agree, one of the first things I do as well. (Editing SQL settings to stop it preventing saving changes)