|
Pa-software community Help, support and conversation |
|
|
|
|
|
<< prev 1, 2 next >> |
markp
Newbie
Group: Moderators
Posts: 17
Joined: Jul 20, 2009
|
Are you using internal disclaimers? If so, does switching the delivery type temporarily to external only allow replication?
Another option is to update the engine to allow the use of an exempt users list rather than the AD group. If you would like to do this, please e-mail support so that we can send you the details.
|
|
|
Posted Jul 19, 2010, 4:13 pm |
|
|
|
markp
Newbie
Group: Moderators
Posts: 17
Joined: Jul 20, 2009
|
This does sound like an issue that occured with an older version of QS Disclaimer and an Exchange/Windows update. So if you are not using 2.6.18, I recommend upgrading to the latest version first.
|
|
|
Posted Jul 17, 2010, 10:10 am |
|
|
|
markp
Newbie
Group: Moderators
Posts: 17
Joined: Jul 20, 2009
|
This error is due to not restarting the IISAdmin service after uninstalling version 1 of QS Disclaimer.
If you restart the IISAdmin service it will release the cached version 1 engine.
|
|
|
Posted Feb 24, 2010, 4:20 pm |
|
|
|
markp
Newbie
Group: Moderators
Posts: 17
Joined: Jul 20, 2009
|
Did you allow an IIS restart when you uninstalled the demo? As this can be postponed, but is required for a full uninstall. If you did not allow an IIS restart (or the restart was interrupted), you will need to stop and start the disclaimer system in the disclaimer manager and allow an IIS restart so that any caches can be released.
|
|
|
Posted Dec 14, 2009, 7:14 am |
|
|
|
markp
Newbie
Group: Moderators
Posts: 17
Joined: Jul 20, 2009
|
Are you forcing the use of a message encoding that can cope with accented characters? If not then you need to set the disclaimer to use ISO-8859-1 as the message encoding, as Exchange may not change the original message encoding after the disclaimer has been added.
|
|
|
Posted Nov 18, 2009, 7:24 pm |
|
|
|
markp
Newbie
Group: Moderators
Posts: 17
Joined: Jul 20, 2009
|
Have you enabled the 'Disclaimer users' group in the disclaimer manager and updated the configuration data? As this is required to force an update of the Active Directory group cache.
Another way to force a cache reload is to restart the disclaimer in the disclaimer manager.
|
|
|
Posted Oct 27, 2009, 9:41 pm |
|
|
|
markp
Newbie
Group: Moderators
Posts: 17
Joined: Jul 20, 2009
|
Version 2.5.13 has fixed failures to connect and update by a remote client. It also removes the need to have the manager open on the server.
|
|
|
Posted Jul 20, 2009, 8:52 pm |
|
|
|
<< prev 1, 2 next >> |
v2.0.6 © Pa-software 2005-2015
|