- Adobe Enterprise & Teams: Panduan pentadbiran
- Rancang pemasangan anda
- Konsep asas
- Panduan Pemasangan
- Pasangkan Creative Cloud untuk pendidikan
- Laman utama Penerapan
- Bestari Penyesuaian Tugas K-12
- Persediaan mudah
- Menyegerakkan Pengguna
- Penyegerakan Senarai K-12 (AS)
- Konsep pelesenan utama
- Pilihan penerapan
- Petua cepat
- Luluskan aplikasi Adobe dalam Google Admin Console
- Dayakan Adobe Express dalam Google Classroom
- Penyepaduan dengan Canvas LMS
- Penyepaduan dengan Blackboard Learn
- Mengkonfigurasikan SSO untuk District Portal dan LMS
- Tambahkan pengguna melalui Roster Sync
- Soalan Lazim Kivuto
- Garis panduan kelayakan institusi Utama dan Sekunder
- Sediakan organisasi anda
- Jenis identiti | Gambaran keseluruhan
- Sediakan identiti | Gambaran keseluruhan
- Sediakan organisasi dengan Enterprise ID
- Sediakan Azure AD federation dan segerakkan
- Sediakan Google Federation dan segerakkan
- Sediakan organisasi dengan Microsoft ADFS
- Sediakan organisasi untuk District Portal dan LMS
- Sediakan organisasi dengan penyedia Identiti lain
- Soalan lazim dan penyelesaian masalah SSO
- Sediakan Frame.io untuk perusahaan
- Urus persediaan organisasi anda
- Urus domain dan direktori sedia ada
- Dayakan penciptaan akaun automatik
- Penguatkuasaan Domain untuk pengesahan terhad
- Sediakan organisasi melalui amanah direktori
- Berhijrah kepada penyedia pengesahan baharu
- Tetapan aset
- Tetapan pengesahan
- Hubungan privasi dan keselamatan
- Tetapan konsol
- Urus penyulitan
- Urus domain dan direktori sedia ada
- Urus pengguna
- Gambaran Keseluruhan
- Mengurus peranan pentadbiran
- Urus peranan pengguna
- Strategi pengurusan pengguna
- Berikan lesen kepada pengguna Pasukan
- Pengurusan pengguna dalam apl untuk pasukan
- Tambahkan pengguna dengan domain e-mel yang sepadan
- Tukar jenis identiti pengguna
- Urus kumpulan pengguna
- Urus pengguna direktori
- Urus senarai pengecualian untuk penguatkuasaan domain
- Urus pembangun
- Hijrahkan pengguna sedia ada ke Adobe Admin Console
- Hijrahkan pengurusan pengguna ke Adobe Admin Console
- Gambaran Keseluruhan
- Urus produk dan kelayakan
- Urus produk dan profil produk
- Urus produk
- Beli produk dan lesen
- Urus profil produk untuk pengguna perusahaan
- Urus peraturan pemberian automatik
- Beri hak kepada pengguna untuk melatih model tersuai Firefly
- Semak permintaan produk
- Urus dasar layan diri
- Urus penyepaduan aplikasi
- Urus kebenaran produk dalam Admin Console
- Dayakan/lumpuhkan perkhidmatan untuk profil produk
- Aplikasi Tunggal | Creative Cloud untuk perusahaan
- Perkhidmatan pilihan
- Urus lesen Peranti yang Dikongsi
- Urus produk dan profil produk
- Bermula dengan Global Admin Console
- Amalkan pentadbiran global
- Pilih organisasi anda
- Urus hierarki organisasi
- Urus profil produk
- Urus pentadbir
- Urus kumpulan pengguna
- Cipta laporan penetapan lesen
- Kemas kini dasar organisasi
- Urus templat dasar
- Peruntukkan produk kepada organisasi anak
- Laksanakan kerja yang belum selesai
- Muat turun log audit dan eksport laporan
- Eksport atau import struktur organisasi
- Urus storan dan aset
- Storan
- Urus projek
- Penghijrahan Aset
- Tuntut semula aset daripada pengguna
- Penghijrahan aset pelajar | EDU sahaja
- Urus perkhidmatan
- Adobe Stock
- Fon tersuai
- Pautan Aset Adobe
- Adobe Acrobat Sign
- Creative Cloud untuk perusahaan - keahlian percuma
- Pasangkan aplikasi dan kemas kini
- Gambaran Keseluruhan
- Cipta pakej
- Pakej aplikasi melalui Admin Console
- Cipta Pakej Pelesenan Pengguna Bernama
- Urus pakej yang dijana terlebih dahulu
- Urus pakej
- Urus lesen peranti
- Pelesenan nombor siri
- Sesuaikan pakej
- Pasangkan Pakej
- Urus kemas kini
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Selesaikan masalah
- Urus akaun Pasukan anda
- Pembaharuan
- Urus kontrak
- Laporan & log
- Dapatkan bantuan
How to troubleshoot the internal server setup and solve maintenance issues.
Adobe Update Server Setup Tool (AUSST) enables you to centralize the download of Adobe apps and updates to a single server location.
You may check for the error logs or error codes to find the error reported during a server setup or while downloading the updates.
Also check the given troubleshooting tips if you face problems in deploying apps and updates through internal update server.
Error logs
Errors, warnings, and troubleshooting information are recorded in the log files.
The following log files are located in the %temp% folder in Windows and in the ~/Library/Logs in macOS:
- AdobeUpdateServerSetupTool.log
- AdobeAcrobatUpdateServerSetupTool.log
DLM.log is located in the following locations:
- Windows:
- %Temp%\CreativeCloud\ACC\AdobeDownload
- %Temp%\AdobeDownload\
- Mac:
- ~/Library/Logs/CreativeCloud/ACC/AdobeDownload
- ~/Library/Logs/AdobeDownload/
Error codes
The following error codes may be reported if the internal update server is unsuccessful.
|
Error Code |
Error Message |
|
2 |
Internal error occurred |
|
3 |
Could not access specified path |
|
4 |
Network failure |
|
5 |
Server unresponsive |
|
6 |
Proxy authentication failed |
|
7 |
Output disk full |
|
8 |
Write permission denied |
|
9 |
File not found on server |
Basic troubleshooting
If the web server that is used to distribute the apps and updates is not set up correctly, apps and updates might get downloaded from the Adobe update server (Adobe Update Server Setup Tool does that automatically), but will not be distributed to the clients.
To test that the web server is running correctly, see Verify your internal update server.
Ensure that there are no problems related to network connectivity and that the internal update server can connect to the Adobe update server.
For example, check that you can access the default welcome page of the internal update server.
End users see the following error if the Creative Cloud Desktop App is unable to connect to your internal update server (AUSST):
Troubleshoot the internal update server setup and sync issues
When you run the AdobeUpdateServerSetupTool command, ensure that there are no spaces in the following cases:
- Between parameters and the = sign
- Between the = sign and arguments
For example, the following command has an incorrect extra space between --root and the = sign
- Anywhere in a path.
For example, the following command has an extra space between the quotation mark (") and the forward slash (/)
The URLs for the server should include the protocol (such as http://). If the port number is different from the default value of 80, the port number should also be specified.
For example, the following section in the AdobeUpdater.Overrides file is incorrect because it does not specify the http:// protocol:
<URL>/Adobe/CS/webfeed/oobe/aam20/win/</URL>
<Port>1234</Port>
Note that in this example, the port number (1234) has been specified, which is required if the port number does not have the default value of 80.
Ensure that the location on the server where the apps and updates are to be stored has the correct write permission. Otherwise, apps and updates might not be synced/downloaded on the internal update server. The server setup process is not complete unless all apps and updates are synced/downloaded on the internal update server.
Check that the paths provided to all the command-line options are absolute paths. AUSST does not support relative paths.
Troubleshoot the setup of clients
The client configuration files are generated at a location determined by the --genclientconf parameter of the AdobeUpdateServerSetupTool command. For more details, see Generating client configuration files. Two files are generated, one each for Windows and macOS clients. Check that the files are available in the respective locations on the internal update server.
After the client configuration files are generated on the internal update server, they are deployed on each end-user computer. The files are different for the Windows and the macOS platforms.
The location for the file on each end-user computer is platform-specific. Ensure that the configuration files are deployed on the end-user computers at the locations. For more details, see Deploying client configuration files.
Use fresh sync to troubleshoot
In exceptional cases, multiple apps/updates of the same package might get stored on the internal update server if the option of incremental update sync is specified. These will then be deployed to the end-user computers, and the users will see multiple copies of the packages on their computers. If this happens, perform the fresh update sync (one time) by running the following command:
AdobeUpdateServerSetupTool --root="<update folder>" --fresh
This ensures that the correct single copy of the packages get downloaded to your internal update server, from where they are deployed to the end-user computers.
If you are using the incremental sync option and continue to get errors even after trying all the previous steps, perform fresh update sync (one time) by running the following command:
AdobeUpdateServerSetupTool --root="<update folder>" --fresh
This will ensure that all updates from the Adobe update server are downloaded to your internal update server.
