IPS says they can't help-trying to get past deactivated Nexus

[scorpion5005]

A disgruntled former business partner nuked our OS on a dedicated server, taking out the IonCube Loader (which I wasn't aware was required for Nexus, maybe I missed it in the docs and requirements) and, as a result, I lost a forum site that I had invested fourteen months of hard work into. Trying to get my IPB installation back to some point where I can access the admin CP, I tried to reload the IonCube but it didn't help get the forum back online, so I deactivated Nexus in my suite package at the next renewal. No sense paying for something I'm not using. Same with the 250 chat and everything else but a basic IPB install.

I can get to the folders and files on the server and edit them, but the software keeps trying to load Nexus. I can get to the SQL database and edit that, but I'm not that comfortable with doing anything there until I take care of any config files or ini's or other that might help solve the problem.

I submitted a support ticket to IPS to see if anyone could tell me where I could edit a file or files to remove any references or calls to the IonCube and Nexus, something that would give me control of the installtion again. I was told I had to reactivate (pay for) Nexus again, then install IonCube and maybe then I could get the forum running to a point where I could recover things. Aside from that, and suggesting I use a dB back up (which all backups were made with Nexus installed, so no good there) IPS says they can't help and I'm on my own.

Back in the early days of IPB, everything was handled in a few config files and something like this would have been easy to correct, without having to reactivate third party software and pay additional fees. Edit an ini or change a coupleo of lines in a php file and we were back in business. Now the software is spread out and, unless a user has dedicated time to follow the changes and code, it's almost impossible to know what is controlled where.

At this point, I'm making some backups of the mangled installtion as it sits now, then I'll start trying to remove anything that looks like it references Nexus. I'll try editing the dBase and take it out there. I'll use trial and error as long as I can until I either get it started again or admit it can't be saved. Unless someone else has some serious suggestions. I really really really don't want to lose fourteen months worth of work.

[Rhett]

Hello, the problem you have here is a catch22, you would need to disable or uninstall nexus for it to not be called by the system, so just removing the files won't solve the issue in this case. I would suggest you get ioncube working on the server, you can even use the easy loaders for this as well. Then uninstall it, and delete the files, then you should be good.

we can help you identify the files and even remove them for you, however with it still installed, that's likely to cause issues.

http://www.ioncube.com/loaders.php

http://www.ioncube.com/loader_installation.php

Your host should also be able to do this for you, if this is a self managed server, then you are likely on your own though, but the above links should help.

[Ae9803]

If you need help installing Ion cube, just ask here. Alot of us have experience doing it :)

[scorpion5005]

Do I have to do that? Maybe it's my Asperger’s, but once something like IonCube and Nexus (which wasn't an absolutely necessary part of my initial business plans, I just paid for it in a blanket decision) is used against me, or causes this level of P&S, it's off my list. Maybe at some later point, if it turns out it would benefit my community, but to start with, I really don't want it.

My specialty in IT problem solving is more on the hardware side and not software and coding, but if I have to, I'll muddle through this as long and as far as I can. I still believe it's possible to remove any IonCube and Nexus triggers from my install. It might take some work and a lot of time, but seeing that I invested fourteen months into prep for this rollout, what's a few more months? Sorry if removing a high retail value addition to the IPS suite is contrary to company philosophy.

[scorpion5005]

Yes, this is a self-managed server (5 years) that, until last month, was mostly handled by the former partner (his decision, not mine). Now that he is out and gone, I'm trying to clean up a lot of mess, both malicious and incompetent.

[scorpion5005]

One last bit, this isn't a matter of money. Reactivating Nexus and any other costs are incidental to my dislike for issues like this. My day job requires me to manage a Windoze 2003 server, a Windoze 2008 server and a dedicated MS SQL server for the USDoD. The foul-ups forced on us (sys admins) by Cyber are historically horrible and are routinely catastrophic, which leaves us on our own to correct and make whole again. I can't do much about that on the job, but on my own server, I can reduce the dependency on as many outside thrird party apps as possible.

[PeterUK]

You should just install the ionCube decoder which as others have said should help in your ability to uninstall it. It can be "used against you", all it does it decode ionCube encoded files, which Nexus is. If you are worried then install it, remove Nexus, and then uninstall ionCube, but many, many servers have ionCube installed and it doesn't cause any problems.

[scorpion5005]

Solved the problem, maybe just temporarily, but am accesing SQL tools in the adm CP now.

Thought about the whole thing and decided to do something I am a mite bit more familiar with; I recompiled Apache to upgrade to newer PHP version and installed IonCube in the new profile. Backed the entire server up before I started, let it run and voila, I'm in...at least for now. I'm going to have to sit down and read up on the management side of running a Linux server vs. the Windoze machines I admin at work. Last time I ran *nix was a lightweight LAMPP version some years ago. Started my MS work on NT4.0 and fell into this gig with Server 2003, 2008 and dedicated MSSQL. I usually spend half my day with my head down inside spreadsheets and access dBs, the other half buried inside a server rack or pulling fiber or cable to a room somewhere.

I guess this one is closed. I do appreciate the advice. I see not everyone thanks people who respond to these topics, but an old guy like me sees hope when people actually take the time to try and help others out. It kind of softens the troll static most assist sites have.