I have made a new web application on sharepoint foundation 2013 using the steps mentioned in link below.But when i try to access it using both server and client i get the message "401 UNAUTHORIZED".what to do?
http://sharepointgeorge.com/2012/create-web-application-site-collection-sharepoint-2013-preview/
I made it on a client pc having rights of administrator.I have tried quite a few thing by changing iis settings but this problem is not getting solved.Any help would be greatly appreciated.
Do you have kerberos enabled in this environment? If it's not configured correctly, this behavior can happen. You might check your logs to see if there is any additional information.
Related
I set up an office web apps server 2013 in windows server 2012 R2, it is good to open this link http://localhost/hosting/discovery, means the office web apss server 2013 is running well.
But when I tried to open this link http://localhost/op/generate.aspx, it gives an error : A big red X, server error sorry for the mistake. We have recorded an error for the server administrator.
I was looking for some blogs, somesay that is causing by logging in the website with the system account, but I dont know what is the system account, and is that logging means the iis service?
I am not use WOPI and sharepoint, what I want is only use office web apps server 2013 to provide view & edit doc and docx files in browser.
Please help, thanks!
PS. If the question not meet the requirement, comment it, I will edit it.
eidt 1 :
I had solve this problem, I had installed AD and OWA in one server.
Install them in different server will ok.
But there is another problem :
When open a word file, It gave an alert:
Microsoft Word Web App
sorry, some problem had appeared, cant open this file.
How to fix this ...
update :
I finally solved it by changing another server to install OWA.
If you want to be able to open documents from UNC paths then run the following command in the PowerShell on your OOS/OWA machine.
Set-OfficeWebAppsFarm -OpenFromURLEnabled
If you need to connect your OOS/OWA to a WOPI host (SharePoint or a custom host) then http://localhost/hosting/discovery is a good enough indication that the instance works fine.
I've installed SharePoint Foundation on Windows 7 Home Premium using the tutorial at:
http://msdn.microsoft.com/en-us/library/ee554869%28office.14%29.aspx#50
Everything went well except for the last step when I actually try to load either the site or Central Administration. Instead of a Foundation website, only a blank page appears.
I tried without success the suggested solution to change IIS -> Authentication -> Basic Authentication to Enabled.
After this change it was necessary to enter a username and password when trying to access a Foundation site. Unfortunately, after entering correct data a "Server Not Found" message appeared and I was not able to proceed.
Any ideas?
Thank you for your time,
Ben
1st step of troubleshooting this is to take SharePoint out of the equation. Setup a new web application in IIS, put in a simple 'hello world' type static html page and try and load that. If you can't then the problem is IIS/networking and not SharePoint.
For what it's worth, I've found a way to install SharePoint Foundation 2010 on Windows 7 Home Premium and solve the Windows Authentication issue (you CAN actually enable it on Home Premium as well - it's just a manual process, that's all).
You can find the steps I followed on my blog at http://www.rl-soft.com/en/blog/Lists/Posts/Post.aspx?ID=21
Hope this helps a few folks!
Raphael.
I'm getting the following error while trying to create a SPSite instance (not open it, just create it):
"The Web application at <URL> could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application."
I have SharePoint Foundation 2010 installed on x64 Windows 7 laptop and VS 2008. I've done a lot of searching the last couple of days and I've tried any suggestion there is:
Setting user permissions to the database.
Targeting the application for x64 CPU.
Running my app with the sharepoint app pool account. Creating new app pool.
Creating windows forms and console applications to run the code from there.
Adding and removing the web application administrators.
Checked the logs (nothing in there).
Writing the URL in full, with machine name and with IP.
The funny thing is that the same code was working fine at one point and then just stopped. I cannot recall to have done anything special to damage it.
Any help will be much appreciated.
Regards,
Martin
To answer my own question the sharepoint site had to be on the default port - 80. Publishing it on any other port and trying to access it by putting the port in the URL did not work. Strange but it worked.
I setup a test box computer with server 2008 (standard edition, not R2 and not hyper-v editing). I then installed SharePoint 2010. I was amazed how easy the whole setup went (the prerequisites setup on the SharePoint disk made this process oh so easy – great install system). Really this was just so easy.
This test box is being used for testing Access web services. I am able to well publish access applications to this test server and Access applications publish and run just fine on the web SharePoint site through an web browser.
However, the only thing that does not work is when I launch a Access report. The error message I get back is
This report failed to load because session state is not turned on.
Here is a screen shot:
I can’t seem to find the setting anywhere to turn session state on. Any hints or links on how to enable session state in SharePoint 2010 would be most appreciated.
On Todds blog you can find a post which explains how to turn on session state in SharePoint 2010.
Here is the solution:
http://geekdeck.com/sharepoint-2010-this-report-failed-to-load-because-session-state-is-not-turned-on/
Probably not in SharePoint head over to the IIS configuration and see whether session state is enabled there. I am not aware of anything in the SharePoint forms (I did set up 2010 on the weekend) that indicates session state. And as session state on farms is an administrator action (state server etc.), maybe they simply did not activate it?;)
I have installed MOSS 2007 on Windows Server 2008.
I am facing a strange problem:
I am unable to logon to SharePoint using IE 8, but am able to using Firefox. Pl note that I have taken care of the security in IE.
After creating a web application, when I try to chage the web application for creating a Site collection..I am unable to change it (even if I select the web application it says "No Selection".
I am unable to add web parts to any of the sites created! ( Pl note that I have created the sites by using a workaround..changing the SiteId=null to site Id = Id of the Site using SharePoint Manager)
I find no entries in the logs or no error messages..
Please help me in this regard.
Grace
IE8 on Windows Server 2008 is much more stringent with its default security settings. Even disabling IE Enhanced Security Configuration does not allow all functionality. This is to discourage you from logging into the server and perhaps inadvertantly installing an IE addon that compromises security.
You really should connect to SharePoint Central Administration from your local machine. Then you won't have the security problems and also will be following Microsoft best practice.
Try adding the Site (Central Admin ) to the Trusted Site in IE and Make the Security Setting as Low. It will give all the Required stuffs like Javascript and it should solve your issue.
I have also had the same problem, not being able to select a web application. In our case we ended up reinstalling sharepoint (actually a clean install of the OS), then it worked fine.
There was probably some step in the installation that we did not do in the correct order.
Installing Sharepoint on Windows Server 2008 is not a regular install. Make sure you have the latest Cumulative update installed + SP2. Better yet, slipstream the installation.
Take note, especially when installing Language Packs attention is need when performing the install, there is a specific order in which to install the product / updates / packs.
More info Code eater blog post
You may need to disable the loop back checking if the site is using a host header name. See this article for more details.