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
Related
In my company, a few ports are blocked and I am unable to identify a list of ports to tell my IT team to whitelist.
I am using Visual Studio 2015.
The reason why I am being so specific on ports is that, these steps I have followed at my home machine & I found no issues. The problem is only in my company due to Proxy/Port/Firewall.
Steps followed:
I have created a sample MVC Web application & kept authentication as default (Individual User Accounts).
After creating this application, I right-clicked on the project & clicked on Configure Azure AD Authentication & followed the steps properly.
I created a few users in Azure Portal and ran the application which is working fine.
Then I deployed the application on my local IIS by changing connectionstring (which got created in Step 2) from localDB to SQLExpress
The application isn't working after deploying on local IIS in my company but working on my home machine.
I am unable to identify the ports/proxy settings which I need to tell my company to whitelist.
Please help me. Thanks!
Have a look at the Hybrid Identity Required Ports and Protocols documentation, find your scenario and see the ports needed for that.
The following document is a technical reference on the required ports and protocols for implementing a hybrid identity solution. Use the following illustration and refer to the corresponding table.
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
In our current Production Setup, we have setup SSRS and have been able to successfully use the SSRS reports in our .NET Web Application since years. We have used Impersonation in Web.Config (there might be other solutions available, we had to go with this) as shown below.
<identity impersonate="true" userName="domainname/username" password="password"></identity>
This solution worked well becuase our Active Di
rectory and SSRS server are located in the same Network / domain.
Now, as part of our Azure migration, we have migrated our SSRS server to an Azure VM. and we are able to view the reports using Report Server Manager within the VM. Now, when we access the Web Application (App Service - Web App), we are getting the following error. Below is the updated impersonation attribute that we have used.
<identity impersonate="true" userName="username#ouremailaddressdomainname.onmicrosoft.com" password="password"></identity>
"Could not create Windows user token from the credentials specified in the config file. Error from the operating system 'The user name or password is incorrect"
Obviously, this is because of the fact that we don't have a Active Directory domain setup in Azure. Below are my questions.
Can we utilize the users available in the default Directory that gets created on Azure?
If yes, how do I specify the impersonization?
Thanks,
Prawin
With your planned setup you cannot use identity impersonation. This is because the AppService Web Apps do run in an isolated sand-boxed environment which cannot be part of a Windows Domain.
You have couple of options:
Change the reporting server to use mixed mode Authentication and create local for the SQL Server login and user with appropriate permissions. Then configure your reporting application to provide these SQL Server credentials
Move your Web Application to same VM (will not require Domain environment) as your Reporting Server (or just the part which deals with the reports)
Move your application to a separate VM and utilize the Azure Active Directory Domain Services to make the VMs part of same domain (an overkill IMO)
I would vote for the first option, as it requires least changes and leverages PaaS services (App Service). Everything else is overkill or just an abuse of the cloud platform.
I created few web applications for the one app service plan. For all these apps I am seeing one FTP url. Issue is that when I go to the URL, I can see one "Site/wwwroot" folder which only shows one application.
Isn't is possible to access FTP of other web applications?
All applications works fine. I don't understand how this FTP is being created. If it's showing just one application in FTP, what criteria is based on that? I am seeing the 1st application based on the alphabetical order.
The FTP Url is same for all the sites in a stamp and will be same even if you create multiple app hosting plans as long as the hosting plans are in the same stamp. A stamp is a collection of servers and roles in a particular datacenter.
So how azure connects to the right site - the distinction here happens when you provide the user name for the site that you are trying to connect. The user name has the form sitename\$sitename when using publish credentials and has the form sitename\username when using deployment credentials and this name is used by app service to identify which site you are connecting to.
http://weblogs.asp.net/bleroy/azure-web-sites-ftp-credentials has more details.
Also read https://github.com/projectkudu/kudu/wiki/Deployment-credentials to understand difference between the two kind of credentials.
So just specify credentials in this way and you can connect to your sites using ftp.
Hope this helps
Help! When I try to creat a web site on Azure, I receive the following error message:
There was no endpoint listening at https://geomaster.azurewebsites.windows.net/subscriptions/2762018c-1ace-4b11-a55d-7b69d004cca3/webspaces/eastuswebspace/sites that could accept the message.
I was able to create 2 sites about 3 months ago without any problem. My subscription is an active pay as you go account. I'm not trying to do anything advanced, just a web site connected to a SQL DB. The SQL DB creates without a problem. I was also able to create a virtual Win2008 machine. Azure reps have said my account is fine. I don't know where else to look. Thanks
-ph
If your development machine is behind a proxy server, the problem could be caused by the machine's proxy server settings. Have a look at them via Control Panel / Network and Internet / Internet Options / Connections tab / Lan Settings and try checking the box for 'Automatically detect settings' if it isn't.
Solved: Azure Problem - There was no endpoint listening at that could accept the message
Windows Azure Package Deployment Failed with Error - "There was no endpoint listening"
Same for me. Seems they simply do not have enough recourses atm.
refs:
http://social.technet.microsoft.com/Forums/windowsazure/en-US/611545bc-a061-4107-9240-597b60131b8b/error-creating-azure-website
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/389cba4f-8943-4f56-8b0e-9f9066154337/error-creating-azure-website