Skip to main content
Question

FSM 6 Update 14 Installation Error

  • January 19, 2022
  • 6 replies
  • 154 views

Forum|alt.badge.img+8

IFS internal  Installation / SQL Server DB.

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

6 replies

SanjeewaJ
Superhero (Employee)
Forum|alt.badge.img+12
  • Superhero (Employee)
  • 89 replies
  • January 19, 2022

Did you check pre-requisites in your app/DB servers aligning the installation guide?


Forum|alt.badge.img+8
  • Author
  • Sidekick (Partner)
  • 36 replies
  • January 20, 2022

Hi Sanjeewa,

 

Thanks for the response!!

 

Yes all the pre-requisites in the app/DB servers aligning the installation guide is done.

 

Please find the list below:

  1. Power shell version - 5.1.17763.226B
  2. .Net frame work version 4.8
  3. .Net core 3.1.12
  4. Microsoft SQL Server 2017 (RTM-CU22) (KB4577467) - 14.0.3356.20 (X64
  5. Google chrome version 97.0.4692.71

Let me know if I missed out some.

 

Regards

Abhishek


Forum|alt.badge.img+9

Did you check the installStatus.log and/or the FSM6_CreateViews.log.  These logs are created as the New Install or Upgrade scripts are being run and can be found in the relevant DatabaseData folder where the FSMInstaller is run.

@ABTIWARY 

@SanjeewaJ 


ISI-RWL
Do Gooder (Partner)
Forum|alt.badge.img+1
  • Do Gooder (Partner)
  • 1 reply
  • March 14, 2022

Can someone sharing with me, the installation guide for FSM 6. We just got the demo from version from IFS. but missing the installation guide.


Forum|alt.badge.img+9

@ISI-RWL Please find attached the New Install Installation Guides for both On Premise and Azure deployments of current release of FSM6 Update 16.

All of the system documentation should be present in the Documentation folder that is included in the release package.

Is this request related to the original post here?


Ruchira Jayasinghe
Hero (Employee)
Forum|alt.badge.img+7

Dear ABTIWARY,

 

This issue can be arisen because of few reasons.

  1. You could be using an old PowerShell version.
  2. There are situations where even though you upgraded the PowerShell version, you might need to perform a Server reboot in order to get things applied successfully.
  3. The “PowerShellGet” module is not available / updated.
  4. The user you are using to execute this does not have Administrator rights.
  5. The operation is being blocked by the Windows Security. (If the Controlled Access is being enabled.)

 

Thanks and Regards

Ruchira


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings