Enterprise Installation

[notrednamc]

The Enterprise Installation instructions say to open the Dist/Data folder, this folder does not exist, nor do the 2 files it tells me to copy to my server. Are there updated instructions?

[dfcuderek]

To resolve I had to use the databases from the 10.0 version then use the database upgrade tool to upgrade to 10.3. However, I had a lot of issues with that. Make sure you set the DB user as the owner of the database to avoid some of the issues. Good luck.

[inlguy]

I just posted the 10.3 database binaries in the 10.3 release so you can access them directly. No need to use the old ones or upgrade hope that helps.

[dfcuderek]

@inlguy see my comments on my ticket but so far the new install of 10.3 with your DB is working. Thank you.

[notrednamc]

@inlguy I downloaded the database binaries and proceeded with the documentation instructions. However, when attaching the database in SSMS I immediately get an error that states "An error occurred when attaching the database(s). Click the hyperlink in the Message column for details." No message appears in the message column of the Attach Databases pane.

[dfcuderek]

@notrednamc do you already have a CSETWeb database in SQL? If so you can detach the old one. When attaching, after you click "Add" and select the database make sure the "Attach As" field is not the same as the other database if you didnt detach it and the "Current File Path" is correct with correct filename. It may show up as \CSETWeb instead of CSETWeb10300.

If you don't have any other databases attached then I'm not sure what the issue might be. Still make sure that the "current file path" is correct with correct filename. Make sure your logged into SMSS with the sa account or a windows admin account.

Also, after you get the database attached, in the Web.config file make sure you change the "initial catalog=" to the name of the database you attach. If you keep the same DB name then it would be "initial catalog=CSETWeb10300"

[notrednamc]

@dfcuderek @inlguy I am attaching a screen shot of the error with the details showing for perspective. This is a new install so there is no previous DB to detach. The screen shot shows that I have the .mdf file in C:\inetpub\wwwroot\ directory, this is just the last place I tried it from. I also tried it from C:\ and C:\Users\Administrator.

I should also probably ask if using Windows Server 2019 and SQL Server 15.0.2000.5 would be causing any issues. The documentation says you use Server 2016 and SQL Server 13.0.4001.0.

[dfcuderek]

You may be correct about the SQL version. I am using SQL2016 myself. However, It could also be a permissions issue. The default folder location for the database in SQL has the MSSQLSERVER group with "Full Control" permissions set. Either place the DB's in the default database folder that SQL 2019 uses (you'll see the Master DB there) or add the MSSQLSERVER group with full control to a folder you choose but I wouldn't use the wwwroot folder.

To add the MSSSQLSERVER group follow this MS article https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-file-system-permissions-for-database-engine-access?view=sql-server-ver15

I hope this helps.

[notrednamc]

@dfcuderek
I added the DB files to the default database folder and was able to connect successfully. Proceeding through the rest of the Enterprise Install instructions, I get to modifying the web.config file. I modified it to how I understood the instructions but get an error when trying to browse to the web page (below). Could someone please verify I have modified the connection strings section properly:

Web Config:

Web Page Error:

And after rebooting the error says it cant open the db

[dfcuderek]

If you left the database named CSETWeb10300 when you attached it in SSMS then your connection strings should be:

;Initial Catalog=CSETWeb10300

Replace your CSETWeb in all three connection lines. You might want to restart the website in IIS. Let me know if that works.

[dfcuderek]

@notrednamc have your issues been resolved? Let me know if the above solution worked. If your up and running you should close this issue.

[notrednamc]

@dfcuderek I changed the connection string to show CSETWeb10300 I then restarted the server. Then the error was that the DB user's password had to be changed. Now I'm getting a different SQLException. It looks like it is looking for s src directory on the C:\ drive. Additionally the CSETWebAPI directory it references does not exist in the Enterprise Binaries zip.

[dfcuderek]

Hmmm... Lets start by trying to access the webpage from another PC on your network:

> http://<Network Name Or IP of CSET Server>

Make sure the firewall on the server (the computer that CSET is installed) has port 80 open inbound if you stuck with the default port.

You can find the IP by opening a command prompt and typing IPCONFIG and Enter. I believe you will see your CSET logon from another computer. Sometimes, in my experience browsing the webpage from the computer serving the web pages (the CSET webserver) act differently than browsing from another computer on the network.

The reason you had to change to 127.0.0.1 instead of using "localhost" in web.config is due to the Windows "Hosts" file not being set. Just Google that if you interested but the way you have it is just fine.

Let me know the outcome.

[dfcuderek]

You may also just need to use http://localhost/home/login from the local CSET server but if from another computer on the network, you may need to use http://servername/home/login

[wiicode]

Going mad trying to get 10.3 on IIS running. The database stuff was seemingly fine, but the webapp is just not even wanting to play. I am getting basic 404. Completely fresh Windows 2019 server with IIS/ASP etc. I did notice the instructions around app pools, service accounts, and general runtime go a bit fuzzy in the instruction docs.

Not Found
HTTP Error 404. The requested resource is not found.

[dfcuderek]

@wiicode are you browsing to the CSET site from a different computer or trying to access the site from the same server your running IIS?

[wiicode]

@dfcuderek , all on the same machine and testing internally/locally. I tried accessing via hostname and via localhost.

AWS EC2 instance: Windows 2019 Base
IIS installed as perscribed with .NET overrides
Removed default wwwroot and dumped the latest bundle, v10.3.
used SQL 2019 with latest SSME
Firewall presently off.

First issue was SQL setup is not quite the same for the DB schema. I simply made a user called "csetuser" and made it a db_owner for now. My assumption is that this will be fine to get things running and then I can work the documentation difference.

Web.config setup was a bit frustrating because it's set to SSPI and the documentation is a bit rough around this area. Replaced with user info for "csetuser".

I did not change service accounts on IIS or SQL, I also did not change app pools. To me, it's like IIS has no idea what it should be serving on that site.

[wiicode]

@dfcuderek maybe I just had a slight bit of progress. I reset the hostname field in IIS and got a real error. Now, at least, it's loading the app... even though it's failing with 500. I assume that's due to auth.

Detailed Error Information:
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error
Config File \?\C:\inetpub\wwwroot\web.config

[dfcuderek]

@dfcuderek maybe I just had a slight bit of progress. I reset the hostname field in IIS and got a real error. Now, at least, it's loading the app... even though it's failing with 500. I assume that's due to auth.

Detailed Error Information: Module IIS Web Core Notification Unknown Handler Not yet determined Error Code 0x8007000d Config Error Config File ?\C:\inetpub\wwwroot\web.config

I think so. Try changing the web.config auth string to the SQL sa account and password just to see if that gets the page to open. If it doesn't then you'll know its not an auth issue.

[dfcuderek]

@wiicode I have had issues loading this site from within the server itself. I have always had to use another computer accessing through the port I set up. In my case http://myservername:1433/index.html. In your case since your on AWS I'm not sure how can do that unless you have a domain setup

[wiicode]

@dfcuderek I tried messing with web.config -- just to break it and see what happens, it seems to just throw the same error. Meanwhile, your string has the Web on port 1433, that's in use by SQL on my end. Anyways, I can easily load from another system, I have IIS public facing, but it does the same thing sort of... it's a less clear version of the error "Server Error 500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed."

The docs around editing Web.config are not jiving with me, my edit was as follows:

<add name="CSET_DB" connectionString="data source=localhost;initial catalog=CSETWeb;persist security info=True;user id=csetuser;password=passwordstring;MultipleActiveResultSets=True" /> and while csetuser is not a full server admin it is a db_owner. I can elevate the permissions to see if it's DB, I don't think it is.

I also tried 10.2 version of the config file, same thing.

`HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

Detailed Error Information:
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error
Config File \?\C:\inetpub\wwwroot\web.config
Requested URL http://localhost:80/
Physical Path
Logon Method Not yet determined
Logon User Not yet determined

Config Source:
-1:
0:

More Information:
This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
View more information »`

[dfcuderek]

@wiicode I'm not sure if this is the issue but make sure that the SQL Database name exactly matches the catalog="Database Name". When I did a fresh install and used the supplied database binaries the database name is CSETWeb10300 instead of CSETWeb.

Also, just double check the Web.config syntax itself and make sure there isn't semicolon missing or something. Stupid I know but that error sounds familiar.

[wiicode]

Thanks @dfcuderek , I started off with a renamed file and later saw supporting notes it was a good move. It's not it. I'll go through the config file syntax today. It's one of those things that I fully expected the instructions to get me to a running state, and they fall short.

[wiicode]

I finally had time to come back to this and my error was due to failing to install URL Rewrite which is mentioned in README but it's easy to miss; the link in readme is not valid either but I got it from https://www.iis.net/downloads/microsoft/url-rewrite.

This let me load CSET but - I did not realize this - you must then setup an account to which an email password is sent. Well, while the practices here are sound - including salted pass in DB - this just adds a whole other hurdle. I need to use AWS SES and so far I've had no luck getting a message through. My SES setup works, I think the app is either not liking the format of the keys, or just not handling SSL/TLS the way it needs to be handled.

[dfcuderek]

@wiicode I have not tried this but an "add user" app can be found at https://github.com/cisagov/cset/releases/download/9.2.2enterprise/AddUser.zip. Give that shot, otherwise I'm sure you'll eventually get the email working. It's just getting the right combination of port, credentials, encryption etc.

[fn00b]

@dfcuderek I changed the connection string to show CSETWeb10300 I then restarted the server. Then the error was that the DB user's password had to be changed. Now I'm getting a different SQLException. It looks like it is looking for s src directory on the C:\ drive. Additionally the CSETWebAPI directory it references does not exist in the Enterprise Binaries zip.

I had the same error 'cannot find the object "dbo.MATURITY_MODELS"' when I initially loaded CSET.
To resolve it I granted the cset db user Membership to the db_owner role.
I reloaded the page and it took me to the login page.
I removed the db_owner access after that initial launch, and the issue didn't return.