steven_reid Absent Member.
Absent Member.
1993 views

Errors Creating Database Schema

Hi,
I am trying to install File Reporter 3.5 using SQL Server 2017.

When i am running the File Reporter Database Configuration Wizard, I am getting the following error

Starting*database*preparation.
Identified*database*as*SQL*Server.

Checking*database*minimum*requirements.
SQL*Server*reports*version*14.0.1000.169
SQL*Server*edition*'Developer*Edition*(64-bit)'*is*valid

Creating*database*srsdb.
*-*Using*existing*database*'srsdb'.
*-*Transaction*Isolation*Level*set*to*READ_COMMITTED_SNAPSHOT
*-*Set*recovery*model*to*SIMPLE

Creating*database*service*accounts.
*-*Using*existing*system*login*'srsadmin'
****Login*type:*****SQL*User
****Login*disabled:*False
****Login*locked:***False
****Login*expired:**False
****Days*until*login*expiration:*[No*expiration]
****Login*default*database:**srsdb

*-*Updated*password*for*system*login*'srsadmin'
*-*Reset*default*database*for*system*login*'srsadmin'*to*'srsdb'
*-*Using*existing*database*user*'srsadmin'
*-*Mapped*database*user*to*associated*SQL*Server*login*'srsadmin'
*-*Set*default*schema*for*database*user*'srsadmin'*to*'srs'

Granting*privileges*to*database*service*account.
-*Added*database*user*'srsadmin'*to*the*'db_owner'*role

Setting*up*primary*database*schema.
*-*Processing*001_Initial-Schema.sqlError:**Error*processing*statement:*-- --**SRS*3.5*Initial*Functions --**SQL*Server*Schema --** --**Last*Modified:*2018-03-07,**D.*Arnold --**Copyright*(c)*2018*Condrey*Corporation.**All*rights*reserved. -- --*Preliminary*schema IF*NOT*EXISTS(SELECT***FROM*sys.schemas*WHERE*name*=*'srs') BEGIN ****--*The*schema*must*be*run*in*its*own*batch ****EXEC(*'CREATE*SCHEMA*srs'*); END .* *Exception:*Login*failed*for*user*'srsadmin'.


Database*configuration*complete.


Any Ideas?

Thanks in Advance.
0 Likes
2 Replies
steven_reid Absent Member.
Absent Member.

Re: Errors Creating Database Schema

Found out the error. and thought i would post it here for reference.

Turned out that the SQL Server install was set to only allow Windows Authentication.

As the wizard is trying to connect using "SQL Server Authentication" then you need to modify your server authentication:

Within the Microsoft SQL Server Management Studio in the object explorer:
- Right click on the server and click Properties
- Go to the Security page
- Under Server authentication choose the SQL Server and Windows Authentication mode radio button
- Click OK

Restart SQL Services
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Errors Creating Database Schema

On 8/30/2018 5:56 PM, steven reid wrote:
>
> Found out the error. and thought i would post it here for reference.
>
> Turned out that the SQL Server install was set to only allow Windows
> Authentication.
>
> As the wizard is trying to connect using "SQL Server Authentication"
> then you need to modify your server authentication:
>
> Within the Microsoft SQL Server Management Studio in the object
> explorer:
> - Right click on the server and click Properties
> - Go to the Security page
> - Under Server authentication choose the SQL Server and Windows
> Authentication mode radio button
> - Click OK
>
> Restart SQL Services
>
>

Steven,

That's correct. As specified in the File Reporter installation
documentation here
(https://www.novell.com/documentation/filereporter3/file_reporter_3_0_install/data/b18qheec.html,
Step 20) the SQL Server instance must be in mixed authentication mode.

Glad you were able to proceed!

-- NFMS Support Team
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.