We restored from backup twice and the same issue happens no matter what. So that was 2 months of 24 hours indexing. For some unknown reason, the index was corrupted and it could only recover to that point. Except our index files went from 11.5 GBs to 5 GBs. He reboots, finishes up the RDP issue, and bam, we're back in action. While fixing it, one of the SAs had to reboot the server. I had to stop people from being able to run Copernic that weren't that one account, or it would break every time someone would log in. We spent weeks trying to figure out why Copernic would only work at random times. Which wouldn't be a huge deal, except Copernic runs on startup by default. Presumably because they both try to run off the same port, which causes conflicts and doesn't allow the clients to search. Since Copernic isn't real server software, you can't run more than one instance on the server.We had issues where someone would log into the account and then log out and everyone freaked when search stopped working. Which means the account that runs this has to stay logged into the server forever. The desktop GUI has to be open all the time for the clients to work and for the indexing to continue. So if you map your data to D:\ on the server, but your client PC already has a D:\ drive, you're tough out of luck. But to view those files, you have setup a shared drive on the client to the server with the same drive name as the drive name on the server. When you perform a search on the client, it connects to the server and shows a list of files in the index. Copernic doesn't send the data down to the client as you would normally expect.If the account Copernic is running under doesn't have full access to the folder, it hard crashes.So I had to lookup a config on a client and paste the node onto the server config. And since it's XML based, the path was contained in a node that I didn't have the name to. I had to manually edit the config file to get it to run again. But it crashed immediately because it couldn't find the non-existent path. We were having issues with the drive path for the indexing, so we deleted the value from the software and restarted it. Copernic has no checks for missing configurations, common errors, etc.Which doesn't work super great either and requires us to reset it every now and then. In order to connect to a remote drive, we had to purchase 3rd party software. So it can't connect to remote drives and what not. Copernic is desktop software first and foremost.The idea was that they would have a service running on the server doing the indexing and then we would have clients connect to the server to pull down data. They recommended we use Copernic to index support files like patches, docs, etc. The company I work for hired a company as our ERP support provider. The secret to the program's speed lies in the fact that it creates a complete index of your hard drive the first time you run it, and its content is constantly updated so that the program log always contains information about all of your PC's files and their locations.Ĭopernic is compatible with the Outlook Express, Microsoft Outlook and Mozilla Thunderbird email managers and with the Microsoft Internet Explorer and Mozilla Firefox browsers.It's probably fine for personal use, but even then, just use Everything. You can also access your Internet data, such as your website history, favorites, contacts, emails. This won't be a problem any more thanks to Copernic Desktop Search, as you can use this practical utility to find any document, email, image, or multimedia file on your PC in a matter of seconds. If you have a drive that is full of files and a processor that's not very fast, the search can take forever. More than once, you've probably searched your whole hard drive for a file without getting the best results.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |