Can't install BI Publisher for desktop - oracle11g

I'm having problems installing BI Publisher for Desktop 11.1.1.9.0 32bit(11g) on Win7 64 bit system (Office 2013). Previously I successfully installed it but there was no add-on visible in Office, so tried with 64 bit version but with no luck. After that I've uninstalled it but now it keeps giving me these errors, "INSTALL DIR get falied!" and "TBMenusSetup.msi!"
Any idea hoe to solve this?
Br

This is what I did on Windows 7 (64-bit) and Office 2013 (32-bit):
Download: Oracle BI Publisher Desktop 11.1.1.7.0 for 32 bit Office on Windows (244 MB) - http://www.oracle.com/technetwork/middleware/bi-publisher/downloads/index.html
Run BIPublisherDesktop32.exe
If Add-In doesn't show up at this point, run step 4
Run setup.exe from here: C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotNetInstallFiles\setup.exe
Done

I also check the following conditions if I have trouble with installing BIP (which I often have)
Make sure that the versions on your system are matching
(JRE,Office,BIP). That means: If you have Office in 64bit you need
JRE(64bit) and BIP(64bit).
Check if the addon is deactivated by word and activate it in case.
Use "Run as Administrator" with the BIP Installer.
Hope this helps :)

download bi publisher desktop and do a fresh install.
if you are not getting the add on then go to Microsoft office icon-->word option-->add ins-->then check in manage drop down(disabled items).If its Bi Publisher then click on that.You will get this in MS word.

https://carsandcode.com/2014/05/12/oracle-bi-publisher-desktop-on-64-bit-windows-with-32-bit-office/
Personally, until next time, not sure what worked, as above step I did earlier with no resolution.
But, I have been installing, troubleshooting BIP Desktop for few years and each time it is broken, fix do not exist and there are threads which leads to absolutely nothing. This time around, O365 was rolled out to Pilot Users and yes BIP toolbar gone. Uninstalled O365, re-installed Office 2010, repair/remove/reinstall - none worked. Ran MS Debug/ Sysinternals - Procmon/ProcessXP - found leak threads but nothing to suggest which components is missing or corrupted. Finally, I started running all msi and pre-req sw in BIP dir and DotNetInstallFiles, and it did come back the elusive toolbar, which MS Word fails to load or kept in Inactive add-ins.

Related

The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. and install Access Database Engine 2010 don´t work

I have trouble when I try to upload an Excel file, I've searched in a lot of places how to solve this, but the solution the give (only install Microsoft Access Database Engine 2010 Redistributable) doesn´t work for me. I have VS2017 and I've installed Microsoft Access Database Engine 2010 Redistributable, I´m kinda new doing this so I donn´t know what I´m missing.
Thanks
a pleasure to greet you, an hour ago I had the same problem, the only thing I did was download both versions (both the 32-bit and the 64-bit version) and the first thing I did was install the 64-bit version of normal way, downloading from the official page, but I installed the 32-bit version from Command Prompt with the following code:
CD: [path]/AccessDataEngine.exe /passive
in this way I managed to solve that error

How to prevent Qt 6.0 Installer from crashing?

Here’s what happens
I open the installer, choose the packages I want(I choose to install some 1.7 GB of components), everything goes well.
But then when I click on the Install button, and Qt installer crashes! And by crashes I mean it crashes, Windows DOES NOT tell me it is not responding. The window just gets invisible from the taskbar.
There also is no possibility that it is installing in the background, as I waited for approx. 5 mins, and when I checked in the folder where I was going to install it, I didn’t find a SINGLE component installed!
How to solve that?
I asked some questions earlier because a person needs more information. It also depends on what compiler you have. There are many many known issues with Qt 6.x.
The default kit doesn't work with MSVC2019
https://forum.qt.io/topic/120357/wrong-kit-for-qt-6-0-0-msvc2019-64bit/5
Qt 6.0 has install issues with GLib 6
https://youtu.be/IZy6FMQlaNg
There also appears to be significant problems with OpenGL.
https://github.com/opencv/opencv/issues/20499
People seem to still be able to get off-line installers, and, as this French typing person found out, you have to be careful because it appears there are some 32-bit Windows kits.
https://forum.qt.io/topic/123027/installation-qt6-on-windows/7
If you try running them on a 64-bit Windows 10, they crash.
If this doesn't answer your question, you need to supply
Which Windows Version
32 or 64-bit
off-line or on-line installer?

Disable TortoiseSVN project Monitor

I installed TortoiseSVN on my work laptop (win 7 Ent.) and tried to integrate Tortoise with R-Studio. But because of some known issues (see here), I did not take it further and disabled subversioning on R-Studio. Since then, when I start R-Studio client, the Tortoise Project Monitor opens up automatically and takes R-Studio into initialization stage until it crashes and I have to kill R-Studio client.
After playing around for few hours, I learnt that I have to open two instances of R-Studio to be able to run it. So, now, I open R-Studio and let it go into initialization stage and then in the meantime, I open another R-Studio and the 2nd one works fine; then I kill first one. But, it is kind of annoying as the trick does not work sometimes.
I uninstalled R-Studio and reinstalled it again and no change. I am afraid if I uninstall TortoiseSVN and then cannot install it again- as it is an open source and there is no support team to help in case of any trouble.
Wondering if anyone has any idea on how to disable project monitoring at all. I don't really need it at all.
Project Monitor can be disabled in Project Monitor Options.

Can't start Cordova debugging to iOS simulator

I've followed the instructions at the link below to "Build and simulate a Cordova iOS app in the cloud". https://taco.visualstudio.com/en-us/docs/build_ios_cloud/
After completing the instructions I'm able to build and get the iOS simulator working, however, I'm unable to attach a debugger.
The message displayed in remotebuild is:
GET /cordova/build/5655/debug 500 10.865 ms - 28
In Visual Studio I see the following in the Debug window:
Starting launch process C:\Program Files (x86)\nodejs\node.exe "(redacted)\node_modules\vs-tac\emulator.js" --platform ios --action launch --path "(redacted)\buildInfo.json" --serverUrl https://(redacted):3000/cordova --certificateName (redacted) --language en-US --loglevel info --cliVersion 5.4.1 --npmInstallDir "(redacted)" --deployTarget "iPhone 5"
Timed out connecting debugger to remote Apache Cordova app. See Output window for JavaScript console output.
------ Cordova tools 5.4.1 already installed.
Requesting emulate on iOS Simulator for buildNumber 5655 on server https://(redacted):3000/cordova...
Emulated - Successfully sent to ios Simulator
------ Cordova tools 5.4.1 already installed.
Requesting debug on remote iOS device for buildNumber 5655 on server https://(redacted):3000/cordova...
Failed to Debug iOS remote for build (redacted)\buildInfo.json to https://(redacted):3000/cordova :
iPhone 5
My local development machine is using Visual Studio 2015 and Cordova 5.4.1. I have Node v0.12.2 installed locally and v0.12.9 installed on the MacInCloud. Following the instructions in the link above, I am NOT an admin on the Mac machine.
I've also already tried the instructions suggested in this SO answer: Visual Studio Debugger failing to connect to remote Apache Cordova app in iOS simulator
All the suggestions and the links provided by others were helpful but ultimately my assessment of the problem was not being admin/root on the Mac. The Visual Studio Cordova docs linked in my original question would suggest that you can do all that you need on a Mac without having admin/root access but in my experience that is just not the case.
To the credit of the MacInCloud group, they were very helpful in making changes that I requested to permissions and for reinstalling packages such as brew, ios-webkit-debug-proxy, remotebuild, etc... but after a while that back-and-forth kind of approach to fixing the issue proved painful. When I switched from a Managed MacInCloud server to a Dedicated one, everything worked almost immediately.
Looking back I think the initial execution of remotebuild, which executes brew -- without being admin on the box -- caused the whole process to go south. I was warned when I ran remotebuild for the first time that it would install some brew components that might need root access. That should have been a warning sign to me that not being admin on the box was going to be an issue...
Even though I was able to get a Dedicated MacInCloud server working, the lesson I learned about having control over the Mac prompted me to just buy a Mac Mini. That was a little more difficult to setup because I was now doing everything myself, but ultimately I think it will pay off in the end.
For anyone else struggling with similar issues here is a brain dump of some things I learned along the way:
You don't necessarily need to get Visual Studio talking to the Mac to debug Cordova applications. You can use Safari Web Inspector from the Mac. https://blog.nraboy.com/2015/10/debugging-your-apache-cordova-ios-app-with-safari/. Even though I finally got VS working, I actually prefer this because it is more like Chrome's debugger which I prefer to Visual Studio's.
The ios-webkit-debug-proxy NPM package mentioned in other comments and links is basically a proxy which Visual Studio uses to debug the simulator in exactly the same way Safari does as mentioned above. For this proxy to work you must also be allowed to connect to the Mac over ports 9221-9322. https://github.com/google/ios-webkit-debug-proxy. Prior to learning that I thought I only needed port 3000 open for the remotebuild proxy...
The package necessary for launching the iOS simulator from remotebuild is ios-sim and it will occasionally timeout when launching the simulator and cause the debugger not to attach. This is a known limitation. https://github.com/phonegap/ios-sim and https://blogs.msdn.microsoft.com/visualstudio/2014/11/13/tools-for-apache-cordova-update-ios-debugging-windows-8-1-support/ (see comments).
If you should feel the need to install/uninstall brew it is very easy to do. Just run the install script and if already installed it will give you instructions on how to uninstall. http://brew.sh/ and https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting. To uninstall or reinstall a NPM package is equally easy and Google is your friend.
Read and re-read both of these links for setting up a Mac: https://taco.visualstudio.com/en-us/docs/ios-guide/ and https://taco.visualstudio.com/en-us/docs/build_ios_cloud/. Getting the RemoteBuild.config right is crucial for getting secure connections to work -- especially if you want to access your Mac Mini at home from across the internet.
If you are remoting to a Mac I highly recommend iRAPP or some other VNC alternative. My experience has been that VNC is painfully slow and having a bad connection when you're troubleshooting issues just leads to more aggravation. http://www.coderebel.com/products/irapp/
As mentioned above, the MacInCloud guys were great when I asked for support, but if you do need root access for more than six months the cost of a Mac Mini is less than a Dedicated server plan.
Cheers
Since it is the call to /cordova/[...]/debug that is failing it looks like you might not have ios_webkit_debug_proxy installed. You could try making sure that homebrew is installed (from http://brew.sh) and running brew install ios-webkit-debug-proxy. Afterwards you should be able to run ios_webkit_debug_proxy without an error.
If that runs successfully then you should be able to quit out of ios_webkit_debug_proxy and debugging should work via remotebuild.

Visual Studio 2015 download getting stuck at applying Microsoft ASP.net

I'm currently on my third attempt trying to install Visual Studio 2015 on this computer. I have tried rebooting, hard shut downs, canceling setup and restarting, etc. Each time, it gets stuck at applying Microsoft ASP.net. I have tried leaving it overnight (12 hours). My download speed is 50-60 MBPS according to Ookla Speedtest. I am running Windows 10. I did do a "custom" installation and added C++, Python, and the Git extension. If I am not mistaken it said 7 GB size. Why is it doing this? Please help!
I don't understand why this isn't working because I installed VS 2015 for my laptop (a different computer) just a few days ago on a relatives WIFI and their speed was 3-7 MBPS.
(Note: The installer is not technically frozen since the loading dots on the bottom are moving.) However, bar hasn't filled up at all for like 6 hours.
EDIT:
Do I need ASP.NET (for C#, Python, and maybe C++)? Can I uncheck certain features for installation so that it wont try to install this? Also, when I cancel installation it never cancels and just stays there so I have to kill the installer with the task manager. This is getting incredibly frustrating.
Fixed it...
Easiest way is "threaten" to shut down the computer. Go into Power, restart system. You will be warned that there is a logging program which will not let the system reset. Cancel that program and then do NOT restart.
Installer immediately went on to next part and finished install after having been stuck for 6 hours...
I got it to work, it wasn't perfect, but here is what I did: It was getting stuck at very certain points, most notably ASP.NET. I did a little research and got an idea from something I read (I unfourtunetly can't find the source again). Sometimes windows opens invisible "confirm" type windows or installer windows that get stuck. When the installer got stuck I opened up task manager -> details, than checked On the visual studio process by right clicking then clicking analyzing wait chain. This showed me what process the VS install was waiting for. Then, I'd just kill the process. Messy, I know, but better then nothing. I had to do that 2 or 3 times. Afterward it said it installed correctly with 2 components that had warnings. ASP.NET was included. But everything else worked fine (c#, C++) Later I went back and did a repair. That worked pretty smooth. Finally, I installed the Python Tools successfully. (that part is sort of irrelevant but the point was that everything is now working fine).
edit, found another source: Visual Studio 2015 Community Edition Installation Stuck In Windows 10
Yes i had this problem too. To solve this open task manager and go to details tab then search for TiWorker.exe, right click on it and choose analyzing wait chain it will display many instances of the process that are in waiting mode , check all those processes and terminate them after doing this the installer will go to the next step.
To avoid this problem, you have to install IIS first.
Go to Control Panel -> Programs -> Turn Windows features on or off -> Select "Internet Information Services" -> OK
I had this problem a couple of hours before writing this answer and what worked for me was:
I opened other programs at least two or three and went to power and clicked on restart as usual it will warn you about open programs that need too be closed before shutdown or programs that are currently active I then clicked on force close and it closed the first program that I recently opened then I quickly clicked on cancel. Two minutes later instalation was back on track
Press Ctrl+Shift+Esc, then go to Tiworker.exe and terminate all the waiting processes.
I found a solution to this headache of a process to install Visual Studio. If you have tried everything and nothing seams to be working for you even by trying the command line shell then try this.
Go open task manager while running the installer and kill wusa.exe. It will kill the process to search for the update and continue the installation. You may have to kill some other processes as well if they get stuck. Its not great but it seams to be working.
wusa.exe seams to be the task that is the problem that prevents the installer from moving to the next step. This could be because your computer can not reach the update server.
This seams to be the case for both the Community and Enterprise Version of Visual Studio.

Resources