Posts Tagged ‘worksite’

  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


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 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


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
UTC In Use = N
UTC In Use = Y

If this key does not exist 

Run this query in SQL


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


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:


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

To update the WorkSpace for re-indexing:


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
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 "" -to "" -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
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:
“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:
[DWORD value] DisableDefaultSuggestion


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

Worksite/Imanage Monitor can export a document list based on History using the History search but it’s limited in the way it can display comments as well as duplicate Document Numbers. Below is SQL of how to get this direct in SSSM

Change the WorksiteDB to your DB and APPName to your application

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

worksiteCreate a new File Server Location

In the worksite database management , go to File Serveron the Database and assign it a share with the imanage username full permissions

**Restart the Worksite Server Services to accept the new share


Change the a user who is an author of a document you want to move ( check on the existing fileserver or use monitor to check where the file is located ) to use the new file server for that database

Open that file and close it , this will initiate a move to the new fileserver


You can use the tool imRedDoc.exe ( Worksite Document Redistribution Tool) for this task. You can download this via the Worksite Support Site. You will need to download the correct version depending on your Imanage Worksite.

8.5 version can be downloaded through the WorkSite Resource Kit 8.5

Once downloaded, open the file usually found in C:\Program Files (x86)\Autonomy\WorkSite\Server\

Connect to the server with Admin credentials using WSADMIN permissions

Choose the database from which you would like to relocate the files

If you leave the Search Blank , it will do a Database level Search , to itemize this , do the below

Now in Worksite or Desksite create a Saved Search , but right clicking on a workspace in the correct Database and choosing New and Search Folder

Create a filter for this search e.g. this will usually be the creator of the document over a period of time. Create a name for the search and remember it

Go back to Worksite Document Redistribution Tool and enter this name into the Saved Search , click Validate to make sure the Search can be found

If you have specific documents flagged with a boolean value in one of the four document record boolean fields and want only these documents examined and updated, select the boolean field name from the Filter drop-down menu. CBOOL1 is selected by default. ( You can set this to blank if not )

Make sure you login to the Database Administration Tool and set the User’s fileserver to the new one

Click start, and you can see the files examined and files moved , and choose log to see this live

VN:F [1.9.22_1171]
Rating: 1.0/10 (2 votes cast)
VN:F [1.9.22_1171]
Rating: -1 (from 1 vote)

worksiteIn iManage , when you right click a folder or workspace and Choose New then either :

  • Microsoft Word Document
  • Microsoft Excel Document
  • Microsoft PowerPoint Presentation

It comes up with styles that are different to the users

The files are actuallycreated  spawned from files inside

C:\Program Files (x86)\Interwoven\WorkSite\New


You can copy Styles to these documents using

Word 2007/2010: Go to the Developer tab > Templates group, then click Document Template. (If you don’t have the Developer tab [see the Notes below], you can access the Organizer from the Manage Styles dialog box (see Notes) — click the Import/Exportbutton in the bottom left corner.)


  1. Select the tab for the type of object you want to copy — e.g. Styles orMacro Project Items. For this example, you’ll copy some styles from another document to the one you have open; the same method is used to copy macros.
  2. Click Close File below the right panel. (You would usually close as you want to copy from another document, not the Normal template.)
  3. Click Open File below the right panel. By default, Word opens your Templates folder and sets the file type as a Document Template (*.dot) file.
  4. If you’re copying from another document and not a template, change the Files of type to Word Documents (*.doc, *.doc*), then navigate to the folder where the document you want to copy the styles from is stored.
  5. Select the document you want to copy from, then click Open.
  6. The name of the file you selected displays in the Styles available in field below the right panel in the Organizer dialog box.
  7. In the right panel, select one or more styles that you want to copy. UseCtrl+click and/or Shift+click to select multiple styles. In the screen shot below, I selected two Table styles.
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

How to create a new iManage/Worksite Database

worksite1) Create new blank Databases on an SQL / Oracle Server and create or use existing iManage user full rights
2) Add these Databases to the ODBC Sources under Administrative Tools with correct credentials ( Make sure it’s 32bit C:\Windows\SysWOW64\odbcad32.exe ) 
3) Use Imanage Database Administrator to Register a new Database ( right Click on Worksite Databases and Click Register )
4) When it asks for Operating System Path , this is the file server location so point it to the file server e.g. \\imanagefilesvr\sharename
5) This creates all the tables and meta data in the table.
6) Once done open Worksite Service Manager and click the databases button
7) Choose Add Database
8) Find the ODBC Source and add a loginID and password.
9) Add indexing if needed e.g. IDOL Indexer as well as server name of indexer
10) Restart Worksite Server and check logs of connection sucessful

To configure WorkSite Indexer to index content from a new WorkSite library
1. Ensure that you have a backup of your index data.
2. Back up all WorkSite Indexer configuration files.
3. Start the Deploy Tool by running the deploy-8_5.bat file located in the
installation directory.
4. Specify a new output directory that does not overwrite any existing
configuration files.
5. Ensure that the settings that you used to deploy the WorkSite Indexer are still
shown in the Deploy Tool. If the settings are not shown, reconfigure the
Deploy Tool with the same settings that you originally used.
6. Select the Indexer tab.
7. Click Add to add another WorkSite Library. The Add Library Configuration
dialog box opens.
8. In the Add Library Configuration dialog box, type the new WorkSite database
and connection information, then click Test.
9. After the connection test has completed successfully, click OK.
10. Click Grey Cog (Regenerate configuration files). NOT Deploy ( Green Arrow)
11. When the deploy process is complete, click Done, and then close the Deploy
12. Stop the WorkSite Indexer services. See “Stop Individual WorkSite Indexer
Services” on page 88.
13. Navigate to the output folder you specified in the Deploy Tool.
14. If you have not made any additional manual configuration changes, you can
run the _deploy_services.bat file with the new configuration files. If you
have made manual changes to the configuration files, continue with Step 15.
15. Open the following new configuration files, and compare them to the deployed
versions from Step 1.
? WorkSite Connector.cfg
? WorkSite IDOL.cfg
? Worksite ContentN.cfg (if multiple Content servers exist, you must
copy all the configuration files)
? Worksite Active Content.cfg (if applicable)
? Worksite DiffTool.cfg
? Worksite Metadata Content.cfg (if applicable)
? Worksite Workspace Content.cfg (if applicable)
Add Content Servers
WorkSite Indexer Administration Guide 149

16. After confirming all configuration parameters, replace the existing
configuration files in your deployed directories with the new versions.
17. Restart the Indexer services. Use the Index Browser to ensure that the new
index database exists, and that the Indexer starts to process files from this
new WorkSite library.

How to Add Database to Communication Server

  • Add the Database to the Communication Service Properties with a user which is in NTRADMIN Group ( If this group doesn’t exist create it! ) and add user
  • Add the database to the Email Filing Server under Worksite Connect. You may need to stop the service to do this, and add on the end of Databases, Save
  • Restart the Communication Service and Filing Service
VN:F [1.9.22_1171]
Rating: 7.0/10 (1 vote cast)
VN:F [1.9.22_1171]
Rating: +1 (from 1 vote)