we followed the article at http://support.microsoft.com/kb/927675/en-us to implement the pdf filter for wss 3.0.
But the registry entry mentioned on step 2 (adding a new entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\GUID\Gather\Search\Extensions\ExtensionList) is lost if we reboot the system.
Does anyone have any idea why that might be happening?
We installed the adobe reader 10 and tried to configure the pdf filter for wss 3.0
Ok, found the problem. After changing the registry you have to stop and restart the share point search service. No idea how they are related tho!
Following are the commands:
net stop spsearch
net start spsearch
Related
I have a problem regarding White Screen Of Death (WSOD) at my site.
I will try to explain what I have tried until now.
I know it is not a triviel error to debug, but maybe some of you have tried something similar.
Here is the setup: One Windows Server 2019 v1809 with one IIS: 10.0.17763.1.
Multiple websites with associated application pools.
It's a MVC solution, and we are using .net 4.7.2.
What I have tried:
Recycled application pools every night
Restarted the server every night
Issued a IISReset every night
Deleted temporary files in C:\Windows\Microsoft.NET\
Looked at the IIS logs
Looked at the application log, our own log
Looked at the Windows log
Searched the Internet for similar problems
Made sure there always were some traffic at the website
Made sure no errors were shown when pressing F12 in the browser, the site always returs code 200
The WSOD comes at varies times, and not all the sites are affected at the same time.
A manuel recycle of the website always helps.
My question is, have any of you encounted similar problems?
And how did you solve it?
If you need more information please ask, and I will try to provide it.
/Regards Søren
This kind of problem is very unusual in IIS, because there is almost no record and useful information in the log file.
You can try to use this plan to repair IIS.
Unregister all the versions of ASP.NET with command "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ua". and the framework 64 also versions. 3.0 and 3.5... etc
Delete ASPNET account from "Local Users and Group – Users".
reregister ASP.NET with IIS using "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –i". and framework64... net 3, 3.5 etc
Give permissions to the ASPNET account using "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –ga machinename\ASPNET". for framework 32 and 64 and versions.
Reset IIS .
I am new to Linux command line and setting up Magento 2.1 on my VPS. I am thinking to setup Nagios on subdomain so i don't want any interruption on my actual domain ecommerce application.
I have few doubts which causing lot of trouble to me.
By default Zpanel comes up with lower config for Php and Mysql and to make them work with Magento 2 i have to manually upgrade them . I did that but Magento worked, whole Zpanel navigation stopped working. So i re-installed whole ubuntu Os again and ready with my box. I would also like to have Varnish Cache along with some web based console so that i can easily manage my virtual hosts and for some other stuff.
What will be the best approach to setup everything one by one on one domain/sub-domain? I have found so many articles to install magento 2 on ubuntu using command line but they dont use any webpanel. I am open to switch it to any other OS as well.
If there is sequence to setup these all, please guide.
Final Requirement:
Magento 2 with any Linux OS
Nagios server for monitoring
Web panel like CWP or Zpanel etc.
This question will be complete solution and will helpful many other users as well. All answers are highly appreciated. Thank you all in advance.
Regards
H
We are looking at upgrading from Kofax Capture 8 to 10.
Currently, our Kofax Capture 8 installation on a single server with 3 connected client scanner workstations.
When going to Capture 10 can we use the same single server setup as with the current installation? or install new kofax server in new VM and then copy the batch class and batches into the new server?
What are the things we need considering while upgrading?
Anything that individuals can comment on that would help us (do's -don'ts) would be appreciated?
Thank you.
Since you're in a virtual environment and with a fairly small number of stations, I suggest you create a snapshot of the server (VMWare and Hyper-V both have this feature) and do an upgrade with the Kofax installer (start installing on KC 10 on the server and the installer will notice that an old version is present and will prompt you for upgrade).
If the upgrade goes wrong then you can revert to the snapshot you created and start over as if nothing happened.
Once the server is OK, upgrade the stations by running the installer from the WrkInst folder on the server. Try on a single station first, and if that works, roll out to the rest.
When going to Capture 10 can we use the same single server setup as with the current installation?--- use can use the same single server.
Things you need to take care of are.
Your configuration path for importing the batches might get change.
Check for the DB connection.
Dictionaries and database path you might need to change again.
check your export connectors mapping they should not be effected in case they are you need to map it again.
Keep a snap shot of things when your installing and have backup taken of project fpr file and batch class so that you can roll back to older changes.
I have a deployed a web application in IIS. Which used to work without any issues. Recently i have shifted that web application to another machine, Here is the problem. Once i setup the Webapplication when i opened the default document in IIS im getting the File not found error as following
Internal Server Error
\?\C:\inetpub\wwwroot\application\web.config
I have no clue why the IIS is not able to find the web.config. The file is present in the path C:\inetpub\wwwroot\application\web.config but the IIS is looking in the path \?\C:....
Please let me know how to resolve this??
Firstly this is documented on support.microsoft.com so I would suggest that anyone who has this issue read this first as it covers a number of solutions which I won't
Now from personal experience I encountered this error after setting up a new development machine. What I had forgotten to do was install the Url Rewrite 2.0 IIS module. Sadly the IIS error gives absolutely no idea that this is the actually issue.
Therefore to solve this issue investigate the system.webServer setting in our web.config and ensure that you have installed all the iis modules that you use. I did this by systematically removing elements from my web.config until I came across the cause.
In my case, I was running ASP .NET Core website so I had to install .Net Core Runtime from
https://dotnet.microsoft.com/download/dotnet-core/current/runtime
I know it's old post but I resolved the same issue as follows:
If you are using TFS and you are getting this problem then Reason is ".vs" file is not excluded from commit.
Because of that ".vs\config\applicationhost.config" gets the local version of another user/Developer.
To Solve the error, First open that file Update Physical path inside "" xml tag.
Also ask user to exclude this folder from TFS to prevent future issues.
If you are getting mysql localhost error. What I will do will work for you.
Control Panel(View by: Large Icons) >> Programs and Features >>
(Usually upper left corner) Turn Windows Features on or off >>
Internet Information Services >> Web Management Tools and World Wide Web Services
After Restart.
I am working SDL TRIDION 2011 SP1 version. Suddenly I am unable to see the Trdion site in Internet Information Services(IIS) Manager. Please tell me the procedure how to get it back again.
Remove Tridion Completely (uninstall), then run the installer again.
You won't loose any data (it's all in the database), and you're likely to get your server up and running way faster than trying to fix by hand.
As #bart suggested, your best option to get the web application back (assuming it really has gone), is to run the repair option with the installer. There are a lot of folder specific settings which would be very hard to recreate manually.