-
Preparing External SQL Database
I have always used the below requirements from Article ID# 2638 for setting up a MS-SQL Database. Someone challenged me yesterday on #5 in the list as they want to basically give me a SQL account with DBO rights to all the DW DB's only. Is that SQL right in #5 an ongoing need or is it for the initial setup of the DB only?
Microsoft SQL (MSSQL) for DocuWare Installation
- Make sure MSSQL server is up to date with their service packs (SP), especially if you are using old version of Micorsoft SQL Server.
- Microsoft SQL Server has to be configured with a static port number for installation. Dynamic porting is not support by DocuWare during the installation. The default port for MSSQL is 1433. Also MSSQL Express Edition is not supported by DocuWare.
- To see if SQL server instance has been configured with static or dynamic port you can use the tool called "SQL Server 20xx Configuration Manager"
- Also take a look at the "System Requirements" for each version of DocuWare.
- Micorosft SQL server has to be configured to accept SQL Authentication and Windows Authentication. During DocuWare installation SQL authentication will be utilized. This is typically done in SQL Server Management Studio (for SQL 05/08/12/14/16).
- By opening “SQL Server Management Studio” login into the SQL Server and create a SQL user with:
- Securityadmin role rights
- Sysadmin role rights
- This SQL user must be able to create databases and objects with the database (tables, triggers, indexes, etc).
- This SQL user should also be mapped as securityadmin role for tempdb databases.
- If your SQL server has multiple instances running then you have to connect from DocuWare using the full instance name (E.g.: ServerName\InstanceName) during the installation.
NOTE: Once the database has been prepared, DocuWare Authentication server installation will onnect to that database and create all necessaries components required for DocuWare software. If you are installing DocuWare in a different server, then you could test the connection by creating a test ODBC connection from that DocuWare server to the Micrososft SQL Database server (as test only).
-
VBA Check Tool
The VBA Check Tool to validate that you don't have VBA scripts that will cause problems in v6.12 Workflow Engine no longer comes with the Main Software download or the latest HotFixPack. I had to pull it from a v6.11 HFP24.
What is the direct download for the tool now?
Thanks
-
You must run this as a User
You must run this as a User who has Local Admin rights on that PC. Some users are restricted from running software installs.
-
Connect to Ricoh Add-On
Can the Connect to Ricoh Add-On be used on Ricoh Copiers with the Android "Smart Op Panel Screens"?
https://www.docuware.com/sites/default/files/forums-images/Ricoh%20SOP.png
-
SQL High Available Server Set Ups Supported
I go another question about the SQL database for high availability.
Does DocuWare support SQL Clustering and/or ALWAYS ON configuration?
-
SQL Database with Encryption
Are there some specifications about what levels of encryption at the SQL database level are supported by Docuware v6.12?
TLS 1.2?
Data encryption at Rest?
TDE?
Any specific restrictions of incompatible settings?
-
The post above works great.
The post above works great. In version 6.12 there are only two items to modify in the Inex.html file. Also users will have to point there initial url to http://server/docuware with no additions and it will log in a users who has a Network ID in the DocuWare user account that matches their PC login account.
-
Cloud Users - Import to Create Available
I know I have seen this posted before but can not find it.
Is there a way to import user account creation for Cloud? I have an account that may require many users to connect.
-
Old vs New Licensing Rules
I have a customer on v6.11. There license is a 10 concurent user license that we have converted one of the concurrent licenses to 2 names licenses so the system is currently set as 9 concurrent and 2 named.
The have purchased an additional 5 named user licenses under the new license method and this requires me to upgrade their system version to 6.12 to allow them to be used.
They want to convert more of their 9 concurrent licenses to named ones as part of this whole process.
Now for my question...Is there any advantage converting these concurrent licenses to named ones before upgrading or will they retain the same 2 to 1 ratio for conversion when they are on v6.12?
-
Ok, this makes sense, add a
Ok, this makes sense, add a professional server license to the one to get two installs available. Will you tell me what quantity of servers can be installed with a base Enterprise license.