If I used UNICODE_FSS I seam to be unable to use primary keys that
consist of more than one column and are longer than 60 characters
(sometimes it lets me go to 100, other times to 79 as well,
apparantly randomly). According to the release notes the length
shouldnt be a problem:

The new limits for indexes are:

Page Size Single column Double Column
------------------------------------------------
1 k 60 48
2 k 124 99
4 k 252 203
8 k 508 406
16 k 1020 816

I have tested on a 16k page size database so I wouldnt expect a 150
wide varchar to give an error, its max length would be 150x3(max
unicode size) which is significantly lower than the limits mentioned
in the 1.0.3 release notes.

The same indexes work perfectly on a WIN1252 char set database with
the same blocksize.

Any ideas?