CameraRaw V6.7 in Elements-10 Issue

After updating CameraRaw V6.6 in Elements-10 to CameraRaw V6.7, CameraRaw is missing on the plug-in list and it can't open any NEF files. What to do?

Have your NEF files been transferred directly from camera to computer, or previously opened in Nikon software or another application?
You only need v6.7 if you have recently purchased the Nikon D4, Nikon D800 or Nikon D800E.
The Nikon D3200 is not yet supported in Elements.
N.B. see this link on using older versions of Nikon Transfer.
https://nikoneurope-en.custhelp.com/app/answers/detail/a_id/53027

Similar Messages

Premiere Elements 13 issue with the mouse on When I select a clip of video and move to a different place in my time line, Premiere Elements 13, will not release the clip rom the mouse. The clip follows my mouse movements and goes to other places in my

Premiere Elements 13 issue with the mouse on MAC OSX Yosemite 10.10.1
When I select a clip of video and move to a different place in my time line, Premiere Elements 13, will not release the clip from the mouse.
The clip follows my mouse movements and goes to other places in my time line.
I try to delete these extra insertions, but the mouse will not release the clip.
Action I’ve taken: I’ve re-installed Premiere Elements 13. Problem remains.
This issue has consumed too much of my time and does not go away. It ruins my video.
Help please.
Thanks

I tried using the Guest Account on my Mac. In the Guest Account, Illustrator works perfect!
Then I started wondering what processes (tools/tweaks) I run by default on my account. Turned out the problem was called by a little background tool called RightZoom. RightZoom let's the green 'zoom' button always maximize your current window.
So thanks! Problem solved!

LEAD Codec for MotionJPEG-Premiere Elements Playback Issues

There are several reports online (here and elsewhere) recommending installing LEAD Codec for MotionJPEG-Premiere Elements Playback Issues. Most, if not all, of the feedback is that it works and is only $10 USA dollars.
Today I went in search of that codec at LEAD Technologies and could not find a $10 LEAD Codec.
http://www.leadtools.com/SDK/Multimedia/Multimedia-MCMP-MJPEG-codec.htm
Instead, I found a bunch of kits priced at way over $100.00.
From the chat service at that web site, I discovered that the LEAD codec is no longer sold separately. In order to get that codec, you would have to buy the Multimedia SDF Kit (priced $595.00).
Any workaround suggestions
OR
pay the $595.00 to get the LEAD Codec
OR
go the file conversion route for the MotionJPEG?
ATR

ATR,
Great news!
On the PrPro forum, it's been 100% for MainConcept, and 99% for Morgan. One user could not get the Morgan to work on his/her system, but that could well have been OE on that poster's part. Still, those are not bad odds, and the 'cost" of the Morgan is better...
Just glad that it worked for you.
Good luck,
Hunt

Can I get a phone contact number for Adobe Premire Elements tech issue?

Can I get a phone contact number for Adobe Premire Elements tech issue?

If your issue is about purchasing or downloading or installing a product, then Adobe Support is available via Chat.
If it is about how to use the product to do something then the forums and web and video tutorials are the ways to get your questions answered.

WebI report on SAP Mobile BI for iOS that contains a chart with element linking issue

Hi gurus. I have the following issue:
I have element linking based filters on my chart # 1 to filter values on chart # 2. It worked fine on Ipad. And it worked fine on BI Launch Pad.
But after some time I check my webi report and it stopped working on IPAD.
Filters are not shown on the graph.
However it still works fine on BI LaunchPad
Have you faced this issue before?
Using: BI mobile 5.1.12
Before, example:
After some time, I opened sap mobile and it is not showing up the filter anymore
Now: We upgraded to SAP Bi Mobile 6.0.8.12 but issue persists.
Could you do the test?
Steps to reproduce:
Create a simple Webi report with a table.
Copy that table and paste it to the report.
Turn the original table into a column chart
Add element linking from the chart to table. (When user filters on the chart it should change the table as well)
Test that the element link works in BI LaunchPad.
Save the report to the Mobile category and test on iPad.
Open report on iPad
Tap chart bars. Yellow filters, that are supposed to show up, are not displayed.

Hi Erika,
Is this report element linking defined as 'All Objects' or 'Single Object' in Webi.
I ask this that report element linking on 'All Objects' is not supported yet. This support is expected to come in later releases.
However, if this is single object then it should be working. Can you verify this on latest app store build and confirm. If still it does not work for you, then please raise a support ticket for the same.
Regards,
Ashutosh

PS Elements/Lightroom issues

Hi, Could anyone help me with an issue using Lightroom and PS Elements. When I move from Lightroom to edit in PS Elements, I loose my saved image. It does not show back in Lightroom as everyone tells me it should. I have tho save it somewhere else. Any ideas would be welcome. Thanks Barry from MM

You need to start the round trip from LR as follows and use the save command (Ctrl+S) not save as:
1) Ctrl+E in the Library to export selected image with develop settings (I choose PSD) or right-click and choose Open In PSE
2) Edit in PSE; then Ctrl+S to replace (overwrite) Lightroom export copy
3) Ctrl+W to close in PSE and update Lightroom thumbnail.
On Mac OSX Cmd+E; Cmd+S; Cmd+W
The important point is to overwrite the LR export copy by using File >> Save (Ctlr+S) because if you use “Save As” you create a new document which LR knows nothing about.

Adobe photoshop elements 12 issue

my adobe photoshop elements 12 organizer keeps stopping? anyone know why?

For what it's worth: On my PC running 64-bit Windows 7, I found that PSE 12.0's Organizer simply stopped working (crashed) for no apparent reason from time to time. After updating to PSE 12.1 a few weeks ago, Organizer hasn't crashed a single time. Whether 12.1 addressed stability issues, I have no idea. Perhaps it's just my imagination, but 12.1 does seem to be more stable.

WSDL, custom datatypes, fault element name issues

Hello all,
I am having a LOT of problems with BEAs webservices. I am posting
this here in the hope that someone can help me and tell me what I am
doing incorrectly. I am running
WebLogic Server 7.0 SP1 Mon Sep 9 22:46:58 PDT 2002 206753
WebLogic XMLX Module 7.0 SP1 Mon Sep 9 22:54:41 PDT 2002 206753
Background:
My goal is to make my company's product web services aware. I take an
EJB, try to run it through the standard ant tasks and generate a web
services accessible EJB. Sounds pretty easy, but complex types seem
to make this quite difficult.
I have been able to create a web service accessible EJB (only since
7.0.1), but I am quite unhappy with the quality of what I am able to
produce.
I have a datatype which acts as a key, but it does not follow the
javabeans idiom - i.e. it does not have a default constructor or
accessor methods and I am not in the position to change it. I have
created a codec for this class which works and an xml schema (both by
hand). Its name is AgentKey. I have also had to use the autotyper to
create codecs and typemapping entries for java.util.Properties,
I can connect using the WebLogic classes and I am now trying to
interact using MS Excel and Apache's Axis as my test clients.
Issues:
My first question deals with generating a client. There seem to be
two ways to generate a client. Firstly via the <client> subtask of
<servicegen><service>, the second way via <clientgen> task. Since I
am using a custom data type (AgentKey) I have to manually insert the
AgentKey schema into the web-services.xml file generated by
servicegen. When I try to generate a client via the
servicegen/service/client task there is no opportunity for me to
insert this datatype schema information and I therefore get the
following messages (lots of them, but I'm only including one):
[servicegen] WARNINIG: Unable to find a javaType for the xmlType:['java:net.agentis.apml.runtime']:AgentKey.
Make sure that you have registered this xml type in the type mapping
[servicegen] Using SOAPElement instead
BTW: I am also receiving the same problem with java.util.Properties.
BTW: WARNING is misspelt
If I attempt to generate a client class via the <clientgen> task, I
need to supply either a wsdl or ear file as a parameter. I cannot
supply a wsdl file because I haven't deployed the EAR yet (and I don't
want to until the EAR has the client classes in it), and I can't
supply the EAR because I want the ear to include the client classes.
It is a bit of a catch 22 situation. Is there a solution I can't see?
NOTE: it would be very, very nice if you added a schemaMapping
attribute to the <servicegen/service> task so the web-services.xml
file didn't have to be manually hacked. Something similar to the
typemapping attribute already in the servicegen/service task would do
it.
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?
Another problem with the WSDL (once you have cleansed the multiple
exception messages) is that the fault elements of the
binding/operation elements require names and they don't have any. For
example, this is straight from the deployed EJB WSDL file:
<binding name="ExampleAgentPortSoapBinding" type="tns:ExampleAgentPort">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="serviceWithPrimitiveDatatypes">
<soap:operation soapAction="" style="rpc"/>
<input>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</input>
<output>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</output>
<fault>
<soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</fault>
</operation>
<operation ...
The schema definition at http://schemas.xmlsoap.org/wsdl/ says the
fault element require a name attribute:
<complexType name =" tBindingOperationFault">
<complexContent>
<extension base="wsdl:tExtensibleDocumented">
<attribute name="name" type="NCName" use="required"/>
</extension>
</complexContent>
</complexType>
The name of the fault should be the same name as the fault in the
portType definition. In my example the name is "AgentisException" as
evidenced by this snippet:
<portType name="ExampleAgentPort">
<operation name="serviceWithPrimitiveDatatypes">
<input message="tns:serviceWithPrimitiveDatatypes"/>
<output message="tns:serviceWithPrimitiveDatatypesResponse"/>
<fault name="AgentisException" message="tns:AgentisException"/>
</operation>
Once these changes have been made then the WSDL will validate. Are
there plans to fix these bugs?
On a different note, when I try to interact with a method that uses a
custom data type, such as AgentKey, via the "WebLogic Webservice
standard testing home page" the custom data type without a default
constructor cannot be rendered correctly. For instance, the AgentKey
value is:

<agentKey/>
Since I can't deploy a valid WSDL, I can't get either Axis or Excel to
connect to my web services.
When I attempt to invoke Axis' (beta 1.1) wsdl2java I recieve the
following message.
java.io.IOException: ERROR: Fault is missing a name= attribute in operation
"serviceWithPrimitiveDatatypes", in binding {http://sillyurl.com/reallysilly}ExampleAgentPortSoapBinding.
This seems understandable considering the issues I mentioned earlier.
Unfortunately Excel doesn't really give me anything to go with. If I
type in the WSDL URI then it will give me a list of methods I can
invoke, but if I try to add the service I get the very unhelpful "The
Web Service References Tool could not generate the requested code.
Any changes that were made to your project have been rolled back."
Any help with those two issues would be greatly appreciated also.
One final issue is that I cannot seem to fix is taskdef'ing
<servicegen> properly from Ant. I can do the actual taskdef but then
it cannot find classes from within the weblogic.jar. If I run the
setExamplesEnv.cmd first the I don't need to do the taskdef and
everything works fine. Has anyone else had this issue? (we can't run
that command on our clients desktops before we build our build scripts
- anyway, I've put it down to one of those weird Ant classpath
issues.)
In summary:
Problems I can see and would like some help on are:
- multiple exception messages
- fault operations with no name
- the ability to generate client code with complex data types before
the EAR is deployed.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
I know this has been quite a long email, but it has been months in the
making. Anyone's time would be greatly appreciated.
Mark Mansour
Agentis Software
[email protected]

Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDL seems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late this quarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a look at this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people too.
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the exceptionmessages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty( "weblogic.webservice.servicenamechecking","false" );
This is not a client issue. The WSDL is generating incorrect WSDL. Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey" xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal" xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL it is redefined
every time a method has the AgentisException in its interface (which in my case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed in the upcomingrelease that will be
available for beta testing shortly. Contact [email protected] if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types before
the EAR is deployed.
There is an example to show how to do this: http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
Unfortunately this doesn't solve my problem. I still don't have an EAR or WSDL
file from which I can generate a client to be included in the final EAR file that
gets deployed to the server. My original post explains this a bit better.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50 and others
in this area.
This was more in reference to the building of the web services in the first place
rather than registering custom datatypes at runtime. The manual procedure is
documented at http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to write my own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

Fault element name issues

Back in January I noticed a post concerning generated WSDL files and fault
element not containing a required attribute "name".
I seem to be having the same problem in WLS8.1
Can this be possible since it was fixed in version 7SP2?
After I generate the web service, when I try to generate a JAXRPC client
(via the JavaSoft web services toolkit), it complains that the WSDL file is
invalid because there are <FAULT> elements without name attributes.
Also, I'm having a problem using the clientgen Ant task, its having an error
generating types. This worked 2 days ago when I was running 8.1beta, but
since I upgraded to 8.1 it no longer works.
M
"Bruce Stephens" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDLseems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late thisquarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write
my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a lookat this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people
too.
>>
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the
exception
messages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty(
"weblogic.webservice.servicenamechecking","false" );
>>>
>>
This is not a client issue. The WSDL is generating incorrect WSDL.Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException"xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey"xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal"xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException"xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL itis redefined
every time a method has the AgentisException in its interface (which inmy case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed in
the upcoming
release that will be
available for beta testing shortly. Contact [email protected]
if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types before
the EAR is deployed.There is an example to show how to do this:
http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
>>
Unfortunately this doesn't solve my problem. I still don't have an EARor WSDL
file from which I can generate a client to be included in the final EARfile that
gets deployed to the server. My original post explains this a bitbetter.
>>
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.
Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50
and others
in this area.
This was more in reference to the building of the web services in thefirst place
rather than registering custom datatypes at runtime. The manualprocedure is
documented athttp://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to writemy own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

Please try 8.1 sp1, it is strictly wsdl spec complaint. It generates
<fault> with name.. Clientgen requires fault name to correctly parse wsdl.
thanks,
-Neal
"Mark Fine" <[email protected]> wrote in message
news:[email protected]...
Back in January I noticed a post concerning generated WSDL files and fault
element not containing a required attribute "name".
I seem to be having the same problem in WLS8.1
Can this be possible since it was fixed in version 7SP2?
After I generate the web service, when I try to generate a JAXRPC client
(via the JavaSoft web services toolkit), it complains that the WSDL fileis
invalid because there are <FAULT> elements without name attributes.
Also, I'm having a problem using the clientgen Ant task, its having anerror
generating types. This worked 2 days ago when I was running 8.1beta, but
since I upgraded to 8.1 it no longer works.
M
"Bruce Stephens" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
From your base post:
My next problem deals with the validity of the WSDL. I am seeing that
the WSDL created has exceptions defined multiple times. I saw a
message from Manjo saying that it looked like a bug. I agree and
would like to get a copy of the patch. On a more significant note,
when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDLseems to be the root of most of
your issues.
Concerning the upcoming release, I believe it is scheduled for late thisquarter; contact Michael
([email protected]) for more information.
Also, at the bottom of this post:
I would just like to see an automated way to do this (I've had to write
my own
utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a
look
at this?
http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
Thanks,
Bruce
Mark Mansour wrote:
Hiya Bruce,
I will try and get some time to follow this up with the support people
too.
In response:
Problems I can see and would like some help on are:
- multiple exception messages
In your client code, you can set the following property to avoid the
exception
messages so that the typemapping
registry can be setup.
//dont parse wsdl till we set the typemapping
System.setProperty(
"weblogic.webservice.servicenamechecking","false" );
>
This is not a client issue. The WSDL is generating incorrect WSDL.Here is a
little snippet :
<message name="AgentisException" >
<part name="AgentisException"
xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
<message name="setTraceLevel" >
<part name="agentKey"xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
/>
<part name="intVal"
xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
/>
</message>
<message name="AgentisException" >
<part name="AgentisException"
xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string" />
</message>
As you can see the AgentisException is defined twice (in my real WSDL
it
is redefined
every time a method has the AgentisException in its interface (which
in
my case
is 5 times))
- fault operations with no nameI believe the fault issues that you have raised have been addressed
in
the upcoming
release that will be
available for beta testing shortly. Contact [email protected]
if you
want to participate in the beta.
great. Is there any ETA on the final release date?
- the ability to generate client code with complex data types
before
the EAR is deployed.There is an example to show how to do this:
http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
Unfortunately this doesn't solve my problem. I still don't have an
EAR
or WSDL
file from which I can generate a client to be included in the final
EAR
file that
gets deployed to the server. My original post explains this a bitbetter.
Could the product team add
- a clean way to add in schema datatypes without having to manually
hack the web-services.xml file.Take a look at
http://dev2dev.bea.com/direct/webservice/wswa.html#qz50
and others
in this area.
This was more in reference to the building of the web services in thefirst place
rather than registering custom datatypes at runtime. The manualprocedure is
documented at
http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
I would just like to see an automated way to do this (I've had to
write
my own
utility to do this for me :(
Hope this helps,
Bruce
Thanks Bruce.
Mark

ABAP Container Element Hotspot Issue

Hi Friends
I developed a report using container element and added the HOTSPOT functionality for the field Partner Number.
Partner number have 4, 5 fields like Sold-to-party,ship-to-party, reseller, end user.While executing this report, some time all the fields have value, some times few fields will come with blank value.In that case I need to enter the value for Blank fields.But if I activate HOTSPOT, its not allowing me to enter the value under partner function column.
Kindly give me your suggestion to achieve this functionality.
Thanks
Gowrishankar

Hi Gowrishankar,
Use double click event to handle the same scenario as hotspot, because hotspot are not meant for changing,
also you have a single click event on a row, you just have to pass row, column, sender these three parameters in that event to trigger similar event such as an hotspot. There you can handle editable ALV issues.
Best Regards,
Tapodipta Khan.

Premiere Elements 7 issue with track 1

I just recently switched to premier elements 7. When I first switched it was fine, but now when I bring video into the timeline it always creates new Tracks and will not allow me to put it into Track 1. No idea why this is happening and it's not the end of the world, except when things are put in automatically they are put onto Track 1, and I can't even move my video from Track 2 to Track 1. My computer is Vista home premium. Any help would be appreciated!

Hmm. I see that this is a dual-format cam that will also record in MPEG2.
How are you getting this MPEG into your computer? Are you using Premiere Elements' Media Downloader to pull it off your hard drive?
Also, for this video you should be using the project preset for hard drive or DVD camcorders.
I'm not an expert on these dual-format camcorders, so there could be an issue with it using 5.1 audio, if it is for those MPEG. That could lead to the problems you're describing.

Printing from Elements 10 issues question:

If I print anything from my Elements 10 on our HP Officejet 8600 the printer goes birserk and will only print the odd page. After attempting to line feed numerous times, the printer comes up with "Out of Paper" however the printer has plenty of paper. This does not occur with the HP 8600 printing from Excel, Word or Explorer.
It was not that long ago we updated the printer driver. The earlier driver palyed up even more ! Seems to be an incompatibility between Elements 10 and certain HP printer drivers. Is there a patch from Adobe that will resolve this ? It appears to be the signal Elements sends to the printer to line feed between each page.
Look forward to areply ASAP.

Brad1313 where you able to resolve this? I have multiple xerox workcentre 7556 printers that we print from osx 10.7 through a 2008 r2 print server. before the print job is even released at the mac, a "Printer control command" gets stuck in the local queue and never makes it to the 2008 queue. If i delete the printer control command job at the mac, the actual print job is released and prints through the server to the printer correctly. Account codes are also in use with this machine, but this doesnt seem to be the issue... its the Printer control command that seems to be getting things stuck.... If I print directly to the printer using lpd i have no issue, the pcc file doesnt get stuck (i paused the queue to verify the pcc file is still being created, and it still is). Unfortunatley this is against company policy, all jobs must go through the server queue. osx 10.6.8 has no issue and im using the updated driver for the printer. Just curious if you found a work around. Thanks!

Elements Activation Issue

My daughter has Adobe Photoshop Elements 8, PN: 65045174. About a year ago, we installed the software on 2 desktop machines in our home, mainly for my daughters' school use. One of the systems was too slow to run it properly, so we uninstalled it. The other system crashed and we had to reformat the hard drive. We lost everything and never reinstalled Elements. 5 months ago we purchased a new laptop for my daughter to take to college and we installed Elements on it; this is now the only computer where we have Elements installed. The problem is; she keeps getting an error message saying you will not allow her to use it because it is installed on 2 other machines. When she clicks on "I have already deactivated this serial number from one of my other machines, and I am ready for Adobe to validate this." it just takes her back to the original error screen. We can't "deactivate" it, because it's not on the other systems to being with. I thought about trying to reinstall it on my desktop system and then deactivate it, but that may create yet another issue. What do you suggest? We have Elements on only one machine and aren't able use it.
Please advise.
Thanks for your help.

lwdykes for the best assistance, I recommend our chat support at http://adobe.ly/v6wfLL. Our chat representatives can provide a personalized experience to resolve the issue you have described.

PS Elements activation issue (not recognising this laptop)

My copy of Photoshop Elements 9 is installed in my laptop and my partner's. It has rarely been used on hers but she tried to open it and it is saying it can't be activated as the serial number is already in use on two machines. This IS one of the machines it is activated on. It is telling me to deactivate it elsewhere but the only other place it has been installed is my laptop. Does anyone have any ideas why this is happening? I am positive it has not been installed elsewhere so should not be having this problem.

Our support team can investigate your difficulties with the activation. For the best assistance, I recommend our chat support at http://adobe.ly/yxj0t6. Our chat representatives can provide a personalized experience to resolve the issue you have described.

Premiere elements 9 issue with m4v

i have a sony cybershot h55 and it shoots in m4v.
everytime i put my videos into premiere elements it gets spots where it goes black or white and pixely & it ruins the frame for a few seconds on and off
this isnt a trial version; i got the program straight from adobe. ive updated everything but it hasnt fixed my issue.
i have a windows vista sp2, if it helps.
anyone know why this is happening or how i can stop this? its soooo frustrating!

Premiere Elements will likely not be able to edit that video.
But you can increase the odds that it will be able to by:
1) Ensuring you have the latest version of Quicktime installed, per the program requirements.
2) Installing the software that came with the camera. (It may install some necessary codecs.)
3) Ensuring that your Premiere Elements project is properly set up. Your setup could activate necessary components for you to be able to work with this video format.
It's hard to say which settings to select for your camera, since the camera shoots in both 1280x720 and 640x480 format. But most likely the settings you will need are listed as one of the DSLR options. Did you choose one of these when you started your project?
Did you use Premiere Elements' Get Media/Video Importer to get the video from your camcorder into yoru computer?
The biggest challenge is that, unlike DSLRs, the video from these consumer-style still cameras often uses the MJPEG codec, which can be challenging for videos to work with. I don't know if that camera shoots in MOV or AVI format, but knowing that could help us figure out how to convert the video to an editable format if the existing project settings dont' seem to work.
BTW, are you sure your camera produces m4v files? That's generally a file format that's only used for iTunes video.

CameraRaw V6.7 in Elements-10 Issue

Similar Messages

Maybe you are looking for