Corwall…

Well not really the whole summary, but hey just some pics… Well in fact only these mmm 4 pics… Will write a full report once I’ve slept… Oh and more pictures as soon as myspace decide to let me upload anymore… Wow look I even posted “Devon” not “Cornwall” am such a dumbass…

Oh can I just say this computer sucks…

Dzien’ dobry Polish people

Well this is strange, I’ve just been looking at the stats for this very website, and I kinda guessed that quite a few people would be from the UK, so amazingly 76% of the share is UK visitors… However, I kinda thought that US might be the second, but hold on, nope Poland by 6% – 13% of the visitors share… This is so geeky I know but waiting for CRM 3.0 to configure on the Server and thought I would have a look at the stats… So anyhow, thats it, just wondering thats all!!!

Oh yes CRM configuration am going to put this here as well if you are upgrading from 1.2 to 3.0 and get the following error:
“The foreign key constraints in the CRM database are not consistent with CRM 1.2 foreign key constraints.”

Do the following:
1, Look at the CRMV3setup.log found in “C:Documents and SettingsApplication DataMicrosoftMSCRMLogs”
2, Example of the error logging is:
23:14:25| Info| The following foreign key constraint(s) are not consistent
with Microsoft CRM 1.2 foreign key constraints:
23:14:25| Error| remark: deleted foreign key
23:14:25| Error| tablename: leadaddressbase
23:14:25| Error| columnname: parentid
23:14:25| Error| referencedtablename: leadbase
23:14:25| Error| referencedcolumnname: leadid
23:14:25| Error| foreignkeyname: lead_addresses
3, Now I had a different error, so I reinstalled CRM 1.2 on a test machine and then checked the databases like this. Through the GUI, it is usually in the tablename: that the problem is.
4, Alternatively you can run/modify this (I didn’t have much joy doing this such is why I suggest reinstalling 1.2 on a different machine.
4, a, First drop the constraint on the table.
4, b, Then:

ALTER TABLE [dbo].[LeadAddressBase] ADD
CONSTRAINT [PK_LeadAddressBase] PRIMARY KEY NONCLUSTERED
(
[LeadAddressId]
) ON [PRIMARY]
GO

ALTER TABLE [dbo].[LeadAddressBase] ADD
CONSTRAINT [lead_addresses] FOREIGN KEY
(
[ParentId]
) REFERENCES [dbo].[LeadBase] (
[LeadId]
) NOT FOR REPLICATION
GO