Plug in directory

Hi, I am in the process of configuration, the environment is: SQL 2005, Windows 2003, the installed component is: Weblogic 9.2, EPMA, Essbase, Planning, SmartView. when I configure the web server, I select Apachy, and the next screen ask for the web server plug in folder, "Enter the directory where the plug-ins(mod_wl_20.so) are installed, who can tell me the correct plug-ins directory?thanks!

When you installed weblogic, did you select custom install and select "web server plugins", this will install the files you need in the BEA installation.
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

When installing, get "Error! Can't initialize plug-ins directory"

Began having problems when opening Firefox and trying to make Firefox the default browser. Windows 7 updated, AVG up-to-date and virus scans clean, MalwareBytes up-to-date and scans clean. Troubleshooting finally caused me to uninstall and try for clean install ... normal Windows 7 uninstall process successful. Made sure Firefox folder in "Program Files" was deleted. Downloaded "DownloadApp_1_7_5_198_Setup" (29,442 KB) from Mozilla website and run ... get "Error! Can't initialize plug-ins directory. Please try again later."

Thank you guig2! Followed your bleepingcomputer.com link above and found the problem was my permissions on C:\Users\Bill\AppData\Local/Temp. It was not "Full Control" for my User or Administrator. Updated the two lines to permit full control for folder, subfolder and files. Ran perfect.

Error messages after alternate plug-ins directory chosen

After my initial install of the CS6 beta, which went quickly and flawlessly (I have learned to turn off my virus protection during install due to previous problems with installs of older versions of PS) I went to preferences and chose my CS5 plug-ins directory.
After that was done I got a series of 3 error messages which, after closing them, did NOT prevent CS6 from opening eventually.
I would like to know what I can do to get rid of those error messages.
I've posted screen grabs here: <http://www.flickr.com/photos/isabel95/7009088577/in/photostream> Click on "newer" to see the following two error messages.

you should not do that.
isabel95 wrote:
After my initial install of the CS6 beta, which went quickly and flawlessly (I have learned to turn off my virus protection during install due to previous problems with installs of older versions of PS) I went to preferences and chose my CS5 plug-ins directory.
Plug-in Compatibility
In general:
3rd Party plug-ins that are compatible in Photoshop CS5 should be compatible in Photoshop CS6
Adobe provided plug-ins, and additional plug-ins, for CS5 are not compatible in Photoshop CS6 Photoshop CS5 Optional Plug-Ins (Mac/Win)
TWAIN plug-in | Photoshop CS4, CS5
OpenEXR Alpha plug-in | Photoshop CS5 Extended
Do:
Check the plug-in manufacturer's website for the latest version of your plug-in
Use the manufacturer's plug-in installer to install their plug-ins
Don't:
Do not point Photoshop CS6's "Additional Plug-ins" preference (Preferences>Plug-Ins...) at a previous version of Photoshop's 'Plug-Ins' folder.
Do not manually drag plug-ins from a previous version of Photoshop's plug-ins folder to Photoshop CS6's 'Plug-Ins' folder

Photoshop Plug-In directory localized names

Hello,
I want to build an installer that automatically finds the right destination directory for a plug-in. The only problem I have is that Adobe uses localized names for the "Plug-Ins" directory as well as its subdirectories (esp. "Import/Export" in my case).
Is there some official documentation on what these names are for the different languages (in versions CS2 and later). I couldn't find such a document online or in the SDK, but this surely must be available somewhere.
Thanks.

One other thought: the idea of an automatic installer which makes this
decision alarms me. It's very useful to pick a default before
presenting the user with a choice, but to just go ahead is surely
wrong.
I have seen plug-in installers that do this. The problem is that they
do not accommodate the case where you have more than one copy/version
of Photoshop installed. Where the installation is complex (more than
copying a file) it can make it difficult or impossible to use the
plug-in with those other installations.
How about
* Find the default Photoshop folder
* Put up a folder chooser window inviting people to choose their
plug-ins folder
* Normally this is just one folder within this Photoshop folder, but
people with more than one installation can choose
* If you can't find Photoshop, skip straight in at the prompt (with a
suitable message, as not everyone really understands system
requirements)
Aandi Inston

Error message: cannot find browsers plug in directory

I am trying repeatedly to install flash player 9. I have
installed from the web site, I have down loaded the installer file
and ran that. I have downloaded the uninstaller, ran that,
rebooted, reinstalled from the web site, rebooted and still
nothing. I keep just getting white blank boxes. this is so
frustrating. When I run the downloaded installer it keeps coming up
with an error message that says flash player cannot detect your
browsers plug in directory. I don't know where to install the file
to, i don't know where the browsers plug in directory is. help
please

Hello Ian,
From what I understand, this problem occurs because of the fact that DSC loads some DLLs dynamically in some of its VIs. Since they are loaded dynamically (instead of having concrete search paths), it takes LabVIEW a while to find them...if it takes too long, you will receive the error you mentioned.
From what I understand, this problem does not occur in the 6.1 version of the DSC module. If you are still using 6.0.2, the simplest workaround for now is to use the File >> Open option in LabVIEW instead of double-clicking on the LLB.
I hope this suggestion helps. Good luck with your application.
Sincerely,
Darren N.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Want to make firefox my default brouser but get error message "can"t initialize plug ins directory" try again later?

That's the basic problem. I've tried a number of trouble shooting corrections; but nothing works.

Hello,
Certain Firefox problems can be solved by performing a ''Clean reinstall''. This means you remove Firefox program files and then reinstall Firefox. Please follow these steps:
'''Note:''' You might want to print these steps or view them in another browser.
#Download the latest Desktop version of Firefox from http://www.mozilla.org and save the setup file to your computer.
#After the download finishes, close all Firefox windows (click Exit from the Firefox or File menu).
#Delete the Firefox installation folder, which is located in one of these locations, by default:
#*'''Windows:'''
#**C:\Program Files\Mozilla Firefox
#**C:\Program Files (x86)\Mozilla Firefox
#*'''Mac:''' Delete Firefox from the Applications folder.
#*'''Linux:''' If you installed Firefox with the distro-based package manager, you should use the same way to uninstall it - see [[Installing Firefox on Linux]]. If you downloaded and installed the binary package from the [http://www.mozilla.org/firefox#desktop Firefox download page], simply remove the folder ''firefox'' in your home directory.
#Now, go ahead and reinstall Firefox:
##Double-click the downloaded installation file and go through the steps of the installation wizard.
##Once the wizard is finished, choose to directly open Firefox after clicking the Finish button.
Please report back to see if this helped you!
Thank you.

How to enable a plug-in to load in previous versions of Acrobat

We need to run a plug-in compiled with Acrobat 9 SDK under Acrobat 7. However, when I copy my plugin to the Acrobat 7 plug-ins directory and open Acrobat, it gives an error saying Plug-in is incompatible with this version of Acrobat.
Please let me know how can we enable the plug-in to work in Acrobat 7.

I just figured out a way to enable the plugin in Acrobat 7 by modifying the PI_ACROSUPPORT_VERSION defined in pirequir.h from ASCallsHFT_VERSION_8 to ASCallsHFT_VERSION_7.
Please confirm if this is the correct.

VI Search Path not working in LV2011 for VI Server Plug-ins with exe

I have found what seems to be a problem with the search path when a LabVIEW 2011 built executable calls a Plug-in VI.
When the plug-in VI has subVI’s from vi.lib on its diagram the executable has to know where to find them. Not all VI’s in vi.lib are part of the run time engine or the dll’s that may get generated as part of the build. The things you have to do to make plug-ins work for an executable are explained in several Developer Zone articles. The article titled “How Can I Change or Set the VI Search Path for LabVIEW Executables” describes the ini file setting viSearchPath. When this is set to the vi.lib directory I have not encountered problems with previous versions up to and including LabVIEW 2010.
I have come across an example in LabVIEW 2011 where it doesn’t work. I have attached an example (I am using LV2011 SP1). It demonstrates the basic plug-in architecture. Everything works in the development environment. But it doesn’t work from a built exe. I haven’t included the actual built exe in the zip file in case that causes a problem downloading it. If you run the build spec from the src directory project file the exe should get generated in the bld directory. The problem appears to occur when certain VIs from the analysis library are in the Plug-in. In the example attached, the Plug-in VI is very simple but I have placed the troublesome SubVI on the diagram. The VI in this example where there is a problem finding it is the Butterworth Filter VI. I have placed it on the diagram in a conditional disable structure so it is easy to enable and disable. When enabled and you run the test Plug-in VI the error 1003 is raised, meaning a subVI cannot be found in the dynamically called VI (for example see this post). Note that a way round this may be to incorporate the Plug-in VI into the built exe but this shouldn't be necessary. It’s not a problem with this specific filter VI, as it occurs for other VIs I try on the diagram. However if you place an FFT VI on the diagram there is no problem. I suspect that one is built into the Run-Time Engine.
I also note I am running Win7 64 bit and 32 bit LabVIEW (note the relevant viSearchPath in the ini file – you may need to change if you are on different version of Windows). If the example is converted to LabVIEW 2010 everything works as expected for the built exe. I tried that on a colleague’s computer running XP and 2010 but I am pretty sure in still also works on Win 7.
Things I am suspicious of are that the analysis VI’s are part of a LabVIEW library (lvlib) and perhaps something has changed there? I understand there is a problem with OOP in LabVIEW 2011. Perhaps it is related to that as that seems to be an issue in 2011 (see this Discussion Forum post). Perhaps it is related to OS version?
I also tried generating a Source Distribution to extract out all the vi.lib VI’s and place them directly in the Plug-in directory. That didn’t help.
Interested in whether anyone else reproduces this behaviour. In any case something is different in 2011.
Attachments:
LV 2011 test Plug-in.zip ‏42 KB

I found some more out about this issue working with my local NI rep here in Australia. Apparently something has changed in the compiler between LabVIEW 2010 and 2011. Using the viSearchPath token in the ini file, as described in various Developer Zone articles, now guarantees that the Plug-in will not work. The only way to make it work appears to be to create a Source Distribution. I noted in my original post that I had already tried this and it would not work. It turns out that having the viSearchPath token in the ini file when using a Source Distribution causes the error 1003 to occur. When the token is taken out of the ini file the Plug-in (containing an analysis VI) with a Source Distribution works - in the simple example I posted.
Well I then found its a bit more complicated than this. It all worked for the simple example I posted. Recall we found the error when there was an analysis VI in the Plug-in VI. In our actual application (which is a large one) that calls Plug-ins - we still got the error 1003. By trial and error I found a workaround. There are certain Build Spec settings for the calling exe that I set and found worked. On the Additional Exclusions page I found that I had to make sure that I left unchecked "Modify Project Library File after removing unused members". I've always had trouble understanding the need for this setting. In the Build Spec Help on that page it notes that the build will take longer. In most builds you remove polymorphic VI instances, remove unused members of Project libraries and also Modify the project library file after removing the instances (this is a sub setting of the previous). This makes the exe smaller in size and a quicker build time. Obviously modifying the project library caused a problem. In the big application exe calling Plug-in, I probably have the same analysis VI on the diagram (I haven't actually checked and also whether it is the same polymorphic instance) and in the simple example I posted I definitely did not have VI in the calling exe example - so there may be some clue there. I should try putting the same analysis VI on the calling exe diagram in the simple example to see what happens but I'm running out of energy on this one :-(
So none of this gives me much confidence and I wish I could get a better explanation from NI regarding this behaviour to be sure I am not going to encounter a different problem for different calling exe and Plug-ins. I was advised that a CAR would be issued. Perhaps this is now expected behaviour for 2011 but it would helpful if some definitive explanation could be given about what has changed from LV2010. And an update of Developer Zone articles on the subject would be helpful.

How to uninstall a plug-in?

This is with Photoshop CC 2014 on Windows 7.
Help > System Info reports the following (at the very end of the list):
Optional and third party plug-ins:
SilverFast 8 x64 10.0
Plug-ins that failed to load: NONE
Flash:
Installed TWAIN devices: NONE
There is no SilverFast file in "C:\Program Files (x86)\Adobe\Adobe Photoshop CC\Plug-ins\".
There was a file named "SilverFast 8 x86.8ba" in "C:\Program Files (x86)\Adobe\Adobe Photoshop CS5\Plug-ins\Import-Export\"
I don't understand why CC is reporting the plug-in when I don't even have CS5 installed anymore, but I deleted that file in the CS5 directory. My understanding is that this should uninstall a plug-in. I also uninstalled the stand-alone SilverFast software through the Windows control panel.
After moving the file out of the Plug-ins directory Photoshop CC Help > System Info still reports that the SilverFast plug-in is installed.
Am I missing something? Thanks.

Figured this out myself eventually. Posting the solution here in case anyone ends up here searching for this situation.
My confusion came from the installation location. I guess a 32-bit installation of Photoshop CC went into "c:\program files (x86)\", but the one I was working off of was in "c:\program files\".
I tracked down all the files in the "plug-ins" directories there and removed them, which did the trick.

Browser plug-in with mac run-time engine problem

I have repeatdly tried to get web browser (Both Explorer 5.2.3 and Safari) VI viewing on my Mac (OS 10.4.2). I have reinstalled the run time engine (Labview 7.1.1 as downloaded from NI) numerous times with no luck. I get the usual "Browser plug-in required" message.
Doing a seach on my machine in the Internet plug-in folder reveals no new plug-ins after installation of the RTE.
I can run this VI work fine on a remote PC running Explorer, so I think my VI server is running fine. I quit the PC before trying it on the MAC to avoid any license limitations.
Any suggestions? Is the browser plug in available as a seperate down load? I could not locate it on the NI site.
Thanks
-G

Hi G,
Lets try this. Install the LV71NPlugin file, in the attached image, in the /Library/Internet Plug-Ins directory. I had to save the image with a different extension to be able to upload it to the forum so...
1) Download the file
2) Change the file extension from "abc" to "dmg"
3) Copy LV71NPlugin to /Library/Internet Plug-Ins
Please let me know if this works for you.
Thanks
Chris J
Attachments:
LabVIEW71BrowserPlugin.abc ‏83 KB

TiltShift plug-in doesn't work anymore

I have an edit plug-in that I bought some time ago (still have the eReceipt) called TiltShift but its no longer loading. I get an error when I try to edit an image with the plug-in, Aperture saying there was an error when loading the plug-in.
The plug-in is still on the disk, in Aperture application support, in the plug-in directory. Oddly, its not in the Edit folder (none of my edit plug-ins are, but the others seem to work). But its there. A quick look through Time Machine shows no obvious changes here. It just stopped working.
I do see the plug-in is no longer available for download from the Apple page, which is how I got it in the first place. Wondering if the company went out of business, and if the plug-in somehow tries to validate itself before loading? I think the company name was Share It. German based, I believe.

All the given information are correct...a simple "googling" gave me this:
http://www.apple.com/downloads/macosx/aperture/tiltshift.html (it's still active)
plus, if you click onto the company name the homepage will open...you can write an email to ask for support or whatever...
...not so difficult, isn't it?
Have a nice day!
Alberto

Possible to Change the Plug-Ins Folder Used by Safari?

I'm trying to set up Firefox with no plug-ins and Safari with plugins, to switch back and forth as needed.
Both want to use the same Library/Internet Plugins folder.
Any way to alter the plug-ins directory for either of them?
Is a Unix command going to come to my rescue to set Safari's plug-ins path?

I would expect both applications to call the same system command to locate the plugins directory. It's not going to be as straightforward as a string of text in a preference file.
The only way I can see this working is to move the plugins in/out of the plugins direcotory before you launch each app. Of course, that may be problematic if you want to run both browsers at the same time.
If you want to run both browsers at once, one thing that might work is changing the plugins directory mid-stream. Most apps will only check for plugins during startup (which is why you usually need to reboot to activate new plugins). Therefore you may be able to move your plugins out of the directory, launch FireFox, move the plugins back and launch Safari.
In this setup Firefox should see no plugins and Safari sees them all. A script could automate this process if it works for you.

Waves Plug ins and Final Cut

I run Pro Tools on a Macbook Pro which also hosts Final Cut Studio. I am having a problem whereby on booting the program it crashes if the iLok isn't inserted but if the iLok is there, it takes forever to load - I mean forever - I am still waiting for it after about 10 minutes and am unsure whether it is going ot do it at all. It is just the Native Power Pack but there are a lot of impulse responses for the reverb it seems to be loading - the point is, I don't want to use Waves with Final Cut - I just want to import and edit some video quickly but this is causing me a bit of a headache - I am sure there is a simple solution.
Thanks in anticipation all you wonderful boffins
Matt

The solution is simple but but you might not like it ...
FCP is Audio Unit aware, and your Waves plug-ins are Audio Units and so are being loaded by FCP.
The only way to stop this from happening is to move the offending plug-ins out of the /Library/Audio/Plug-ins directory before you launch FCP ... of course, this then means you need to move them back in again before you use Pro Tools ... not too great :/
Manually, you could simplify this by creating shortcuts (aliases) to the folders on the desktop, so it would be easy to drag and drop between the two.
Or, if you're that way inclined, you could create an Automator action or AppleScript to do it for you.
Perhaps easiest would be to create two separate user accounts, one you use for Pro Tools and one for FCP. Install the Waves plugins in the Pro Tools user's ~/Library/Audio/Plug-ins folder, rather than the global one. Then just use Fast User Switching to switch environments.
Hope it helps
Andy
EDIT: Oh heck look --> http://www.audiofile-engineering.com/audiounitmanager/ this may be by far the better solution for simply switching plugin sets, you just need to create a separate set for FCP and Pro Tools, or just switch between None and All. Gotta be worth checking out as its free! Everybody loves free

Plug-Ins folder paths

How do people go about installing their plugins on different languages? It seems like Adobe is localizing the name of the Plug-Ins folder depdending on the language the system is installed on or maybe it's their localized installers doing it. In any case, i need to find out the correct paths for these languages:
English
French
German
Italian
Spanish
Japanses
Simplified Chinese
Does anyone know where i can find these?
thx

This gets asked a lot, so perhaps folks can post information for the languages they know about.
A German customer of mine reported that the plug-ins directory for CS2 on his Windows XP system is
AdobeCS2\Zusatzmodule
And the following subdirectories are localized as follows
"Effects" = "Effekte"
"File Formats" = "Dateiformat"
"Filters" = "Filter"
"Import-Export" = "Importieren-Exportieren"
I'd like to know the equivalents for French systems.
David

Acrobat retains plug-ins after deletion

I have installed Acrobat Pro 8.1 and added upgrades for 8.1.1 and 8.1.2.
This is with Vista Home Premium.
I added some plug-ins eg pitstop and then uninstalled them. They are not in the plug-ins directory or on any drive, however Acrobat still has them working?
I also have a problem when I click help, I get no drop down and the program stops working?

For info! Problem solved.
I have found the api Using advanced search method and ticking the box "Include non-indexed, hidden and system files" option.
It found
C:\Users\Ian\AppData\Local\VirtualStore\Program Files\Adobe\Acrobat 8.0\Acrobat\plug_ins\...
Now I do have a virtual machine loaded to run XP programs that fail in vista I must have once had acrobat on it with these plug-ins then I removed acrobat, so now when I look at it I see no acrobat and think it is clean, but there it is! Even now if I look at c:\Program Files\Adobe\Acrobat 8.0\Acrobat\plug_ins in the XP virtual machine I see nothing infact there is no Acrobat 8 at all, but this file remains!
So If I go to vista, as me, delete that file when acrobat runs the plug-ins have gone.

Plug in directory

Similar Messages

Maybe you are looking for