MCOM_Nexplorer_15 Installer only

[Weiland86]

Hello mates,

Just in case someone can provide med for this 2 great tools, i am sharing latest installers

MCOM_Nexplorer_15.txt

[babak1349]

Hello mates,

Just in case someone can provide med for this 2 great tools, i am sharing latest installers

MCOM_Nexplorer_15.txt

hello,
still the old solution with a bit change , works. you need to have ,.Net framework 4.0 to run the tiny program to get the lic string
1) inssall NeXplorer or MCOM
2) copy "license.dll" under ..../RNS Tools/197
3) run the lic generator and set the project name and choose the program you wang and generate the lic

cheers

[striker]

hello,
still the old solution with a bit change , works. you need to have ,.Net framework 4.0 to run the tiny program to get the lic string
1) inssall NeXplorer or MCOM
2) copy "license.dll" under ..../RNS Tools/197
3) run the lic generator and set the project name and choose the program you wang and generate the lic

cheers

Hi babak,

Have u tried running the installers without affecting
The SQL of actix.I've been trying to make it work but
Spotlight and analyzer repository will have a problem
. Can somebody tell me here successfully using it
Without affecting the actix SQL.. Thanks

[babak1349]

Hi babak,

Have u tried running the installers without affecting
The SQL of actix.I've been trying to make it work but
Spotlight and analyzer repository will have a problem
. Can somebody tell me here successfully using it
Without affecting the actix SQL.. Thanks

hello,
about Actix, I think you are using version 5 ? right ?
It seems there is bug in it and it fails when you load log files on repository Even some guys who is not using Nexplorer and MCOM reported it So they got back to Actix 4.5
Normally I don't use MCOM but you can look at my previous thread abuot Nexplorer somebody commented about problem of MCOM with SQL So it might help you to fix it

Cheers

[striker]

hello,
about Actix, I think you are using version 5 ? right ?
It seems there is bug in it and it fails when you load log files on repository Even some guys who is not using Nexplorer and MCOM reported it So they got back to Actix 4.5
Normally I don't use MCOM but you can look at my previous thread abuot Nexplorer somebody commented about problem of MCOM with SQL So it might help you to fix it

Cheers

actually there is no problem with version 5 the issues is when installing MCOM or NExplorer it will affect the repository ang spotlight of actix..maybe is still not possible..

[Weiland86]

Hello babak1349,

does this solution works for win7 x64?
thanks in advance

hello,
still the old solution with a bit change , works. you need to have ,.Net framework 4.0 to run the tiny program to get the lic string
1) inssall NeXplorer or MCOM
2) copy "license.dll" under ..../RNS Tools/197
3) run the lic generator and set the project name and choose the program you wang and generate the lic

cheers

[babak1349]

Hello babak1349,

does this solution works for win7 x64?
thanks in advance

hi
I installed it on win 7 X64 as well
cheers

[babak1349]

hello,
about Actix, I think you are using version 5 ? right ?
It seems there is bug in it and it fails when you load log files on repository Even some guys who is not using Nexplorer and MCOM reported it So they got back to Actix 4.5
Normally I don't use MCOM but you can look at my previous thread abuot Nexplorer somebody commented about problem of MCOM with SQL So it might help you to fix it

Cheers

Hello Striker,
A friend of mine was telling me about experience which he has had with Actix, he was saying Actix 5 is using SQL server 2008 and, if you have SQL server 2005, actix will not install the required entity of SQL server 2008 and in this case you might face problem during loading logfiles and also creating repository, he was suggested to uninstall SQL server 2005 and actix and reinstall Actix and sql server 2008 ( which has better performance)
Now the question is about MCOM which tupe of SQL server it uses , if you have SQL server 2008, it does install SQL server 2005 ? It should be tried

PLEASE KINDLY NOTE if you follow the above mentioned potential solution, any failure or risks will be on yourself. I am just sharing what I heard
Besides I experienced before uninstalling SQL server could be risky as it might affect other program's whch are using it

Cheers