Not able to invoke REST APIs Sharepoint 2013 onpremise - sharepoint

I have deployed fresh SharePoint 2013 instance on VM. I am able to create Web-Application and Site-Collection successfully. I can even access my site, create folder, file through web browser.
However, I am not able to access REST APIs for the same site and getting below error. Please have a look on below snippet:
GET http://xx.xx.xx.xx/_api/web/lists
Getting error as "The Web application at http://xx.xx.xx.xx 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."
Please suggest.

are you using with host name or IP?
if you are using hostname, you should add new entry in hosts file.
Structure:
IP Host Name
xxx.xxx.xxx.xxx contoso
http://support.sherweb.com/Faqs/Show/how-to-edit-the-hosts-file-windows
Or
You can modify alternate access mappings.
https://learn.microsoft.com/en-us/sharepoint/administration/configure-alternate-access-mappings

Related

Unable to reach web site locally on Azure web role

I am deploying multiple web sites on Windows Azure cloud service on Single web role. I have added required binding and host file entries. when I run ping command I am getting the response as well.
However when RDP to VM and browse the site locally on VM as localhost
it is not reachable and showing 404 not found.
Error from IIS events
The application '/' belonging to site '1' has an invalid AppPoolId 'DefaultAppPool' set. Therefore, the application will be ignored.
when RDP to VM and browse the site locally on VM as localhost it is not reachable and showing 404 not found.
I access the desktop of your web role running in Azure and add a new Web site to your Web server, I can browse the site locally. If possible, you can try to create a new web site to server static html files and check if it works fine, or you can share us the detailed information of bindings and your application.
Add a website:
Settings:
Application pool:
Browse site locally:
The application '/' belonging to site '1' has an invalid AppPoolId 'DefaultAppPool' set. Therefore, the application will be ignored.
Some community members encounter and post similar issue in this so thread, you can check if any .dll files are missing or 32-bit libraries are used.

IIS authentication error

I'm trying to simply run a local website which has sime basic HTML files using IIS.
Through the IIS Manager I have created a new website and have set the physical path to the directory with the HTML files.
However when I input the physical path I get the following warning:
The server is configured to use pass-through authentication with a
built-in account to access the specified physical path. However, IIS
Manager cannot verify whether the built-in account has access. Make
sure that the application pool identity has Read access to the
physical path. If this server is joined to a domain, and the
application pool identity is NetworkService or LocalSystem, verify
that \$ has Read access to the physical path.
Then test these settings again.
Now, when I navigate to the site through localhost I get the following Unauthorized error:
You do not have permission to view this directory or page because of
the access control list (ACL) configuration or encryption settings for
this resource on the Web server.
What's going on here? When I right click my folder I seem to have given access to everyone. I haven't made any specific IIS changes so what could be the issue here?
EDIT:
MAN I cannot believe this. My case is so simple (I just wanna display some HTML files on localhost) which should require ZERO configuration at all. Yet IIS fails to meet the demand.
EDIT: I think everyone should have permission to my folder. Here's a picture of the permissions screen for the folder:
Working with a set of server protocols is different than adding files to a share. In this case, you're going to want to open IIS and navigate to the website you added it as.
There, you'll see a variety of icons, some under the heading of ASP.NET, some under IIS. The first heading you'll see under IIS is Authentication. That's the one you want. If this is strictly internal/for learning, go ahead and enable Anonymous Authentication. It's not safe, but it'll get you in the right place to start googling around.

Remote machine accessing a deployed SSRS report

I have created an SSRS report using the Business Intelligence reporting service of VS 2012 and I have also successfully deployed it on the web service url i.e. http://computer name/ReportServer, the deployment was successful. The main purpose of deployment is to enable the client to access these reports from their machine, and I really do not have much idea on how to proceed with that, what and how do I give permissions to the client and how does the client access the above url in order to view the reports? Please elaborate I was not able to find much online help on this and its my first venture in this domain. Thank you very much in advance!
Open Reporting Services Configuration manager from windows Start
Connect to your Report Server
basically Two ULR tabs are available there
Web Service URL
Report Manger URL
you want to go to Web service URL
assign Some virtual Directory then use that URL for client PCs.
if not work use IP address in place on Computer Name
for credentials use Service Account Tab in this Manager
check Use another account
and what ever domain username is given here will be used for client to log in .
i Had same issue, i jst replaced computer name with deployed server IP address,
http://10.60.0.0/ReportServer

FTP access into Azure where there are two Websites

I have 2 web sites in my Azure account and I would like to access the second one via FTP, however, when I load up the FTP site I am getting the FTP area for the first site and I cannot see any data for my second site.
My first site is a straightforward web site, but the second is an Orchard template. I was expecting to see the Orchard folder structure when I accessed the FTP area but seems only the first site is accessible via FTP.
I have looked at other threads about setting up your own FTP but I would like to avoid doing that until it is absolutely necessary.
So my question: Does anyone know if the Orchard website, generated by Azure, is accessible via FTP, or to get access can I safely reset the credentials from the dashboard on the second website so it has its own FTP area via an individual set of credentials?
I believe the username you use for FTP should be <web site name>\<username>, so you should already have different credentials for the two sites. Can you confirm you're using the right credentials to try to access the Orchard site? Check the "deployment user" on the right-hand side in the portal and make sure you're using that.

TFS SharePoint default collection site not accessible from public IP

I need the community's help on this.
We have TFS 2010 and SharePoint services installed on a server in our internal network and I can access it fine via servername/sites/DefaultCollection/.
We're trying to give access to external teams to the same site.
When we try to access publicIP/sites/DefaultCollection/
we get a 404 NOT FOUND error (publicIP points to the IP of the TFS server).
I noticed that in Team Foundation Server Administration Console in the [General] tab is says:
DefaultCollection URL: servername:8080/tfs/DefaultCollection/
While at the [SharePoint Site] tab under Default Site Location shows: servername/sites/DefaultCollection/.
When I try locally servername/tfs/DefaultCollection/ I get the same error (404 NOT FOUND).
So it seems like when we try to visit publicIP/sites/DefaultCollection/ it actually goes to publicIP/tfs/DefaultCollection/ without the address changing on the browser.
How can I make this work?
Any help will deeply appreciated.
Have you set up alternate access mappings in Sharepoint?
Go to Administrative Tools -> Sharepoint Central Administration.
Click on the "Operations" tab
In the "Global Configuration" section, select "Alternate access mappings"
Select "Edit Public URLs"
There you can add a new URL for the "Internet" site so that external users can access Sharepoint. Note that this URL may need to be a fully qualified domain name, not an IP address. (However I've never tested with an IP address.)

Resources