What ports are required for connection when using QCS? (4351817)
What ports need to be opened and will be used when QCS is working? ... There is no need to open any special ports between the HQ and any Branches when using QCS. ... This tool will collect the data and will send it per e-mail to the partner, so as long as e-mail (SMTP) communication is working the tool will work.
How To Configure a Free/Busy Synchronization in an Exchange 2007 and Exchange 2010 Environment (4241022)
Outlook Users with Mailboxes on an Exchange 2007/2010 Server would like to be able to access the Free/Busy Data for Users from a Collaboration Partner. ... This is possible if the Exchange availability service is configured correctly, and a valid replica of the Shedule+Free/Busy public folder is able to be accessed by the Exchange 2007/2010 Mailboxes.
When updating a calendar for a user in a remote forest I get the error "could not be updated" (4272045)
When updating a calendar for a user in a remote forest I get the error "could not be updated" ... When opening the calender for a user in a remote forest you are opening the calendar in the Stub mailbox which cannot be updated by users.
Unable to connect to QCS using a web browser (4291627)
Users are unable to connect to QCS using a web browser. ... Local access on the QCS server works fine. ... This is an issue for QCS when hosted on a 64-bit operating system. ... The issue is due to the web service with the Microsoft SOAP Toolkit for communication, as web services extension, it stops working on 64-bit system.
Stubs are not created for source objects that do not have a LegacyExchangeDN (4219874)
<p>A publication is created for user objects that do not have the LegacyExchangeDN attribute populated. ... The QCS server on the subscriber does not create stub objects for these users.</p> The LegacyExchangeDN attribute is required for QCS to properly publish and create stub objects.
Outlook fails to deliver message, The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message (4303046)
The e-mail address you entered couldn't be found. ... Please check the recipient's e-mail address and try to resend the message ... Delivery has failed to these recipients or groups: ... This error occurs because there is a problem with the legacyExchangeDN of the mail-enabled Contact/user you are trying to send to.
Quest Messagestats and how it can be used before and during a migration (4211799)
When Quest's migration tools are deployed by Quest Professional Services, Quest Partners or other consultants, Quest strongly encourages the use of Quest Messagestats in support of the migration effort.
QCS sync stops working entirely, "Invalid messages were received from these addresses: (4275744)
No updates are received from the synchronization partner - it may also be listed as "not responding". ... This may occur if the primary SMTP address of the branch service account has been changed.
How do you set up the Remote connection for Quest Collaboration Services? (4320944)
How do you set up the Remote connection for Quest Collaboration Services? ... If QCS has been installed before the IIS was installed console, then the following from the installation Guide must be followed.
Configuration database maintenance failed cannot VACUUM from within a transaction (4222633)
In the Events node you see an event similar to the following: ... Code : 0x80049f01,Description : cannot VACUUM from within a transaction [EIP: 0x03155E01,0x03167AB3]" ... AntiVirus or indexing service is scanning the Collaboration Services directory at the time the database (.sdb) files are being written to.
How to rebuild the MAPI Subsystem for MAPI CDO (4319638)
Run a Search for EMSABP32.dll and rename it to EMSABP32.dll.old ... Run a Search for CDO.dll and rename it to CDO.dll.old ... Run a search for fixmapi.exe and then Right click on it and Select Open ( Nothing should happen which is expected behavior)
Failed to update object <ObjectName> in collection <CollectionName> (4234872)
[EIP: 0x0442EF9F,0x04444AC3] [EIP: 0x04352E26,0x04357395] [EIP: 0x0123B579,0x05398096] [EIP: 0x0539809F,0x054B6785] ... The Domain Controller in the error returned a referral when querying for the user object
TargetAddress is populated with incorrect value, instead of primary SMTP another address was used (4353360)
Some of published users have multiple proxy addresses with the same namespace, eg. ... and company.com is the Namespace which is allowed under QCS properties. ... When creating the stub object QCS uses any of the listed above proxy addresses randomly, and this is causing inconvenience.
Considerations when troubleshooting various QCS issues. (4354262)
There are some issues and all attempts to resolve them are causing inconvenience or even jeopardizing the production becausea wrong step might result in the removal of target objects from the GAL.
Is the Permitted senders list of a source DL replicated to the target stub DL? (4219772)
If you add a DL that has a permitted senders list to a publication does the permitted senders list get synched and added to the target stub DL? <p>Yes the permitted senders list will get synched to the target stub DL.
After an object has been removed from the publication the subscribers are still getting an error. (4267440)
After an object has been removed from the publication the subscribers are still getting an error: "Error code 37995 packet processing from packet queue failed for object...." <p>On the subscriber with the error:</p>
After Reprocessing a Non-Applied Object the Stub Object Calendar is not created. (4247752)
This Can happen if the Object was listed under Non-Applied Objects for and extended period of time. ... The initial Calendar Sync packet my have been discarded as obsolete. ... Verify the retention period for Calendar Packets in the Collaboration Services Console on the subscribing side:
How can Collaboration Services and Federated Serices work together? (4320285)
Currently we have no processes or documentation that will support this configuration.
NAMING VIOLATION (4331084)
Normal user accounts should not be CNF objects. ... If a conflict exists it should be cleaned up in AD and then after you fix the account the error will go away.
No Calendar Receiver events after subscribing to a Calendar collection. (4271913)
In the QCS Console there are no Calendar Receiver events after subscribing to a Calendar collection. ... The following errors are logged in the debug logs. ... MAPIServ.log ... 02/10 10:35:02:436 | CalendarApplierImpl.cpp(83) | 8792 | *** EXCEPTION Exiting CCalendarApplierImpl::OpenUserCalendar
During Install Error: "8007022F - A constraint violation occurred" (4280408)
Verify the permissions required for deploying Collaboration Services for Exchange.
Custom LDP filters and how to obtain help (4351454)
LDAP filter is not working. ... Can Quest Software Support assist with troubleshooting the filter and creating a working one? ... Quest Technical Support does not assist when creating, validating, testing or modifying any custom LDAP filters.
QCS (Quest Collaboration Services) keeps loosing MAPI connectivity to the service mailbox (4307758)
The following errors are reported consistently in the QCS Events Log with the specific time interval: ... MAPIServ.log contains the following entries corresponding to the above events: ... The same can be reproduced with MFCMAPI when logged with QCS service account into its mailbox:MAPI application will fail on access to the above mentioned folders.
Where should Collaboration Services be installed when there is an Exchange Resource Forest? (4243682)
<p>When Exchange is installed in a forest and the user accounts are in a different forest, which forest should host Collaboration Services</p> <p>Install the QCS in the resource forest. ... As all of the Exchange specific Active Directory objects reside in the forest where Exchange is installed, Collaboration Services should be installed on a server in the same forest.
Distribution Lists are not synched when the publication is populated using groups (4225660)
When creating your publications you used groups to specify which user accounts you want to publish. ... These groups as well as the user objects which are members are synched to the subscribing QCS forest, however Distribution Lists which are members of these groups are not synched.
신제품 조합