Compressor unable to submit to queue

hi there, i was using compressor3.0.3 and everything worked fine then a message would come up when i submit a project saying " unable to submit to queue. please restart or verify compressor install is correct". i spoke with a mac person that had me trash my prefs then open a new user. it worked at first then i got the same message. i uninstalled fcp then reinstalled but it is still the same. can anyone help??? thank you

I had the same issue on a couple of machines, the common denominator seems to be a character that is not a valid network address character i.e. "&". I removed it from four locations I am not sure which is actually important. Here are the 4 locations: 1. Sharing preference option "Computer Name" 2. Sharing preference then in "Edit..." option "Hostname" 3. Apple Qmaster preference Setup pane option "Identify this QuickCluster as:" 4. Apple Qmaster preference Advanced pane option "Identify this computer to Qadministrator as:".

Similar Messages

Compressor 3.05 "unable to submit to queue" after upgrade to Mountain Lion

I have successfully compressed 1500 videos using Compressor 3.05 while running OS X10.5 (Leopard). I just upgraded to 10.8.3 (Mountain Lion) and the first batch I sent to Compressor had destination issues that I fixed (I think). I'm not getting any more exclamation marks but now it drops down the error message "Unable to Submit to Queue - please restart your computer or verify your Compressor installation is correct." I have restarted, of course. I have no idea how to verify the installation is correct. We did migrate all the files to a new boot drive, but FCP 6.0.6 and all other programs are working well.

Perhaps Compressor installed correctly but Qmaster didn't. You could try running Compressor Repair (check the trash preferences box) and see whether that changes anything. Also repairing permissions after installing is always a good idea,
FWIW, I've been skeptical about the reliability of using Migration Assistant on pro apps – although I know there are a lot of hurdles to get over if installing FCS 2 on either Lion or ML and can understand why. I hope that someone who has actually installed FCS2 on either of those OS versions will chime in with suggestions based on their experience. Have you tried getting the Rosetta installer to install on ML so you can use the FCS disks?
Russ

Compressor 4.2 Unable to submit to queue

I am having trouble with Compressor 4.2, "Unable to submit to queue, Please restart your computer or verify your Compressor installation is correct."
I am not able to compress anything from Compressor 4.2, but I am able to use all the Compressor preset including that one that I create in Compressor from FCP X.
I have repairer Compressor with Digital Rebellion,
I have delete Compressor with FCS Remover from Digital Rebellion,
I have remove the Compressor folder in Library Application Support,
If I open Apple Qmaster there is a massage "Apple Qmaster cannot be opened because of a problem.
I have also remove Apple Qmaster.
I don't know what else to do.
Any help would be appreciated.
Ricky

Im surprised that trading trashing the Compressor folder wasn't the cure.
Try moving Qmaster to the trash (you don;t have to empty it).
Any luck?
Russ

Compressor-Unable to submit queue-Any solutions yet?

Below is a common problem with compressor I am now experiencing. In the past and on the web there are many many references to this problem with no simple solution. Has any one heard of any new fixes for this problem?, or just anything that works to fix it. I would like to use compressor again,
Compressor-Unable to submit queue
Please restart your computer or verify your Compressor installation is correct.
I did ugrade to dual core intel mac pro recently
mac pro OSX 10.6.8

You tried all of the troubleshooting tips posted by Michael Grenadier?
Russ

Getting "Unable to submit to queue" message

I'm trying to run a .mov file through Compressor 3.0.5 to shrink the audio track using a Dolby Digital Pro 2.0 setting. I load the necessary file, destination, and settings info into the job, but when I hit "Submit," I keep getting a dialog box that says "Unable to submit to queue. Please restart or verify that your installation is correct."
Well, restarting hasn't helped. Neither has trying some different settings, to see if the problem is just associated with one configuration. I don't use Compressor often, but the last time I tried this routine - quite a while ago -- I believe it proceeded without a hitch. All my other FCS apps - Final Cut and Motion, at least -- have been working fine.
Any suggestions on how to break through this submission barrier? I've got a DVD project that needs to be delivered in 24 hours. Thanks.

There may be an issue with the installation of Compressor.
Digital Rebellion also has FCS remover which can assist with properly removing Compressor from your system. You can then reinstall from your discs.
Due to the shared elements in FCS you will need to feed a large part of the discs to complete the reinstall. You may just want to consider uninstalling all and then reinstalling all of FCS.
Digital Rebellion also has a preference manager that can save preferences for FC, DSP, etc. You get to choose what you would like to save.

Compressor Unable to Submit

This problem has been posted about before . . . I I have not been able to find a solution that works for me.
Since "upgrading" FCS2 Compressor has been broken and has produced nothing but "unable to Submit to queue." I have followed all the instructions in the "Compressor: Troubleshooting basics" to do a remove and reinstall and then upgraded. It did not help.
I also cannot start Qmaster sharing because "qmasterd is not running." which I assume is the underlying problem.
Anyone solved these problems?

For the record, I finally got Compressor to work . . . after the second time reinstalling it. What I did was:
1) Delete the previous installation per the instructions on Apple's Compressor troubleshooting page.
2) Reinstall FCS2 from the upgrade disk (deselecting the install content options to save time)
3) Install the Qmaster that's included on the FSC2 Upgrade disk in the extras folder.
4) Upgrade FCS2 via Software Update.
5) Started sharing from the Qmaster preference pane in System Preferences.
The key, I think, was compeleting these steps before attempting to run Compressor. Previously I had tested Compressor before doing the updates.

Simple Solution to "Unable to submit to queue..." Problem

This may not work for everybody -- configurations are so different
Did a clean install of the OS, reinstalled FCS2 (all parts), but still got the "Unable to submit to queue..." message. While I was looking at the Compressor screen with that frustrating message, I clicked on the Batch Monitor button.
Up came the Batch Monitor screen saying "No cluster" in the left side column and "No cluster" in the right side column. Then I went to the Batch Monitor User Manual under the Help menu. On page two, I found this wording accompanying the "Cluster List" section: "Displays a list computers (sic) available for processing batches, including 'This computer' (the one running Batch Monitor) and all enabled Apple Qmaster processing clusters..."
Well, "This computer" did not show up in either of the columns -- both showed "No cluster."
I called Tech Support to see if this could be at the bottom of my "Unable to submit to queue..." problem.
The helpful staffer told me to go to the System Preferences panel and check the "Computer Name" under the "Sharing" settings. There was no computer name. Since I am the only person using the G5, I never saw a need to name it.
I put in a name and rebooted. Problem gone! Compressor works fine after all these months of frustration and doing clean installs, etc.
Hope this works for some of you, too.

Hello David,
I cannot agree with you I am afraid. iChat works fine for me on 10.4.3. I am sure it works fine for many others too. There are some set up issues, they seem to get resolved pretty quickly in here.
Not a criticism as such David - But suggesting that the best fix is a retro grade one is perhaps not the best resolution to a problem.
I am not saying I can fix your problem - there are many here better than me at sorting out problems ( I won't name names but they know who they are! ) :-)))
Why not post back with some more information about the problem. The set up there. Any error messages you get.... I'll bet you a Pound of Apples and a large Pineapple that some one can get you chatting happily on 10.4.3.
Now theres a challenge!!!
Best regards
Ian

Compressor unable to submit Batch

I have compressor 3.0.2 and no matter what i do i can't get it to submit a batch. I drag the desired .avi clip into the batch window. I set the proper codec settings and assign a destination to it. When i hit Submit the job goes to batch monitor and shows it however no matter how much time i give the computer i can't get it to process and encode the video. (I have tried with a few different codecs already) What am i doing wrong? It has taken me days just to get compressor to open and show the batch window and now i am facing this problem. Any input would be greatly appreciated.

HI Guys a few things you can try for COMPRESSOR and QMASTER..
• stop compressor and qmaster
• remove or purge the compressor plist files as documented in post http://discussions.apple.com/message.jspa?messageID=6803728#6803728
• purge/delete all the files in /var/spool/qmaster (or where ever you defined the cluster metadata file in system prefs/qmaster)
• start up qmaster in the prefs (use option+start to reset) on all nodes
• set up your cluster
• make sure all target, source and cluster file systems (mount them via finder) on the subnet you're using) are available on all the service nodes (NFS is easy)..
• on error: make sure you have defined the cluster correctly using Apple QMASTER ADMINISTRATOR.
• review he /var/logs/qmaster & compressor via console.app.. see of there is any diag message in there that may indicate your issue.
if all is well, submit your job .. should be ok...
post your results.
w

Export problem - "Unable to submit to que....."

For some reason Compressor is now saying "Unable to submit to que, please restart your computer and check to see if your installation is correct." when I hit submit.
I have been using FC Studio (including compressor) for over a year with no problems. I tried restarting the computer and resetting the background processing, still getting the same error when I hit "submit".
Any idea what's wrong?
(OS X 10.5.7, compressor 3.0.5)

This topic comes up quite a lot.
You can access some of the threads for various solutions here:-
http://discussions.apple.com/search.jspa?search=Go&q=Unableto+submit+toqueue

Firefox crashed when I restarted it to install plugins and the crash reporter is unable to submit a report for this crash. How can I submit this report?

# This file is in the UTF-8 encoding
[Strings]
# LOCALIZATION NOTE (isRTL):
# Leave this entry empty unless your language requires right-to-left layout,
# for example like Arabic, Hebrew, Persian. If your language needs RTL, please
# use the untranslated English word "yes" as value
isRTL=
CrashReporterTitle=Crash Reporter
# LOCALIZATION NOTE (CrashReporterVendorTitle): %s is replaced with the vendor name. (i.e. "Mozilla")
CrashReporterVendorTitle=%s Crash Reporter
# LOCALIZATION NOTE (CrashReporterErrorText): %s is replaced with another string containing detailed information.
CrashReporterErrorText=The application had a problem and crashed.\n\nUnfortunately the crash reporter is unable to submit a report for this crash.\n\nDetails: %s
# LOCALIZATION NOTE (CrashReporterProductErrorText2): The first %s is replaced with the product name (i.e. "Firefox"), the second is replaced with another string containing detailed information. These two substitutions can not be reordered!
CrashReporterProductErrorText2=%s had a problem and crashed.\n\nUnfortunately the crash reporter is unable to submit a crash report.\n\nDetails: %s
CrashReporterSorry=We're Sorry
# LOCALIZATION NOTE (CrashReporterDescriptionText2): The %s is replaced with the product name.
CrashReporterDescriptionText2=%s had a problem and crashed.\n\nTo help us diagnose and fix the problem, you can send us a crash report.
CrashReporterDefault=This application is run after a crash to report the problem to the application vendor. It should not be run directly.
Details=Details…
ViewReportTitle=Report Contents
CommentGrayText=Add a comment (comments are publicly visible)
ExtraReportInfo=This report also contains technical information about the state of the application when it crashed.
# LOCALIZATION NOTE (CheckSendReport): The %s is replaced with the vendor name.
CheckSendReport=Tell %s about this crash so they can fix it
CheckIncludeURL=Include the address of the page I was on
CheckSendEmail=Email me when more information is available
EmailGrayText=Enter your email address here
ReportPreSubmit2=Your crash report will be submitted before you quit or restart.
ReportDuringSubmit2=Submitting your report…
ReportSubmitSuccess=Report submitted successfully!
ReportSubmitFailed=There was a problem submitting your report.
ReportResubmit=Resending reports that previously failed to send…
# LOCALIZATION NOTE (Quit2): The %s is replaced with the product name.
Quit2=Quit %s
# LOCALIZATION NOTE (Restart): The %s is replaced with the product name.
Restart=Restart %s
Ok=OK
Close=Close
# LOCALIZATION NOTE (CrashID): The %s is replaced with the Crash ID from the server, which is a string like abc12345-6789-0abc-def1-23456abcdef1
CrashID=Crash ID: %s
# LOCALIZATION NOTE (CrashDetailsURL): The %s is replaced with a URL that the user can visit to view the crash details.
CrashDetailsURL=You can view details of this crash at %s
ErrorBadArguments=The application passed an invalid argument.
ErrorExtraFileExists=The application didn't leave an application data file.
ErrorExtraFileRead=Couldn't read the application data file.
ErrorExtraFileMove=Couldn't move application data file.
ErrorDumpFileExists=The application did not leave a crash dump file.
ErrorDumpFileMove=Couldn't move crash dump.
ErrorNoProductName=The application did not identify itself.
ErrorNoServerURL=The application did not specify a crash reporting server.
ErrorNoSettingsPath=Couldn't find the crash reporter's settings.
ErrorCreateDumpDir=Couldn't create pending dump directory.
# LOCALIZATION NOTE (ErrorEndOfLife): The %s is replaced with the product name.
ErrorEndOfLife=The version of %s you are using is no longer supported. Crash reports are no longer being accepted for this version. Please consider upgrading to a supported version.

I think you may have pasted the wrong thing into the Description.
To try and resubmit a pending report (for example if you lost your internet connection):
#Go to about:crashes in the location bar
#Click the latest report link to resubmit it
If there isn't a pending crash report listed, I'm afraid you may be out of luck for that crash report.

Unable to create a QUEUE in custom schema

Hi,
I was able to create a Type & queue table in custom schema, but using them was unable to create a QUEUE in custom schema
I'm using the following piece
DBMS_AQADM.CREATE_QUEUE(queue_name => 'XXXXXX_QUEUE',
queue_table => 'XXXXXX_QUEUE_TABLE'
Whereas in APPS schema I'm able to create the same queue.
Pls advice ...

Hi,
The only reason is that, we create all the custom objects (owner as custom schema), and a synonym in APPS.
I did not get any error, but the queue, is not getting created
Following are the scripts used
CREATE OR REPLACE TYPE 'XXXXXX_QUEUE_TYPE
AS OBJECT (TYPE VARCHAR2(15));
BEGIN
DBMS_AQADM.CREATE_QUEUE_TABLE (queue_table => 'XXXXXX_QUEUE_TABLE',
queue_payload_type => 'XXXXXX_QUEUE_TYPE'
END;
BEGIN
DBMS_AQADM.CREATE_QUEUE(queue_name => 'XXXXXX_QUEUE',
queue_table => 'XXXXXX_QUEUE_TABLE'
END;
BEGIN
DBMS_AQADM.START_QUEUE(queue_name => 'XXXXXX_QUEUE'
END;
Thanks.....

Custom Measure - Unable to Submit Data Using Input Schedule

We have an application that requires storage of data on a job-to-date basis. To accommodate this, the application was changed to a YTD application and 3 custom measures were added:
JTD (base data)
YTD_JOBS (offsets current period against last month of prior period)
PERIODIC_JOBS (offsets current period against prior period)
Everything is working and the measures resolve to the correct values. The system also completes logic (advanced and dimension) properly. Data may also be submitted through an Import process.
However, we are unable to submit data using an input schedule. We consistently get a "no data to refresh" error message. When the same schedule is used in the older, periodic version of the application, the submission works as expected.
I suspect the problem is the naming of the custom measures is the root cause. I have been unable to find documentation (BPC 5.1M) related to custom measures for 5.1. Any help resolving this issue and/or tracking down custom measures documentation for v5.1 is much appreciated.
Cheers,
Jeff

Joost,
I believe what you are describing is the root of the issue. The application is set to YTD as the data input type both in the web admin section and in the database table. The problem is that JTD is the input member for this application -- we are loading job-to-date values instead of year-to-date.
It seems that BPC does not understand JTD as a "base level" measure fort the input method. I have not been able to find a table in the database that defines PERIODIC and YTD. My hope was to add JTD to the settings.
Unless someone else has made something like this work, I suspect that I'll have to use YTD as the ID of the base member and restructure the custom measures. We did not start this way since the user community thinks in terms of JTD data.

Compressor 3.5 "Submit" button inactive

Hi Everyone,
The Compressor (3.5version) "Submit" button is inactive when I try to compress an external .mov file or a file from the timeline. I recently installed Final Cut Studio 3 (FCP 7) keeping the 6 version as well. When I try to use old Compressor (3.0.5) it quits.
Do you think that keeping both versions is what is causing the problem?
I have Mac Book Pro, 10.6.8
2.4 GHz Core 2 Duo

Sounds like Compressor and Qmaster aren't talking to each other.
In the menu toolbar, Compressor>Reset Background Processing. Close C 3.5, relaunch and try submit again.
If that doesn't fix things, run DIgital Rebellion's Compressor Repair; make sure that the Trash Preferences box is checked.
Russ

Wireless keyboard will not pair with computer. Unable to submit password.

My wireless keyboard will not pair with the computer. Now I am unable to submit the password in order to access the computer.

What version of the Mac OS are you running (from "About this Mac" under your Apple menu)?

Compressor fails to Submit to Batch

Hi - despite removing/re-installing Compressor as diected by Apple, Compressor will not submit anything to Batch. Hosing out prefs, rebooting, etc. to no avail. Program is DOA.
Works fine on the G5. The G4, no dice.
Any thoughts on this are welcome. Thank you.
G2 Dual 1.42/G5 Dual 2.3 Mac OS X (10.4.8)

I have the EXACT problem happening and I'm on a MacBook Pro. I get both the Qmaster and Compressor errors exactly as mentioned above^. I think it is a problem with Qmaster, the computer's sharing prefs, or something else. Qadmin used to list "Eisen Feuer's Computer" alongside "VideoG5" (the other computer, networked to this) but now it only lists VideoG5, which I can run Compressor on with no problem (well, one problem- it's 3 times slower than my MBP and I like to be mobile instead of chained to the office, read: G5)
I set up a cluster in Qadmin with only the G5 in the cluster and I'm able to send jobs to the Batch monitor for the G5 to process. "Eisen Feuer's Computer" fails to blip on the Qadmin radar.
Hope it helps people to resurrect this topic- I sure need it (YES I followed Apple's instructions to the letter)
Right now it's pretty sad- I'm using rooVid lite to do batch compressions rather than the program I paid $400 for D:

Compressor unable to submit to queue

Similar Messages

Maybe you are looking for