SRMError – Error creating test bubble image from group instance ‘RGID-xxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx’ of group ‘GID-xxxxxx-xxxx-xxxx-xxxx-xxxxxx’ on VR Server ‘localhost.localdom’ (address ‘’). VRM Server generic error. Please check the documentation for any troubleshooting information. The detailed exception is: ‘java.lang.NullPointerException’

This happens due to problem RGID which needs to be recreated by the following method for each VMware Machine:

1) Rename the VM Datastore folder for the problem VM on the remote side to something else like vmname.old

2) Wait for the machine sync Replication Status to come up as not active in the vSphere Replication ( You can use Pause Replication then Resume to force this)

2) Stop and remove the replication

3) Rename the VM folder back to the previous name

4) Reconfigure Replication and use the existing data as a seed

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

vmware_vcenter_site_recovery_manager_diagramWhen trying to test a Recovery Plan ( DR Bubble ) upon the starting up two of the machines we get the following error show up in the Errors

Error – Unable to copy the configuration file ‘MachineName.vmx’ from the host to ‘C:\Windows\TEMP\vmware-SYSTEM\machinename.vmx324-0’  – No file exists for given path.

We check the replication status manually as the gui is sometimes out of date by SSHing  into the host with the virtual machine and using:

vim-cmd vmsvc/getallvms | grep –i vmname

This will give you the ID of the machine where you can then do this

vim-cmd hbrsvc/vmreplica.getState vmnameid

The status of the machine was just IDLE instead of Inactive which is incorrect.

Found using this command in /var/log/

grep -i hbr vmkernel.log | grep ” LWD delta transfer terminated (aborted)” | awk ‘{print $10}’ | sort -u

Brought up a load of diskid’s that had issues one of them was our VM. In the end we had to remove replication and reseed again.

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 user who could not access the Sharepoint site via Chrome/IE, it kept presenting the user with a username and password box. Other users in the organisation could access it fine.

On another computer we used the Sharepoint option of Signing In As Different User and signed in as the problem user and it worked fine.

Checking the proxy settings on the computer to make sure the URL/Server address was being bypassed which it was.

Went to Credential Manager in Control Panel

Removed the Windows Credentials for reference to the website, Fixed!


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

citrixiconWe recently rolled out Chrome in our enviroment , a user’s default browser went back to IE one day. On going to default programs in Control Panel , HTTP/URL links where all defaulted to Citrix Metaframe Server FTA and greyed out. This task is responsible for redircting http traffic to the local client for Flash Redirection/Rendering however this does not work with Chrome.

Trying to set these back to chrome would not work using the GUI. For some reason the Chrome Icon in the default programs was not showing either. This was not a local machine ( HKLM or HKCR )or server problem as other users logging into the machine could default to Chrome fine.

In the end, to reset the defaults, I had to delete this key for the user and reset the defaults via the GUI


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

worksiteAfter an Indexer Server Veeam restore, the Worksite Connector/Crawler started but no log file updated, which meant it was in a stale state.

Stop the Worksite Connector Service

Go to the directory : Worksite Connector\actions\fetch

Delete fetch.queue file

Start the service back up

Check to make sure the log file location in Worksite Connector\logs\worksiteCrawler.log is updating

You might want to check the ingestion service log is also updating or you might need to clear the ingest.queue

If below does not work this might need to be done

  1. Stop all services.
  2. Ran _cleanup scripts from E:\Indexer\WorkSite Connector\ &  E:\Indexer\WorkSite Ingestion Server\
  3. Changed the time in this file E:\Indexer\WorkSite Connector\connector_DBNAME_datastore.db back to “m/d/yy” the date when the indexer stopped working. Please note this time is in “epoch” so you will need a timestamp converter.
  4. Started services.

To stop and start the services, there are 2 methods:

  1. Run the script in “IndexerInstallDrive\Indexer\_stop_services”, “IndexerInstallDrive\Indexer\_start_services”
  2. Log into the Autonomy Control Center “http://IndexerServerName:8080/controlCenter”. Default username and password – admin/admin. Once logged in you can stop and start all services in the GUI.


  Essentially when indexing, data flows in the following order:

  1. The WorkSite Connector service to crawl WorkSite databases servers.
  2. The WorkSite Ingestion service, which converts all files to the IDX format.
  3. The WorkSite Content service, which indexes all of the content and serves search requests.

  When troubleshooting indexer issues, the logs are key to identifying issues. I recommend you use ‘BareTail’ as this allows you to view the many logs as well as the changes to them, each component has at least 5 types of logs.

                Connector: componentinstalldisk:\Indexer\WorkSite Connector\logs

                Ingestion: componentinstalldisk:\Indexer\WorkSite Ingestion Server\logs

                Content: componentinstalldisk:\Indexer\WorkSite Content\logs


Here is a nice write up from Autonomy from when the client wants a better understanding about timing with the indexer:

1. Customer drags a document into WorkSite (~1-2 seconds, very minimal)

2. WorkSite Crawler crawls searching for new/updated documents during interval of time between each crawl. (takes a 1 minute rest between crawls)

3. Document is moved through Ingestion (~1-2 seconds, very minimal)

4. Document is moved through Active DIH (~1-2 seconds, very minimal)

5. Document is moved to Active Content, where every 15 seconds Active Content writes the data to disk making it available for search.

So the time for a new document to be indexed is a lot based on where the Connector and Active Content is on it’s interval. Potentially you could see a 1 minute 30 second delay, or potentially only a 30 second delay before searchable.

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


– Manager saves unsent email to his Drafts folder in Outlook 2010
– Secretary has manager’s mailbox listed in her Outlook 2010 folders list.
– Secretary accesses her manager’s Drafts folder and sends the email for him with his credentials in the From field (email sends without issue).

Per Outlook 2003 this is a known fault

However Outlook 2010 it should not do this


Go to the From Field and delete all the autocompleted From Fields

Remove the Show From Field and Close Outlook

Reopen Outlook and try again

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

Re00002[1]cently on unmounting and remounting some exchange databases to stop 24/7 Maintence ( causing 8mb/s read traffic on our exchange EDB’s ) caused the search functionality to stop working

We had this before when the server , as we rebuilt the catalog files from Scratch ( Stop Microsoft Exchange Search Service, Delete the Catalog Folder for DB, Start Microsoft Exchange Search Service ) , however this puts heavy load on the exchange server as well as taking hours depending on the size of the DB ), and we wanted to get search returned ASAP

 We ran Troubleshoot-CI.ps1 which can be found in the Exchange\Scripts folder on the exchange server, which showed the server was deadlocked

 It logged events in the Microsoft-Exchange-Troubleshooters/Operational for the databases :

Detected indexing stall for database DatabaseName. Stall counter value 5059. Stall threshold value is 3600 seconds

We then Ran Troubleshoot-CI.ps1 -Action DetectAndResolve which restarted the Search Service ( Which we already did ) but it seemed to Disable it for a while which makes me think it did some other stuff!

Anyway search came back within 3 minutes of running , however it forced a reindex update across the rest of our Mailbox servers for some reason!

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

worksiteWhen selecting multiple files in iManage worksite and right clicking and choosing open , it crashes Word on opening

To resolve this, the following registry key will need adding >:

Citrix server: HKEY_Current_User\Software\Microsoft\Office\14.0\Word\Options “DisableRobustifiedUNC”=Dword:00000001

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

km_67019_large[1]Recently unboxing a UCS 420 M3, I tried to boot the server and access the CIMC , however upon pressing F8 to boot into the CIMC console, it would display the CIMC briefly with some Errors about DNS and Hostnames , then show Failure to communicate with CIMC then continue the normal boot procedure. I tried getting access to the CIMC through the BIOS ( Usually with the F8 key ) however this would not work either.

In the end I had to Update the Bios and other features of the server to the latest version (6b) via steps below

Download the HUU ISO file:

  1. Navigate to the following URL: http:/?/?
  2. In the middle column, click Servers – Unified Computing.
  3. In the right-hand column, click Cisco UCS C-Series Rack-Mount Standalone Server Software.
  4. Choose the name of your model of server in the right column.
  5. Click Unified Computing System (UCS) Server Firmware.
  6. Choose the release number.
  7. Click Download Now to download the ucs-server platform-huu-version_number.iso file.
  8. Verify the information on the next page, and click Proceed With Download.
VN:F [1.9.22_1171]
Rating: 9.7/10 (3 votes cast)
VN:F [1.9.22_1171]
Rating: +1 (from 1 vote)

WorksiteSaveOperationOK , so when you save a .xls file in 2010 from 2003 , explorer bugs you with : “filename.xls cannot be saved in the current format. To save your changes, click OK, then save it as the latest format.”

This dialogue box then breaks the iManage save as functionality which then brings up

 And you have to resave the document as a .xlsx or resave as a .xls which stops bugging you with message. This is no good for people with linked documents  . I have found no way to disable the first dialogue box/error

Solution for Explorer

1) Save the file to explorer , open the file with 2010 , click ok to the error message , then save it back as an xls ( overwrite )  , then you can open and save from explorer

Solution for iManage/Worksite

1) Save the file to explorer from your DMS file server, rename from docnumber.version to docnumber.xls , open the file with 2010 , click ok to the error message , then save it back as an xls ( overwrite ) , then you can open and save no drama’s from explorer

2) Rename file back to docunumber.version then copy this file back to the iManage file server and it enables the file to be opened saved from 2003 and 2010 no errors.

So 2010 must rewrite the file with new meta data!

VN:F [1.9.22_1171]
Rating: 10.0/10 (2 votes cast)
VN:F [1.9.22_1171]
Rating: +2 (from 2 votes)