- yet another 3.0 to 4.0 upgrade post
- Posted by john dallaire on April 23rd, 2008
I have been carefull to read through them before asking for help on this.
In a test environment installed SQL 2K5 (clean) installed CRM 3.0 clean,
Rollup 2, imported customizations from production install, restored from bak
Meta and MSCRM db's. 3.0 works fine:
Upgrade fails: [two errors at InstallDatabaseAction]
Cannot alter or drop coulmn 'KeyWords' because it is enabled for Full-Text
Search.
[Retry gets past this]
There is already an object named 'AttributrTypes' in the dataabase.
[Retry does nothing]
Have tried the VERY helpfull posts and nothing seems to work so far.
- Posted by Fortis on April 24th, 2008
John - I haven't seen that error before. Can you provide some more detailed
information on it such as what the error logs show?
Thanks!
--
Fortis
www.webfortis.com
"john dallaire" wrote:
- Posted by john dallaire on April 24th, 2008
Thanks!
Here's the snippet from the log file:
Error| System.Exception: Action
Microsoft.Crm.Setup.Server.InstallDatabaseAction failed. --->
System.Data.SqlClient.SqlException: There is already an object named
'AttributeTypes' in the database.
at System.Data.SqlClient.SqlConnection.OnError(SqlExc eption exception,
Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject
stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQuer yTds(String
methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNo nQuery(DbAsyncResult
result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.Crm.Setup.Database.DatabaseUtility.Execu teSql(InstallDatabase
database, String sql, Int32 timeout)
at Microsoft.Crm.Setup.Database.SqlScriptAction.Execu te(DatabaseUtility
dbUtility)
at
Microsoft.Crm.Setup.Database.DatabaseInstaller.Exe cuteReleases(ReleaseCollection releases, Int32 currentProgress)
at Microsoft.Crm.Setup.Database.DatabaseInstaller.ins tallInternal()
at Microsoft.Crm.Setup.Database.DatabaseInstaller.Ins tall(Int32
languageCode, String configurationFilePath, Boolean upgradeDatabase)
at Microsoft.Crm.Setup.Server.InstallDatabaseAction.D o(IDictionary
parameters)
at Microsoft.Crm.Setup.Common.Action.ExecuteAction(Ac tion action,
IDictionary parameters, Boolean undo)
--- End of inner exception stack trace ---
"Fortis" wrote:
- Posted by Fortis on April 24th, 2008
Thanks John - You might want to check this post here for a possible
resolution:
http://blog.kazmarek.com/2008/03/11/...rm-40-upgrade/
--
Fortis
www.webfortis.com
"john dallaire" wrote:
- Posted by john dallaire on April 29th, 2008
Well I had hope, but no luck. I've tried it three ways now, still the same
even with the full text disabled I get the same error!
===================================
History(for those reading along)
-> production server
SQL 2K (all sp's applied) server 1
CRM 3.0 (roll up 2) server 2
minimal customizations running approx. 2 years
-> Test server (single server)
SQL 2K5 (sp2) clean install with ReportServices
Install CRM 3.0 (clean) apply SP2
Import customizations, restore back ups of production DB's
Test -> works fine
Upgrade to 4.0 continues to fail :-(
==================================
"Fortis" wrote:
- Posted by john dallaire on May 9th, 2008
Still no luck, same 'table exists' error... anyone?
Started over:
created new VM with clean SQL 2K5 install, SP2 and Report services.
imported MSCRM and Metabase databases
created new VM with CRM Redployment tool, completed fine
Installed clean CRM 3.0 applied rollup imported customizations
tests fine.
Upgrade showed hope as no diagnostic warnings showed up
Failed again at the index error and the AttributeTypes table already exists.
"john dallaire" wrote:
- Posted by sketchy on May 15th, 2008
John, were you ever able to work through this issue during your test
deployment phase? The reason I'm curious (beside wondering if you got it
fixed) is that I'm trying to figure out a good way to build up a test
environment to test out an upgrade. So I noticed your procedures, and
wondered if you'd recommend it to others.
--
Sketchy
"john dallaire" wrote:
- Posted by john dallaire on May 15th, 2008
Sketchy,
No luck yet, I have put it on the back-burner for now while I deal with some
other issues. My next attempt I will follow these instructions:
http://blogs.msdn.com/crm/archive/20...o-crm-4-0.aspx
and hope all goes well. I'll try and document the results and steps taken,
please do the same if you get there before me.
~john
"sketchy" wrote:
- Posted by sketchy on May 15th, 2008
Of course. Will do.
Good luck.
--
Sketchy
"john dallaire" wrote: