Check the below

 

http://prev.mydomain.com:18681/admin [Running, Access from Work Server]

Steps

 

  1. Restart Prizm Service on your Preview Server is not started

     

  2. Check registry on your Workserver

    – Ensure the registry MSH Host contains the correct value in the following format: ‘http://hostname:PortNumber’

    – Ensure the registry PAS Host contains the correct value in the following format:

    ‘hostname:PortNumber’

    Note: The port number should be the same in both registry entries.

     

  3. Check the configuration file ‘rendition.cfg’ on your Workserver to ensure that the ‘RenditionEngineAlpha-Preview’ section is pointing to ‘end_point = http://hostname:18681/PCCIS’

     

  4. Install the same SSL cert (as used in the Work10 server) into the Preview Server

     

  5. Restart the following services (even if it is started) from your Work10 server

    iManage Active MQ
    iManage Micro Services Hub

  6. clear Preview Cache manually, please perform the following steps:

    1. Delete all cache from the DOCPREVI user in the correct file server
    NOTE: Delete all content within this folder, do not delete the DOCPREVI folder itself
    2. Delete all Preview cache from the rendition_cache table in the database. To do this, run the following:
    delete from mhgroup.rendition_cache where storage_class = ‘docpreview’

  7. Make sure as mentioned above that “Preview Storage” on your DB’s in DB Admin are checked off
  8. Check Rendition.cfg configurations
  9. Check that the service account can read and write to the preview cache.
  10. Reinstalled the Preview server software

Logs

 

 

MsOfficeConverter.log in Preview Server:

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

PreReq

  • VM Shapshot
  • Backup Registry ( HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Interwoven
  • Backup C:\Program Files\Autonomy\WorkSite\Apache\conf\worksite.conf
  • Have your WorkSite Server Serial Number Ready
  • Have your .key and .crt files for your Certificate
  • Check what iManage Work Server Service user currently runs as

 

Installation

  • Run Installer over the top
  • Enter Serial Key and Certificate Files
  • Once Installed Reboot Server
  • Change the iManage Work Server service to Run as a specified user found in PreReq
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 we changed the IP and Subnet of an exchange 2016 server. Trying to Open ECP Showed the Error :

Topology Provider coundn’t find the Microsoft Exchange Active Directory Topology service on end point

This is due to the Server Microsoft Exchange Active Directory Topology not starting

The service was not starting because of the new Subnet was not listed in Active Directory Sites and Services which meant Exchange was not sited aware

Add the domain and restart the server 

 

 

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

This was due to a misconfiguration on the vsf  

  member 2

      type "JL255A" mac-address xxxxxx

      priority 128

      link 1 2/23-2/24

      link 1 name "I-Link2_1"

      link 2 name "I-Link2_2"

Should of been :

  member 2

      type "JL255A" mac-address xxxxxxxxx

      priority 128

      link 1 2/23

      link 1 name "I-Link2_1"

      link 2 2/24

      link 2 name "I-Link2_2"

      exit

   port-speed

 

Commands to run to remove a link from a vsf member : 

no vsf member 2 link 1 2/24

then

vsf member 2 link 2 2/24

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 we started getting errors for our Vcenter address which was a subdomain of our main domain which had a proper certificate for the website. Chrome picked this up and then uses HSTS to make sure all subdomains have a valid cert ( Without an easy option to Bypass ) 

However to bypass just type either word below when presented with the error

thisisunsafe” or “badidea

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 on setting up a new internet connection, I ran a speed test via ( speedtest.net ) with produced the following error

Latency Test Error – Could not connect to the test server A firewall could be blocking the connection or the server might be having some issues

Pinging Google DNS Server 8.8.8.8 came up with a sold under 15m response , strange?

I tried playing around with the MTU to no avail either

Turns out this is actually a DNS issue, the local DNS servers had forwarders set to their Old ISP , so change the DNS to the new ISP or Google fixed this!

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 had a customer use crazydomains for their Emails. Incoming email stopped with the error below

550 Please turn on SMTP Authentication in your mail client. mail-wm1-f50.google.com [209.85.128.50]:38049 is not permitted to relay through this server without authentication.

I check the MX / NS servers to make sure they were pointing a valid records.

Called support and they asked me to remove off Automatically Detect and change to Local Mail Exchanger , it took 15 minutes to apply and starting working again. Guessing their internal DNS had an issue

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. Verify that FileSite or DeskSite and all other iManage Work add – ons are completely uninstalled.
2.
Install 9.3.3 Silently: Setup.exe /s /v”/qn SERIALNUMBER=<serial number> EM_STATUS=OFF”/v”INT_3P=0″
or:
MsiExec.exe /i /qn SERIALNUMBER=<serial number> EM_STATUS=OFF INT_3P=0
3. Run iManage Work.exe to install 10.0.2 Work 10 Client
4. If you have installed FileSite , manually enable the FileSite Add in in your Mail Setup – Outlook \ Data Files
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Symptoms:

  • Missing captions in Outlook tree navigation pane
  • Outlook Ribbon is missing Buttons
Cause:
  • Custom VDM file created for each folder Highlighted in
  • FileSite  ( NOTE: Only applicable to Outlook 2013 and later ) 
Solution:
Pre 9.3.2  : Apply CSAR 2384
9.3.2 and later : Fixed (no need for CSAR)
 

Symptoms:

  • Black boxes on the
  • EM Toolbar
Cause:
  • GDI+ object leak in
  • EM Toolbar
  • component
Solution:
Pre 9.3.2: NT – 60478 resolved in CSAR 2419v5
9.3.2: Fixed
10: Not applicable

 

Symptoms:

  • Black boxes on Outlook buttons
  • Sections of Outlook appear white
  • Distorted Outlook tree pane
  • Emails opening with blankcontent
  • Missing navigation panels
  • Outlook crashing
 
Cause: Memory leak in Outlook 2016 or 365
 
Solution:
  • As diagnosed by Microsoft, the symptoms manifests when Outlook uses more than 1.6 GB of virtual memory.
  • The fix for this specific issue is planned to be released in 3 patches.
  • The first part was released in March via update KB3178668, part two was released in June with KB3191932 and a third patch TBD.
 
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)