Skip to Content
0
Former Member
Jul 18, 2016 at 06:58 PM

could not reach CMS, stopped critical error (FWH 20031)

1034 Views

I'm using Crystal Server/Reports 2016 SP2 on Windows Server 2014 with Standard SQL Server 2012.

Previously I've setup the server successfully using SQL login.

This go-around my goal was to use Windows authentication only.

However I believe my primary problem is that I'm getting my logins confused with my services.

This was the error received:

I read this howto: http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1327347.aspx but my "CMS DB specify option" is disabled.

The SIA service I named "SiaCrystalService2016".

Whereas I created a Windows user named "CrystalServerAgent" to access the CMS of the database.

And added that user to the SQL logins

And mapped it as the CMS database owner

Should I have instead named the user as "SiaCrystalService2016" instead of "CrystalServerAgent"?

Or do you see something else that is wrong with this setup?

Thanks,

Aaron

Attachments

pic3.png (23.4 kB)
pic5.png (14.6 kB)
pic6.png (16.2 kB)
pic4.png (25.9 kB)
pic1.png (156.3 kB)
pic2.png (143.2 kB)