E-mailed File "The project is not compatible with the current version of Premiere Elements"

I have Version 12 on a PC.
My friend has Version 12 on a MAC.
E-mailed him a file.
He could not open, and a message box popped up: "The project is not compatible with the current version of Premiere Elements".
Could someone kindly asssit, this does not make sense as to why it is not opening, since both computers are using the same version.
Thank you,
Ben
[email protected]

Ben
As said, you cannot open a Premiere Elements 12 Windows project file (named project.prel) in Premiere Elements 12 Mac. And vice versa.
Details
Given that your source is imported into a Premiere Elements 12 Windows project and placed on its Timeline for edit. That Timeline content cannot get out of the program without export. Export choices are found in the Publish+Share section of the program.
In your case, you want to take the Timeline content of Premiere Elements 12 Windows and export it to a format with which Premiere Elements 12 Mac supports (look at .mov or .mp4). In this regard, in Premiere Elements 12 Windows look at Publish+Share/Computer/AVCHD and one of its .mp4 presets or Publish+Share/Computer/QuickTime and one of its .mov presets (suggested H.264 video codec).
Those exports will be saved to the computer hard drive of the Windows computer. Then email the .mov or .mp4 file (beforehand, check the
email carrier's specification for that). Depending on the circumstances, you could transfer the file to a USB Flash Drive for the sharing.
Remember, sharing the .mov and .mp4 involves "whole" video. Depending on the edits, the video may need to be cut by the receipent. You are not dealing with the project file. The story would be different if this sharing and editing is done from Premiere Elements Windows to Premiere Elements Windows. And, if that were the case, then you would have to assure that the source media of the project traveled with the project file. (See Project Archiver feature of the program.)
That is a rough sketch of the situation. I can fine tune the details further if necessary.
Please review and consider.
Thanks.
ATR

Similar Messages

I bought a new imac running Loin and Office 2011. The server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software.

I bought a new imac running Loin with Office 2011. I am the only mac in the office and the Server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software other than webmail access through our website. It looks as though 2011 is not compatible with 2003 per some searches online, but what are some options I have to gain full access again? I purchased parallels in hopes that this my help and I am able to use remote desktop connection to log on to server but can not drag and drop files I need. There is a shared drive on that Server we all use to exchange files.
The two main issues are gaining access to my email again and ability to drag and drop files from mac to pc. I hope this is enough info to get some solutions.
PS - IT person says my iMac's IP is what his server does not understand so that is why I can not login.

Office 2011 is not compatbile with Exchange 2003.
I suggest you post further Office related questions on Microsoft's own forums for their Mac software:
http://answers.microsoft.com/en-us/mac

Error :"The provider is not compatible with the version of Oracle client"

Hi guys!
I'm facing this problem:
When my .Net application tries to access the DB, I get this error message above.
The application is into the same machine of DB and the operational system is Windows Server Enterprise 64 bits.
I'm comparing to another machine that has the same scenario but runs in Windows Vista 64 bits. This problem doesn't happen and I can normally access the DB.
The both database versions are 10g Release 2 (10.2) and all components from Oracle Database Components 10.2.0.2.21 are installed as the containing bellow:
-Oracle Data Provider for .NET 1.x 10.2.0.2.20
-Oracle Data Provider for .NET 2.0 10.2.0.2.20
-Oracle Developer Tools for Visual Studio .NET 2003 10.2.0.2.20
-Oracle Developer Tools for Visual Studio 2005 10.2.0.2.20
-Oracle Provider for OLE DB 10.2.0.2.20
-Oracle Objects for OLE 10.2.0.2.20
-Oracle Services For Microsoft Transaction Server 10.2.0.1.0
-Oracle Net 10.2.0.1.0
-Oracle Universal Installer 10.2.0.2.0
Oracle.DataAcces.DLL is 2.102.2.20 and it is reference in my .Net app (that is published and located into IIS).
These are the Oracle assemblies installes in 'C:\Windows\Assembly':
Windows Vista Machine:
ASSEMBLY NAME VERSION CULTURE PUBLIC KEY TOKEN PROCESS ARCHITECTURE
Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 pt-BR 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 it 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 fr 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 es 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 de 89b483f429c47342
Oracle.Management.Omo 2.102.2.20 Neutral 89b483f429c47342 x86
Oracle.VsDevTools 2.102.2.20 Neutral 89b483f429c47342 x86
Policy.10.1.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Policy.10.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Windows Server Machine:
ASSEMBLY NAME VERSION CULTURE PUBLIC KEY TOKEN PROCESS ARCHITECTURE
Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Oracle.DataAccess 2.102.2.20 Neutral 89b483f429c47342 x86
Oracle.DataAccess.resources 10.2.0.100 pt-BR 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 zh-CHT 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 zh-CHS 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 ko 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 jp 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 it 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 fr 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 es 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 de 89b483f429c47342
Policy.10.1.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Policy.10.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Policy.9.2.Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
Policy.9.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
What should I check and do to solve this problems?
Thanks for help,
Anderson

Hi,
Often the error "The provider is not compatible with the version of Oracle client" is raised when the unmanaged dll OraOpsX.dll can't be found, can't be loaded, or is the wrong version. For version 10.2.0.x of ODP.NET and .NET Framework 2.x the file should be called "OraOps10w.dll" and should be found in the %ORACLE_HOME%\bin directory.
Since the ODAC pieces are installed on the same host as the database, are they in a separate Oracle Home or the same Oracle Home as the database software? If there are multiple Oracle Home directories, which one is in the system path first?
I would start with verifying the version of OraOps10w.dll and the system path on the server. You might also confirm that the Oracle Home directory (and everything under it) has the following permissions for Authenticated Users:
- Read & Execute
- List folder contents
- Read
Regards,
Mark

Another: The provider is not compatible with the version of Oracle client

Hi everybody,
We still have problems with the ODP dll. with our .Net development. I copied all the dlls as mentioned here: [http://splinter.com.au/blog/?p=156] and in many other posts here in the forum. The .Net development works fine on our Development PCs (WIN XP32) and on many other PCs in the company. But we still have some PCs (As well WIN XP32) that come up with the Error: The provider is not compatible with the version of Oracle client.
Has anyone an idea???
Thanks a lot for your help
Best Jan

Hi Jan,
If there has never been any Oracle Client software installed on the machines, it seems unlikely that there would be Oracle policy files and version(s) of Oracle.DataAccess in the GAC. But, yes, the CLR will look to the GAC first for loading the Oracle.DataAccess assembly. I'm not sure what Framework or Domain setting would be involved here if there is no Oracle client installed. Are the machines configured the same as far as Regional/Language settings, etc?
One thing you might be able to try is to create an application configuration file and enable ODP.NET trace in the file. This is an ODP.NET 11.1 new feature. However, it's possible the error will prevent the trace file from being created. You would create a file named YourApplicationName.exe.config and here is a sample of the minimum content to enable ODP.NET trace:
{noformat}
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<oracle.dataaccess.client>
   <settings>
     <add name="TraceFileName" value="c:\odpnet2.trc"/>
     <add name="TraceLevel" value="1"/>
   </settings>
</oracle.dataaccess.client>
</configuration>
{noformat}
I wish I had an easy answer for you!
Regards,
Mark

The provider is not compatible with the version of Oracle client

We are running Server 2012 64 bit with multiple homes one is 32 bit and the other 64 bit. We installed the 64 bit first then the 32 bit next in order to get our Classic ASP WebSite that is using COM+ and OLEDB to see the provider.
C:\oracle\product\12.1.0\x86
C:\oracle\product\12.1.0\x64
The other Websites are ASP.Net 4.0 and are running in 64 bit application pools. They are using a DAL .Net assembly built x64 with a reference to the 64 bit ODP.Net version 4.121.1.0 in C:\oracle\product\12.1.0\X64\client_1\odp.net\bin\4.
I also see there is another folder C:\oracle\product\12.1.0\X64\odac_1\odp.net\bin\2.x with version 2.121.2.0. We are on running Framework 4.0 but when I switch to this version it works but with the version out of the bid\4 we are receiving the following error when the 64 bit Websites call the assembly:
The provider is not compatible with the version of Oracle client
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client
Source Error:
Line 87: mDataSource = dataSource
Line 88: mConnectionString = GetDBConnectionString(dataSource)
Line 89: mConnection = New OracleConnection(mConnectionString)
Line 90: mParams = New List(Of IDbDataParameter)
Line 91: End Sub
I have not been successful in getting this to work after spending endless hours, so any help would be appreciated.

Hi,
Oracle Client/ODP build with certified Visual C++ Libraries so application using ODP.NET requires "runtime components of Visual C++ Libraries" to be installed.
Oracle Database Client installation includes the Visual C++ Libraries but ODAC doesn't contain these libraries which may cause such issue.
Please check the Note 43208.1 for the particular version of Visual C++ installs with Oracle Database Client installation(e.g. 11.2.0 Database Client installs Visual C++ .NET 2005) and also you can refer the windows event log error massage to verify which version of Visual C++ is missing.
thanks and regards
Venkat

'The provider is not compatible with the version of Oracle client' exceptio

Hi
I installed ODAC-11.1.0.7.10 Beta on my development system and developed a .net application which uses Oracle.DataAccess.dll to connect to Oracle10g database.
the application is working fine, means opening connection successfully when I run it from my development system. but the same application is throwing
'The provider is not compatible with the version of Oracle client' exception when I run it on my 10g database server system.
what I need to do to run the application successfully on the machine where 10g server exists?
any help is appreciated.
thanks,
harry

Hi Harry,
I am not sure why you installed 11.1.0.7.10 Beta as 11.1.0.7.20 has been released and you should not be using the beta at this time. That error message is because the dependencies being loaded by the process are the wrong version. When you deploy an ODP .NET application using 11.1.7.x, you need to make sure you deploy it to a machine where the 11.1.0.7.x dependencies are installed. My guess is if I read your poat correctly is that Oracle.DataAccess.dll version 11.1 is loaded but its finding 10.2 dependencies on the target deployment box.
HTH
Jenny

I've got a payg sim: i've been given an iphone 3g, and when i connected it to my mac and itunes, a message told me that the sim was :not compatible" with the iphone. is this because, as i've been told, my card is an old style sim and i need the newer styl

i've got a vodsaphone payg sim: i've been given an iphone 3g, and when i connected it to my mac and itunes, a message told me that the sim was :not compatible" with the iphone. is this because, as i've been told, my card is an old style sim and i need the newer style that works In smart phones? if so, how do i go about getting the right card.

Contact your carrier & get a new sim...they should give you one for free.

Inner Exception The provider is not compatible with the version of Oracle

I am using the 64 bit ODP and Net 2.0 SDK in a C# program which runs standalone and is also hosted by another win32 process.
When running standalone it works ok. But when being hosted by another process, I get the following exceptions thrown when i create a connection:
INFO 2007-01-10 12:38:26,843 265ms frmCCMain LogMessage - Exception During Batch Processing1: [The type initializer for 'Oracle.DataAccess.Client.OracleConnection' threw an exception.]
INFO 2007-01-10 12:38:26,843 265ms frmCCMain LogMessage - Inner Exception The provider is not compatible with the version of Oracle client
I checked the DllPath value under the ODP.NET key and it points to the directory where OraOps10w.dll is installed. I also tried copying that Dll into the host process working directory and searched and found no other versions of that DLL.

Yes, this sounds like you may be using the 9.2 client with ODP.NET and ASP.NET Providers for 11g. Usually, you can stop and start IIS to resolve this. IIS will then pick up that the 11g client directory is first in the Windows PATH, ahead of the 9.2 client directory, then use that for any subsequent Oracle client calls.

The provider is not compatible with the version of Oracle client... again!

Please, please, please help me!
I get the error, "The provider is not compatible with the version of Oracle client", intermittently on my Test Server. Strangely, without restarting the server or IIS, my application suddenly decides that I don't have the right Oracle client. I don't have any such issue on my local machine even though I'm using the same Oracle 11g client from Beta 1.
I have Oracle 11g (D:\Oracle11g\product\11.1.0) installed. I tried specifying which assembly to use in my web.config:
<compilation debug="true" defaultLanguage="c#">
<assemblies>
<add assembly="Oracle.DataAccess, Version=2.111.5.10, Culture=neutral, PublicKeyToken=89b483f429c47342" />
</assemblies>
</compilation>
I'm not even trying to use a 10g client with the Providers as discussed here: "The provider is not compatible with the version of Oracle client"
What I don't understand is why this error comes and goes?!?! Has anyone experienced anything like this?

The server is Win 2003. The local development machine is WinXP.
...I was trying to wait to install Beta 2 because of the nasty bugs reported on this forum.
I'm now seeing that ORACLE_HOME wasn't set on my server because my co-worker removed the path. Somehow it was able to find an Oracle Home on the server, but apparently, it didn't always find the same home causing this error intermittently.
Now, my question is how can I get my application to use the 11g Client as its Oracle Home, while my co-worker can use 10g Client as his Oracle Home? To be a bit more specific, he needs to use an ODBC client to connect because his application uses Classic ASP.
Is this possible, or are we going to have to set up separate machines?
Bee

'The provider is not compatible with the version of Oracle client error' popping up randomly

I have several asp.net pages running on an application server which generally work without issue. However I've had the Server error "The provider is not compatible with the version of Oracle client error" crop up twice seemingly randomly that affects all of my pages that interact with the DB server. A simple reboot of the application server solves the issue and the pages run again with no problems. What could be causing this problem?

Sorry if I wasn't clear initially. Basically I've got 2 different applications in 2 different IIS folders on the webserver, each with several asp.net pages. They work fine for a period of time and then inexplicably that error gets thrown and affects all of my asp.net pages in both applications. The admin tells me that the other older applications on the same server are unaffected. A simple reboot of the server fixes the issue until the next time it happens (I can't identify any consistent point where this crash happens, the admin originally suggested that there might be something in my code causing a memory issue). I had the same applications hosted on my local machine for a time and this never happened as well as it never happening when I run them in localhost. How can I trace whether or not another part of my application is trying to load ODP.NET by itself? How can I verify the DLL search order for my application?

Getting "The provider is not compatible with the version of Oracle client"

Hi,
By reading though posts this appears to be a very common and some people have been able to solve it by putting their OracleDataAccess.dll and support files in the same folder as the exe. However, I tried putting the OracleDataAccess.dll, oci.dll, ociw32.dll, orannzsbb11.dll, and oraocci11.dll in the folder and the problem persists.
This application works fine on my development system (Windows 7 64, VS2010 SP1) and 2 of our 3 servers (Windows 2008 R2). But on this one server it does not work! The problem first appeared when a developer installed ODT with ODAC 112030 on server. We installed a full version of the 11.2.0.1.0 Oracle Client (this matches our other servers) and removed the clients created by the ODT with ODAC 112030 install. However, I fear there is something somewhere that was not deinstalled causing the issue. Any thought on how we can track down and eliminate this problem.
Thanks,
Jerry
Edited by: user13142870 on May 22, 2012 9:51 AM

I changed the CPU to x86 in the solutions and the project is now working.

The data type of the variant is not compatible with the data type wired to the type input.

Hello all..
Iam curently struggling with the following:
On my main(top)_VI, I have a mix-signal graph which will output several or one signals depending on the user. I also have an inner subvi which has the analisys i want to give the the data before outputing it to the main(top) VI, which has the mix-signal graph control.
Now, I created a reference from the mix-signal graph and Iam imputing this reference into the subVI (which inside has a property node type_control_mix-signal graph in which Iam connecting the refnum from the top VI to view the output data). The data consists of an array of clusters of 2 arrays of doubles each.
-- let say I create the property node type control mix-signal graph and i choose value property; it lets me put the array of clusters of 2 arrays of doubles each without problems; Now the second I connect the refnum pointing to the mix-signal graph on the Main_VI it brakes the cables and only accepts one cluster of two arrays os doubles instead.
--if on the other hand I connect the refnum to the property node type_control_mix-signal graph before connecting the imput it doesnt complain until I run the VI where it gives the error 91.
I have also notices a (strict) parenthisis at the end of the property node sometimes. [what does this (strict) means?]
FInally if instead of creating the refnum from the Main_VI, I create either a xy graph or a mix-signal praph it lets me connect the an array of clusters of 2 arrays of doubles each without any problem. The refnum connection seems to be the problematic factor, but by the same tolken I dont know any other means of sending that data from the inner to the outter VI.
I have the feeling Iam missing on one or more Labview fundamentals regarding refnums.
Any help will be apreciated

You almost found it on your own. The refnum needs to be 'strict', that means that the data type of the graph is set (2D dbl), otherwise it will use the default data type. To do this you create the refnum directly from the graph after you have wired the correct data type to the terminal. In this case the refnum wire will break if you change the data type of the graph.
Independend of this issue, I suggest you not to use the value property on the graph but directly wire the data (e.g. the 2D double) to the SubVI. The property value is by far the slowest way to get data, and 2D arrays are really some amount of data.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

HT4864 Is the icloud email not compatible with the andriod tablet

I am having a hard time getting my icloud email to set-up on my galaxy tablet. I had no problem getting it set-up on my note, but I'm not having the same luck with the Note 8.0. How Can I find out if the email is POP3 or IMAP.

If you search these forums you'll find other people having the same problem. From what I remember the problem is an IMAP bug in the Samsung, which has apparently been fixed in a later firmware uodate.

I have an ipad2 and everytime I try to use the camera conector kit to read a sd card I got a message saying that the device is not compatible withe the ipad, can any one help me please?

Subject:

First, try gently blowing into the dock connector on your iPad to make sure there's no debris in there. That can sometimes cause accessories to malfunction. If that doesn't clear it up, try rebooting your iPad:
To reboot your iPad, hold down the sleep/wake button and the home button simultaneously until the screen goes black and the Apple logo appears. If, during this process, a slider appears on the screen to power it off, ignore it and keep holding the buttons down.
Rebooting your iPad can solve a lot of problems.

Moved Premiere Elements 10 project Error: "Project is not compatible with current version of Premiere Elements"

After moving an entire client folder from an external hard drive to an internal one, the client's video, created in adobe premiere elements 10, will no longer open in adobe premiere elements 10. It appears to be loading the project, and instead of completing, the following error message is displayed: "The project is not compatible with current version of Premiere Elements."
The same thing occurs when attempting to open the archive files.
New projects, and unmoved projects behave properly.
Moved projects receive this error.
I'm running Windows 7 Home Premium SP1 on a solid state drive (SSD) (c:/), where premiere elements is installed
My documents, including the project I need to work with are on my "storage" drive (HDD). it is (f:/)

txnoda
Archiving Aspects of this.....
First let clear the matter of the "archiving" as a life saver.... We do not appear to be on the same wave length.
a. I am talking about File Menu/Project Archiver with its Archive project and Copy project options. This feature is a safety net to save you when you
inadvertently disconnect source media from the project file. With the Archive option (Trimmed Folder result), you get saved to the computer hard drive (safe keeping) a copy of the project file plus copies of the media that were taken to the Timeline. With the Copy option (Copied Folder result), you get copy of the project files plus copies of much more.
b. Instead, you appear to be talking about "archiving" in the context of AutoSaves. AutoSaves are saved snapshots of the project at various phases of the edit. They suffer from the same shortcomings of the original project that has been disconnected from its source media.
When you import media into a project, all you get are copies of the originals in the project. But, those copies need to trace back to originals at the locations where they were when first imported into the project. Moving, renaming, deleting files/folders that went into the project after the project save close leads to some very time consuming messy situations.
What to do....
If you can, put everything back the way it was. If not.....
Let me emphasis some factors..
You wrote
After moving an entire client folder from an external hard drive to an internal one, the client's video, created in adobe premiere elements 10, will no longer open in adobe premiere elements 10. It appears to be loading the project, and instead of completing, the following error message is displayed: "The project is not compatible with current version of Premiere Elements."
Here you mention specifically "client's video". Later you detail with .mod files converted to .avi. What kind of .avi? If you have converted to AVCHD.avi or H.264.avi, they have been found not to be compatible with Premiere Elements. You should not be able to import them into any new or old project.
From what you described, I am envisioning
"Video" Folder
which contains 2 folders named
"Timestamped Folder" with .avi files
and
"DVD" Folder with the project file (project.prel)
The project file has many files generated automatically in the course of it workflow. Where do you have them going?
(See Premiere Elements 10 Edit Menu/Preferences/Scratch Discs). If you have the Scratch Discs directed
"Same As Project", then we would expect all those files to be going to the DVD Folder in the above scenario.
If we could open the project and get greeted with some "Where is the file.....?" messages, that might give us some hope.
But that is not the case.
Consequently from what you have said, I am suggesting that the path of least resistance is try to recreate the "before".
Please review and consider.
ATR
Add On...Not sure if it will assist in the matter, but the following is the link to Adobe's document related to troubleshooting
damaged projects.
Troubleshoot a damaged project file | Adobe Premiere Elements

E-mailed File "The project is not compatible with the current version of Premiere Elements"

Similar Messages

Maybe you are looking for