By using AWS re:Post, you agree to the Terms of Use

Questions tagged with Amazon WorkDocs

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Power Users can't invite external users?

In the WorkDocs documentation, in [this link](https://docs.aws.amazon.com/workdocs/latest/adminguide/manage-sites.html#ext-invite-settings) in the section on "Security - external invitations", it claims that Power Users can be set up to invite external users. However, in the administration panel it doesn't exist. Our company has one administrator for WorkDocs, but could potentially have a few hundred power users. Those power users will have control over their allocated 1TB of space (and be on their own site), and they need to be able to invite external users to view a folder. Each power user might have a hundred or so external users that need to view folders in their space. What won't work at all is those power users having to contact the admin to send a link to every single external user they need to view their folders because that could potentially be 20,000+ external invitations that would be piled onto the one admin. It also won't work to make each of those power users an admin, because you'd run into the possibility that they could inadvertently create and/or invite paid users, and the cost to our company would skyrocket unnecessarily. Bottom line, we need to be able to have power users invite external users and ONLY external users--they should have ZERO ability to create or invite paid users. Those external users need to be able to view the contents of folders that the power user sets up. Can this be done? Thank you, -Brent
0
answers
0
votes
31
views
asked 3 months ago

Cannot uninstall AWSWorkDocsDriveClient completely from computer

Hi all, I'm trying to uninstall WorkDocs as I had only used it as part of a remote position that I am no longer with. However, even when uninstalling the program AWSWorkDocsDriveClient from Control Panel, the program folder and various files remain on my computer. I still see the auto-update service running in both task manager Processes and Services. The updater also activates on start-up even though I'd disabled Amazon WorkDocs Drive from being able to start when turning on my computer, and of course, uninstalled the program. The program still can still open from the program folder, and I can't get rid of it completely from my hard drive. I've tried to reinstall the software and uninstall again, but no matter what the AWSWorkDocsDriveClient program folder and files still remain, as well as the auto-update service in my list of services. (I can disable it from starting, but I would just like to get rid of it altogether.) The WorkDocs drive program remains in my list of available apps on startup in Task Manager after being uninstalled, either. Windows 10 Home Version 21H1 OS build 19043.1237 Please let me know if I can provide any more information to potentially assist with troubleshooting/solving this issue. Thank you in advance. Edited by: s19k11 on Sep 25, 2021 8:53 AM Ended up using a combination of AutoRun and Process Explorer to get rid of the services and process that kept WorkDocs from launching
1
answers
0
votes
51
views
asked 10 months ago

WorkDocs Drive is shutting down due to an error (Win10)

Good morning, I've been using WorkDocs for around 6 months. This morning went I went to use WorkDocs, a pop-up in my taskbar showed, "WorkDocs Drive is shutting down due to an error!" I tried to restart WorkDocs and kept getting the same error. I'm running Win 10 Pro (ver 2004), 32GB RAM, 500GB SSD, on a machine that I replaced a month ago on July 2, 2020. OS Build is 19041.388. Also running Norton 360. All Windows Updates have been applied, with the last update being KB4562899 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 2004, installed Aug 8, 2020. The WorkDocs logs show: \[code] System.Messaging.MessageQueueException (0x80004005): Message Queue service is not available. at System.Messaging.MessageQueue.Create(String path, Boolean transactional) at AWSWorkDriveClient.Sync.MessageQueueJournal.<>c__DisplayClass24_0.<Create>b__0() at AWSWorkDriveCommon.Util.Functions.<>c__DisplayClass3_0.<ToFunc>b__0() at AWSWorkDriveCommon.Util.RetryStrategy.Call\[R](Func`1 callback, OnRetriesExhaustedThrow retryExceptionType) \[2020-08-11 15:03:53,483]\[thread8]\[INFO ]\[AWSWorkDriveCommon.Util.RetryStrategy] - Exception is retryable, in 00:00:02 will use retry 2 of 5. Same cause. \[2020-08-11 15:03:55,498]\[thread8]\[INFO ]\[AWSWorkDriveCommon.Util.RetryStrategy] - Exception is retryable, in 00:00:04 will use retry 3 of 5. Same cause. \[2020-08-11 15:03:59,512]\[thread8]\[INFO ]\[AWSWorkDriveCommon.Util.RetryStrategy] - Exception is retryable, in 00:00:08 will use retry 4 of 5. Same cause. \[2020-08-11 15:04:07,526]\[thread8]\[INFO ]\[AWSWorkDriveCommon.Util.RetryStrategy] - Exception is retryable, in 00:00:16 will use retry 5 of 5. Same cause. \[2020-08-11 15:04:23,543]\[thread8]\[ERROR]\[AWSWorkDriveClient.WorkDriveClient] - Unhandled exception raised by Name:AWSWorkDocsDriveClient.exe There are no context policies. System.Messaging.MessageQueueException (0x80004005): Message Queue service is not available. at System.Messaging.MessageQueue.Create(String path, Boolean transactional) at AWSWorkDriveClient.Sync.MessageQueueJournal.<>c__DisplayClass24_0.<Create>b__0() at AWSWorkDriveCommon.Util.Functions.<>c__DisplayClass3_0.<ToFunc>b__0() at AWSWorkDriveCommon.Util.RetryStrategy.Call\[R](Func`1 callback, OnRetriesExhaustedThrow retryExceptionType) at AWSWorkDriveClient.Sync.MessageQueueJournal.Create(String queueName, Boolean isCleanStart, RetryStrategy readRetryStrategy) at AWSWorkDriveClient.WorkDriveClient.<>c__DisplayClass25_0.<CreateJournal>b__0() at AmazonWorkDocsDriveFramework.Journal.DedupingJournal..ctor(Int32 maxCacheSize, IFeatureManager featureManager, Func`1 delegateJournalFactory, MetricsReporter metricsReporter, CacheFactory cacheFactory) at AWSWorkDriveClient.WorkDriveClient.CreateJournal(WinClientOptions options, IFeatureManager fm) at AmazonWorkDocsDriveFramework.WorkDriveFramework.Initialize(SystemType systemType, Options options, AppRestartManager appRestartManager, IncidenceLogManager incidenceLogManager, MetricsReporter metricsReporter, INativeOperations nativeOperations, ISystemNotification systemNotification, List`1 customLocalOnlyDeciders, AggregatedAvailabilityTracker availabilityTracker, PeriodicAvailabilityTracker networkAvailabilityTracker, Boolean identifyLocalOnlyFodler, Func`2 databaseProviderFactory, Func`2 mountPointFactory, Func`2 journalFactory, Func`2 providerFactory, Boolean performCreateDeleteEliding, String& mountPoint, ManualSwitchAvailabilityTracker& manualSwitchAvailabilityTracker, UserInfo& userInfo, Optional`1& logUploadClient, IStorageProvider& storageProvider, JournalChangeReferenceManager& journalChangeManager, IReferenceManager`1& refManager, LockManager& lockManager, PathValidator& pathValidator, IResourceNameValidator& resourceNameValidator, IPathConverter& pathConverter, IMetadataManager& metadataManager, IFavoriteDataManager& favoriteDataManager, GarbageCollector& gc, IHardLinkManager& hardLinkManager, IFileRecoverManager& fileRecoverManager, IAsyncFetchFolderManager& fetchFolderManager, IDatabaseProvider& databaseProvider, ICacheManager& cacheManager, IPermissionsManager& permissionsManager, IJournal& journal, Func`1& journalTimerFactory, IJournalReader& journalReader, IFeatureManager& featureManager, ITempFilesManager& tempFilesManager, DriveStatusMonitor& driveStatusMonitor) at AWSWorkDriveClient.WorkDriveClient.CompleteInitialization(WinClientOptions options, AppRestartManager appRestartManager, IncidenceLogManager incidenceLogManager, AutoUpdateSingleton autoUpdate, IWindowsSystemNotification winSystemNotification, IWDObserver`1 systemPopupNotificationObserver, ITaskExecutor executor, Func`1 metricsTimerFactory, String exePath) at AWSWorkDriveClient.WorkDriveClient.<>c__DisplayClass22_0.<run>b__1(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() \[2020-08-11 15:04:23,551]\[thread8]\[INFO ]\[AWSWorkDriveClient.View.SystemTray.WindowsTraySystemNotification] - WorkDocs Drive is shutting down due to an error! \[/code] The incidence log shows: \[code] \[2020-08-11 15:00:31,753]\[thread8]\[ERROR]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - === end failure info === \[2020-08-11 15:04:23,549]\[thread8]\[INFO ]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - Version: '1.0.5378.0' \[2020-08-11 15:04:23,549]\[thread8]\[INFO ]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - Build Type: 'prod' \[2020-08-11 15:04:23,549]\[thread8]\[INFO ]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - System Type: 'windows' \[2020-08-11 15:04:23,549]\[thread8]\[INFO ]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - OS Version: 'MicrosoftWindows10Pro' \[2020-08-11 15:04:23,549]\[thread8]\[INFO ]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - dotNet Version: '528372' \[2020-08-11 15:04:23,549]\[thread8]\[INFO ]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - CLR Version: '4.0.30319.42000' \[2020-08-11 15:04:23,549]\[thread8]\[INFO ]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - Thread Culture: 'en-CA' \[2020-08-11 15:04:23,549]\[thread8]\[INFO ]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - Thread UI Culture: 'en-US' \[2020-08-11 15:04:23,549]\[thread8]\[INFO ]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - Storage Provider: 'WorkDocs' \[2020-08-11 15:04:23,549]\[thread8]\[ERROR]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - === begin failure info === \[2020-08-11 15:04:23,549]\[thread8]\[ERROR]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - WinErrorCode='16389' \[2020-08-11 15:04:23,550]\[thread8]\[ERROR]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - System.Messaging.MessageQueueException (0x80004005): Message Queue service is not available. at System.Messaging.MessageQueue.Create(String path, Boolean transactional) at AWSWorkDriveClient.Sync.MessageQueueJournal.<>c__DisplayClass24_0.<Create>b__0() at AWSWorkDriveCommon.Util.Functions.<>c__DisplayClass3_0.<ToFunc>b__0() at AWSWorkDriveCommon.Util.RetryStrategy.Call\[R](Func`1 callback, OnRetriesExhaustedThrow retryExceptionType) at AWSWorkDriveClient.Sync.MessageQueueJournal.Create(String queueName, Boolean isCleanStart, RetryStrategy readRetryStrategy) at AWSWorkDriveClient.WorkDriveClient.<>c__DisplayClass25_0.<CreateJournal>b__0() at AmazonWorkDocsDriveFramework.Journal.DedupingJournal..ctor(Int32 maxCacheSize, IFeatureManager featureManager, Func`1 delegateJournalFactory, MetricsReporter metricsReporter, CacheFactory cacheFactory) at AWSWorkDriveClient.WorkDriveClient.CreateJournal(WinClientOptions options, IFeatureManager fm) at AmazonWorkDocsDriveFramework.WorkDriveFramework.Initialize(SystemType systemType, Options options, AppRestartManager appRestartManager, IncidenceLogManager incidenceLogManager, MetricsReporter metricsReporter, INativeOperations nativeOperations, ISystemNotification systemNotification, List`1 customLocalOnlyDeciders, AggregatedAvailabilityTracker availabilityTracker, PeriodicAvailabilityTracker networkAvailabilityTracker, Boolean identifyLocalOnlyFodler, Func`2 databaseProviderFactory, Func`2 mountPointFactory, Func`2 journalFactory, Func`2 providerFactory, Boolean performCreateDeleteEliding, String& mountPoint, ManualSwitchAvailabilityTracker& manualSwitchAvailabilityTracker, UserInfo& userInfo, Optional`1& logUploadClient, IStorageProvider& storageProvider, JournalChangeReferenceManager& journalChangeManager, IReferenceManager`1& refManager, LockManager& lockManager, PathValidator& pathValidator, IResourceNameValidator& resourceNameValidator, IPathConverter& pathConverter, IMetadataManager& metadataManager, IFavoriteDataManager& favoriteDataManager, GarbageCollector& gc, IHardLinkManager& hardLinkManager, IFileRecoverManager& fileRecoverManager, IAsyncFetchFolderManager& fetchFolderManager, IDatabaseProvider& databaseProvider, ICacheManager& cacheManager, IPermissionsManager& permissionsManager, IJournal& journal, Func`1& journalTimerFactory, IJournalReader& journalReader, IFeatureManager& featureManager, ITempFilesManager& tempFilesManager, DriveStatusMonitor& driveStatusMonitor) at AWSWorkDriveClient.WorkDriveClient.CompleteInitialization(WinClientOptions options, AppRestartManager appRestartManager, IncidenceLogManager incidenceLogManager, AutoUpdateSingleton autoUpdate, IWindowsSystemNotification winSystemNotification, IWDObserver`1 systemPopupNotificationObserver, ITaskExecutor executor, Func`1 metricsTimerFactory, String exePath) at AWSWorkDriveClient.WorkDriveClient.<>c__DisplayClass22_0.<run>b__1(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() \[2020-08-11 15:04:23,550]\[thread8]\[ERROR]\[AmazonWorkDocsDriveFramework.Logs.IncidenceLogManagerPIIFree] - === end failure info === \[/code] I've uninstalled WorkDocs and have deleted the folder at: C:\Users\\[user]\AppData\Roaming\Amazon\AWSWorkDocsDriveClient Rebooted, reinstalled workdocs, rebooted again, and then signed in to my WorkDocs account -- to see the same error. I've tried that twice now. I've checked and the MSMQ service is running. I've also killed its PID and restarted the service to see the same WorkDocs error. Help? - Al
2
answers
0
votes
318
views
asked 2 years ago

Workdocs Drive does not install

Environment: - Two Workspaces running in same VPC with Internet access via NAT GW and IGW - AWS Workspace running on Windows Server 2008 R2 Datacenter presenting a Win 7 desktop - AWS Workspace running on Windows Server 2016 presenting a Win 10 desktop - Region us-west-2 - AWS Workdocs Drive installed and working in Win10 Workspace (after roughly 3 hours of tweaking rights and browsers etc -- yeah, I'm complaining) - AWS Workdocs Drive seems to install on the Win 7 Workspace and I get the icon for completing the install, but.... Next step should be to run the Workdocs Drive installer that brings up the login screen for the desired Workdocs instance. Problem: The login screen never appears. Instead.... - Opening on the Workdocs Drive icon as Administrator results in the tray icon showing up with the message "Authenticating User..." - The MS Message Queuing Service is started as are its components, MQAC, RPC, and Windows Event log - The Event log shows the following errors: - The only negative event taking place when the installation starts is a warning that mentions a need to restart. - Informational events state that the installation of the drive was successful -- Since there was no pop-up message displayed I restarted the Workspace instance - Upon restart the Tray Icon still displays the message "Authenticating user" - the Event log shows two Errors from the Source "Amazon Workspaces": -- "Error when trying to start service HighlanderCGH." -- "Line 296. Cannot find any service with service name 'HighlanderCGH'." I'm flummoxed. Any useful actionable advice is welcome. Thanks in advance Abev Edited by: albevier on Jun 22, 2019 10:25 AM
5
answers
0
votes
69
views
asked 3 years ago
  • 1
  • 90 / page