Posts Tagged ‘imanage’

  1. Make sure you have a Send Connector in O365 so that I route all emails from your subdomain e.g. imanage.domain.com back to the Public IP where your Communication Server is , use the Router to NAT port 25 from this IP to the communication server and make sure SMTP is allowed through the local firewall

  2. Update the ‘Email Domain’ on the ‘WorkSite Server’ properties to ‘imanage.domain.com’ stop and start the ‘WorkSite Server’ service.

  3. Then update the ‘Domain’ in the communication server ‘Exchange Online’ properties to ‘imanage.domain.com’ stop and start the ‘Exchange Online’ service.

  4. The above will allow internal recipients to Send and File , if  wanting external recipients to be able to file emails to this server, make sure you create an MX Record for imanage.domain.com externally to route to your communications server ( preferably via your Spam Filter) 

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

 

Azure Single Sign-On 

Identifier (Entity ID): https://imanage.domain.com

Reply URL (Assertion Consumer Service URL): https://imanage.domain.com/api/v1/session/saml-login 

Download Certificate file (.cer) and store on iManage server e.g. C:\SSL\

HIVE: HKLM\SOFTWARE\Interwoven\WorkSite\imDmsSvc 

 

SAML Attribute: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name 

SAML Endpoint: https://myapps.microsoft.com/signin/iManage%20SAML/xxxxxxx-xxxxxx-xxxx

SAML Key File: C:\SSL\iManageSAML.cer 

SAML Logout Endpoint: https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0 

SAML Web RP: https://imanage.domain.com

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently installing iManage Desksite , and upon loading the Applicaiton a .net error displayed with 

“WinDatapicker”

Reinstalling the App didn’t help , in the end , I had to change the data format of windows to dd/mm/yyyy for it to work!

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

The Web uses port 443 ( SSL ) TCP

The client uses port 1090 TCP

The client Auth used 1091 TCP

These all need to be open on the router for iManage URL connection to work externally. Also the below registry items need to be set for it to force the client to use a dedicated port instead or the normal client default

 

64bit

[HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven\Worksite\8.0\Common\Options]

"Use Hosted DM"="Y"

"Hosted DM ServicePort"=dword:00000442 ( Decimal 1090 )

"Enable Hosted DM SSL"="Y"


32bit

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Interwoven\Worksite\8.0\Common\Options]

"Use Hosted DM"="Y"

"Hosted DM ServicePort"=dword:00000442

"Enable Hosted DM SSL"="Y"
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
  1. Login to iManage / Worksite Communication Server 
  2. Go to : C:\inetpub\mailroot\Badmail to see the bad mail
  3. Open up one of the emails with wordpad / notepad
  4. Get the Folder ID ( FID ) of where the email is being filed
  5. Get the username of the operator trying to file the email (Control + F “ref” can help alot)

Subject: RE: xxxxxxxxxxxxx (Our Ref:  xxxxxx)[xxx-xxx.FID102361]
 
If the IRN is not visible in the subject, look for the folder ID

“{F102361}.xxx@dms.xxxx.com”

From this example, the folder ID is 650594.


Put that folder id into this SQL query and run it against the iManage SQL database:


Replace the XXXXXXX with the folder ID


select * from [%imanageDBName%].[MHGROUP].[PROJECT_NVPS] where PRJ_ID=’XXXXXXXX’
 
Look for the value of iMan_26. this is the IRN:

You may also use:
select * from [%imanageDBName%].[MHGROUP].[PROJECTS] where PRJ_ID=’XXXXXXXXX’

The IRN can be found under the PRJ_DESCRIPT column:
 
Once you have IRN,

In Outlook search for the workspace that is found in the reference number.
if reference number does not exsist search for a document and use the FID number to find workspace number.
open the IRN Workspace in Filesite/Outlook
expand the IRN so you can see the “File” Folder
right click on the “File” folder , click properties
click profile tab
select the operator Click “Add/Edit” button
The operator might have a Red Circle on it
this means the User is disabled – Enable the user or change to the live user.
Change to the live user is prefered
Click yes to the prompt (don’t need to tick any boxes) let it update, once complete click “close”
 
Now cut + paste the email from C:\inetpub\mailroot\Badmail to C:\inetpub\mailroot\Drop , make sure it does not go back into C:\inetpub\mailroot\Badmail.
 
If we see many emails (over 3) in the badmail folder the comms server may have lost contact with the DB server.
Start the worksite service manager from deskop (imanage user)

Check that the service account isn’t locked out 
Move all badmails to the drop folder and see what get’s bounced to badmail and work from there.
 
If doing alot of these, you may want to edit Communications Server port so it doesn’t bombard users with emails
 
Check User filing with email Enabled in the Database?
User filing has write access to database ( Archive01 only read only ) ?
User filing has the same Email Address she’s sending from then the Same in AD as iManage ?
Try enabling all users and refilling all
Check the Workspace Folder double check the author / operator is installed and change to enabled user
 


VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

There is a logon script that runs the following (Replace the server with whatever your imanage server is)

“C:\Program Files (x86)\Interwoven\WorkSite\addiman.exe” %IMANAGESERVER%

The details can also be added via Registry in the Group Policy : 

Key : HKCU\Software\Interwoven\WorkSite\8.0\Common\Login\RegisteredServers\%IMANAGESERVER%\

Value : Autologin
Type : REG_SZ
Value Data : Y

Value : DATABASES
Type : REG_MULTI_SZ
Value Data : %DATABASE%

Value : Local
Type : REG_SZ
Value Data : N

Value : Password
Type : REG_SZ
Value Data : 

Value : ServerName
Type : REG_SZ
Value Data : %SERVERNAME%

Value : TrustedLogin
Type : REG_SZ
Value Data : Y

Value : UserID
Type : REG_SZ
Value Data : 

 

 

VN:F [1.9.22_1171]
Rating: 8.0/10 (1 vote cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

You can make a change to the WorkSpace description (add a full stop to the description or other characters), save it, and then reverse the change, and save it, it to force a WorkSpace to be re-indexed.

This will update the time stamp on the WorkSpace and the Indexer should pick it up to be indexed.

WorkSite Connector service is only looking for the EDITWHEN or EDITPROFILEWHEN column in the MHGROUP.DOCMASTER table

https://support.imanage.com/forums/showthread.php?t=1660&highlight=workspace

 

If changing this does not get this Workspace in the indexer it seems your connector might be broken , make sure you update to the latest version ( connector.jar )

 

 

If you have a batch of workspaces you can also do this through SQL:

To check if you are running UTC go to the below registry path on your iManage Servers
HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven\WorkSite\imDmsSvc
UTC In Use = N
Or:
UTC In Use = Y

If this key does not exist 

Run this query in SQL

SELECT 'GETDATE() ', GETDATE(); 
SELECT 'GETUTCDATE() ', GETUTCDATE();

Check both the times , and update a workspace name ( by adding a full stop at the end and deleting ) and then use a select query to see which time is closer to see if it’s using UTC or not

SELECT *FROM MHGROUP.DOCMASTER DWSJOIN MHGROUP.PROJECTS PWS ON DWS.DOCNUM = PWS.DOCNUMWHERE PWS.PRJ_NAME LIKE '%name of workspace%'


Check the PRJ_NAME matches your WorkSpace Description.

If you are UTC In Use = N, ( not ) use the below.

To update the WorkSpace for re-indexing:

UPDATE MHGROUP.DOCMASTERSET EDITPROFILEWHEN = GETDATE()FROM MHGROUP.DOCMASTER DWSJOIN MHGROUP.PROJECTS PWS ON DWS.DOCNUM = PWS.DOCNUMWHERE PWS.PRJ_NAME LIKE '%name of workspace%'

If you are UTC In Use = Y, ( Yes ) use the below.

To update the WorkSpace for re-indexing:


UPDATE MHGROUP.DOCMASTERSET EDITPROFILEWHEN = GETUTCDATE()FROM MHGROUP.DOCMASTER DWSJOIN MHGROUP.PROJECTS PWS ON DWS.DOCNUM = PWS.DOCNUMWHERE PWS.PRJ_NAME LIKE '%name of workspace%'

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

As there is no notification with the iManage Email Filing Server when folder status turns from Succeeded to reset the folder , we use the following SQL Statement to notify us via email when there are problems

 

$PSEmailServer = "smptserver"
 
##SQL Query Function no SQL installs needed all powershell baby
function Invoke-SQL ($SQLServer, $SqlQuery) {
#Uncomment below to double check the statement
#Write-Host $SqlQuery
$SqlConnection = New-Object System.Data.SqlClient.SqlConnection
$SqlConnection.ConnectionString = "Server = $SQLServer; Integrated Security = True"
 
$SqlCmd = New-Object System.Data.SqlClient.SqlCommand
$SqlCmd.CommandText = $SqlQuery
$SqlCmd.Connection = $SqlConnection
 
$SqlAdapter = New-Object System.Data.SqlClient.SqlDataAdapter
$SqlAdapter.SelectCommand = $SqlCmd
 
$DataSet = New-Object System.Data.DataSet
[void]$SqlAdapter.Fill($DataSet)
 
$SqlConnection.Close()
return $dataset.tables
}
 
$sqlresult = Invoke-SQL imanagesqlserver "select COUNT(1) from [imanagedatabase].[MHGROUP].EM_PROJECTS where ENABLED='Y' AND (STATUS=-1 or STATUS=-3)"
 
$DocGenCount = $sqlresult| select -expand Column1
 
if ($DocGenCount -gt 0 ) {
 
Send-MailMessage -From "email@domain.com.au" -to "email@domain.com" -Subject "EFS Problem Database Support" -Body "Current number of Issues $DocGenCount "
 
}

 

We recently got alerts through however logging into the Worksite Email Filing Server Management GUI there were no marked folders for resetting. This was due to the email address of the iManage user not matching the users filing email

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
Location of this file
 
C:\Users\INSERT_USERNAME\AppData\Roaming\Interwoven\iwovEFSDB.sdf
 
Can you delete this file and it will recreate
 
 
Limit Size
 
You can also trim down the size of the .sdf file by applying theses reg keys:
[HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven\Worksite\8.0\iwovefs
“CacheRows”=dword:0000012c = 45 days
“CacheHistory”=dword:0000002d = 300 rows
 
Disable Suggested Locations
You can disable default suggested locations from being displayed or selected. This prevents filing an e-mail to an incorrect location because that location was selected by default. Set the following registry key to disable the display and selection of suggested locations from both the filing toolbar/task pane and the Select Filing Location dialog:
HKCU\Software\Interwoven\WorkSite\8.0\EMM\Config
[DWORD value] DisableDefaultSuggestion
Value=1

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)