When running the upgrade from our App server the upgrade pops up with two error
messages, the first message when it is attempting to enable the Full Text
Indexing. The Second error when it is trying drop the SQL v3 jobs. Has anyone
seen this or have a clue as to what is going on?
Thank you for any help you can provide.

Here is the failure from the error log...

14:35:12| Info| Enable full-text indexing in MSCRM
14:35:12| Info| Enable full-text indexing in MSCRM
14:35:12| Error| System.Exception: Action
Microsoft.Crm.Setup.Server.InstallDatabaseAction failed. --->
System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. ---> System.Data.SqlClient.SqlException: Access is
denied to "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData", or
the path is invalid.
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.DiffBuilder.ExecuteAtomicNonQu eryCommand(BuildCommand
buildCommand)
at Microsoft.Crm.Setup.DiffBuilder.EnableFullTextInde xing(String
languageId)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Objec t target, Object[]
arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean
skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.InvokeMember(String name, BindingFlags
bindingFlags, Binder binder, Object target, Object[] providedArgs,
ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at Microsoft.Crm.Setup.Database.DllMethodAction.Execu te()
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 ---, Error, RetryCancel, Option1
14:39:36| Info| InputResult: Retry
14:39:36| Info| Dropping v3 sql jobs
14:39:36| Info| Dropping v3 sql jobs
14:39:36| Info| Dropping v3 sql jobs
14:39:36| Info| Creating v3.0 metabase tables in database
14:39:36| Info| Creating v3.0 metabase tables in database
14:39:36| Info| Creating v3.0 metabase tables in database
14:39:36| 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 ---, Error, RetryCancel, Option1

A little update - the first error was caused be the FTData directory not
being recreated during the upgrade. Seomhow it gets deleted during the
upgrade and then throws an error when it can;t find it. By manually creating
the directory on the SQL server again it continues.
Then I get the dreaded - "There is already an object named 'AttributeTypes'
in the database." Replication is not enabled, so I have no idea what is going
on. There are no error messages on the SQL server and the CRM4 log only gives
this ambiguous error"
Anyone? Please?

"sealy" wrote:
[..]

Sealy,

I had this issue on a deployment where the CRM database DID NOT have
Full-text indexing on before I kicked off the upgrade. I had to turn it on
prior. The second error, was what I got after hitting "retry" - and if
memory serves, the pop-up about the object already existing was what I saw on
the screen. But my issue was not that the upgrade was removing and
recreating Full-text Indexing - it didn't exist at all for the 3.0 deployment.

If you haven't tried this - I would try restoring your 3.0 environment, then
turn on Full-text Indexing. Then try the upgrade. Maybe you've already
tried this - thought I'd throw it out there in case you haven't.

"sealy" wrote:
[..]

Thank you very much for the response. Actually it is partly due to it being
enabled :)
The FT files appear to be corrupt. KB article 910067 states that when you
restore a db with the catalog you have to detach and re-attach the db to get
the catalog in the correct way. After recreating a new catalog we got a
different error. We are working on that now.

"Ted" wrote:
[..]

Finally got a workaround. I had to manually create the FTData directory after
it was removed, but before the installer re-enables FT indexing on the MSCRM
database. I was also able to get it to work if I created a dummy catalog on
the instance. THe problem seems to be because we are using Network Service
for the CRM service accounts and the App Pool, but I don't know enough about
SPNs and security to get it to work as expected. If anyone else runs into
this problem, just re-create the FTData directory after the installer
disables full text indexing on the database. It happens when the installer is
Installing and Configuring CRM Databases.

"sealy" wrote:
[..]

Basically, we got the the same error, and resolved it by deleteing the
FT_CATindex under the MSCRM database. Upon install, the install will recreate
the require index and everything is fine.

We are still having some workflow issues in upgrading, but other than that
all other errors have been resolved. Make sure your user id has SQL
permissions as well.

Hello Sealy,

Just to mention a post where one can find all steps creating new full-
text catalog than may help others (as it helped me):
http://blog.kazmarek.com/2008/03/11/...ing-to-crm-40/

Regards,
Leo Lopes @ L3