Currently we are trying to setup a server IBM Rational Clear Case 9.0.1 and can anyone help with pre-requisites for this setup and what all we need to install to make this code repository working.
The main documentation remains the IBM Support - Rational ClearCase 9.0.1, which does include prerequisites like:
Installing IBM Installation Manager 1.8.2 or later
Installing ClearCase,
Or: Upgrading ClearCase.
Related
I have downloaded the dnn version -9.4.0 install package from url -https://github.com/dnnsoftware/Dnn.Platform/releases/tag/v9.4.0 and configured that with IIS server but it's not running.I am getting compile time errors.
According to it's release document I have upgraded .net framework (4.7.2) in my system as well.
Same Install package for ver-9.2.2 I have downloaded then configured that in IIS and it's running proper.
Can you please confirm me about the issue in 9.4.0 ?
Can you give a few more details?
As an aside, you might want to check out nvQuickSite as an aid in installing DNN.
There were some issues with 9.4.0, but mostly about upgrades. Please try to download and install 9.4.1 which was released recently and addresses these issues.
I attempted to upgrade my tcms-api library from 5.0 to 5.3 using:
pip install tcms-api --upgrade
on a Windows 10 machine, I saw a lot of errors when trying to install the dependent package of kerberos. Even though this is old, I saw a similar set of errors. The package installation failed since the kerberos package isn't supported on Windows and I was left at tcms-api 5.0.
Please file a bug against https://github.com/kiwitcms/tcms-api.
We can do a quick fix by providing 2 package names:
tcms-api and tcms-api[kerberos]
The first one will not install the kerberos package.
The proposed workaround makes sense but changing the underlying kerberos implementation needs careful testing which isn't a quick job.
OTOH https://github.com/kiwitcms/python-social-auth-kerberos uses gssapi which seems to be the latest and most actively maintained implementation of Kerberos for Python. There is an open issue to migrate to that in tcms-api so you can contribute if you want.
As a workaround, I was able to do the following (caveat: I haven't extensively tested my installation yet):
Clone the tcms-api repo from GitHub
Edit setup.py to change the install_requires line to use 'kerberos-sspi' rather than 'kerberos'
Install the following pip packages: Setuptools, Wheel, Twine
CD to repo folder and run: python setup.py bdist_wheel
That creates a package under the dist folder
Run pip install dist\tcms_api-5.3-py3-none-any.whl
Celebrate successful package install
The steps were modified from this page.
Update:
I confirmed the things I need the API to do work with my custom package (create and update test runs). However, I'm in a situation where I don't need to specifically harden my Kiwi instance using kerberos authentication.
when install mongo database on windows 7
is not complete instillation
image of the problem
how to solve this problem
I too have the same issue while installing mongodb-win32-x86_64-2008plus-ssl-3.6.3-signed.msi
Follow the below steps to resolve the problem
Run the installer with a double-click.
Click next.
Accept the License Agreement.
Select the Complete installation type and click Install
Uncheck the Install Compass option (by default this checked and Compass requires the Microsoft .NET Framework version 4.5 or later)
With in a minute time installation will get complete and you can see the exe files under C:\Program Files\MongoDB\Server\3.6\bin
You can follow the url https://docs.mongodb.com/compass/master/install/ for installing Compass (The GUI for MongoDB) later.
I tried following this but with no luck.
http://blogs.msdn.com/b/sqlphp/archive/2012/06/08/introducing-the-microsoft-driver-for-node-js-for-sql-server.aspx
Every time I try to build it, it fails.
Does anyone have any ideas as to why does it fail to build. I am also using the latest version of Node if that helps.
Thanks for your question. Just to clarify you are using the msnodesql driver right?
One of the reasons that you might not be able to build is because you are using the latest node version.
The Microsoft Node.js driver is not forward compatible. The next version is in the pipeline. In the meanwhile you will have to downgrade your node.js version to 0.8.9.
Additionally there are a few other requirements. Follow these steps and you should be good.
Node.js – Version 0.8.9 (32 bit version). Make sure you download the x86 version and not the x64 version. You might have to uninstall your current version and re-install this version to ensure compatibility.
Python 2.7.6.
Visual C++ 2010 - the Express edition is freely available from Microsoft.
SQL Server Native Client 11.0 - available as Microsoft SQL Server 2012 Native Client found in the SQL Server 2012 Feature Pack.
Then just enter these in your node.js command prompt
1. npm install msnodesql
2. npm install -g node-gyp
3. node-gyp configure
4. node-gyp build
You should now see a build folder inside msnodel.
Navigate to build > release. Copy the sqlserver.node file and paste it in the msnodesql > lib folder. Replace the old file if needed.
Now you can follow the rest of the instructions on the blog you mentioned which will help you with connection string and connecting to your db. Let me know if you are still stuck.
Thanks
I am attempting to install the Master Data Services Plugin for Excel, but can't get the install to actually process due to it saying the prerequisites are not installed:
I have made sure I have the right version (32 bit) to match my version of excel (2010), and have the full version of .net 4.5 installed. If I try to install the full version of .net 4.0, I am told that the newer (4.5) version already is installed.
Here are some links with similar issues, but no response:
Microsoft Answers; Microsoft Connect;
Has anyone else faced this issue and got around it?
So, this looks to be a simple fix. The installer needs to be run as administrator, but in order to do that you have to run it through the command prompt as administrator. After doing this, it installed ok.
I'm not sure why the installer didn't request elevated privileges, but I'm guessing it couldn't properly query the system to verify the necessary prerequisites were installed.
Hopefully this helps someone else in the future!