Skip to main content

FSM6 UPD14 Installation Error

IFS internal On-Premise Installation / SQL Server DB.

Getting below error during DB installation and failed. Any idea/advise?

 

 

Is there anyone who could complete FSM6 UPD14 Fresh installation/upgrade in on-prem(SQL server)? Apparently both end up in above error, even with all the pre-requisites are there.


Hi @SanjeewaJ ,

Are you moving with a completely new installation? Or is it an upgrade?

Because such an issue is encountered if a new database is forced to be installed when there is already an existing database in place.

 

Thanks and Br,

Aaqil


@SanjeewaJ

Adding to the above,

I would suggest in checking with FSM-DB mappings and then a SQL server restart before the DB upgrade.

Br, Aaqil


Hi @Aaqil Zackariya 

I tried both.

  1. Fresh installation - Which is the one that is explained above and giving errors
  2. Upgrade on UPD7 environment - It is not throwing any errors in power shell command window. But, apparently it is not executing any script at all. App server works fine.

Just to verify, I ran the same on a BNT environment. DB upgrade end up with below

At the end of Mobile service upgrade

Get above error, probably due to the issue with DB upgrade.

At the end, when I complete the wizard and try to login to Smart Client, 

 

BTW, @Aaqil Zackariya ​​were you able to upgraded an environment to UPD 14 successfully without facing this (or an fresh installation)?

 

/Sanjeewa

 

 

 


Hi @SanjeewaJ 

Yes, I installed UPD 14 to my local machine. The issue I encountered was on the power shell command. In my case it was not a fresh installation, but an upgrade from UPD 13. There was no issue in Mobile service.

I’m afraid whether you need to create a new database for FSM, which should be your last resort. 

But before that you could try deleting the existing login and create a new one. Map the FSMDB to the new login. Then provide those details for installation.

 

 

As u said it is likely to be an issue with FSM-DB upgrade.

 

Br, Aaqil


@SanjeewaJ  Could you please just check on the PowerShell version you are using form below command.

Get-Host | Select-Object Version

Its better to use newer version like 5.1. 


Hi @SanjeewaJ ,

Please try to adding “-QueryTimeout 1000 `” line in FSM_Upgrade.ps1 script. 

{
If ($adminUser)
{
Invoke-Sqlcmd `
-QueryTimeout 1000 `
-serverInstance $($server) `
-Username $($adminUser) `
-Password $($adminPass) `
-Database $($dbName) `
-InputFile ".\FSM_570_MetadataInsert_2.sql" `
-ErrorAction stop `
-Verbose > ".\metadata_2.log" 4>&1
}
Else
{
Invoke-Sqlcmd `
-QueryTimeout 1000 `
-serverInstance $($server) `
-Database $($dbName) `
-InputFile ".\FSM_570_MetadataInsert_2.sql" `
-ErrorAction stop `
-Verbose > ".\metadata_2.log" 4>&1
}
}

 


Reply