SignalR notifications not working. Is IIS required? - asp.net

I am trying to execute a sample demo SignalR application as shown in this post.
When I am making database changes, notifications are not shown on browser. It remains a blank page.
Is IIS installation required for SignalR to work?
I am building on VS 2013 Community Edition with SQL Server 2012 Express. II8 Express is already installed.
In one other site it is suggested to use:
GRANT SUBSCRIBE QUERY NOTIFICATIONS TO "DOMAIN\ASPNET"
When I execute this, it gives error: Cannot find the user 'DOMAIN\ASPNET', because it does not exist or you do not have permission.
Which domain I need to mention?
I have also enabled BROKER from SSMS.

SignalR can be hosted in IIS or it can be self hosted. I believe in that example you are trying to follow your best bet is to host it in IIS or you can run it in IIS Express or as stated part of a windows service which self hosts a SignalR hub. I actually worked on something similar where we used SQL Notification to update a grid via a SignalR hub. We ended up having to use Change Data capture instead of Sql Dependency because of the limitations with Sql Dependency.
Here are the system requirements for SignalR hub

Related

My custom Webpage for Oracle Cloud Application can be accessed from anywhere

I programmed (on JDeveloper Studio) a custom page for Oracle Cloud Application R13 and it is working like a charm. I deployed my customization on my Oracle WebLogic Server but I couldn't help to notice the website I created was HTTP and not HTTPS when I opened it from Oracle Cloud Application. On top of that, I also noticed I could access this custom webpage from anywhere (using any device) without any security verification or login as long as I use the same URL with its token.
I would like to know how to make my custom webpage's url not being accesible just with its URL and also make it HTTPS instead of HTTP if possible.
WebLogic Version: 12c
Oracle Fusion Application version: 11.13.18.10.0
JDeveloper version: 11.1.1.7.0
I believe this might have to do something with the WebLogic configuration, since I tested the same java project on Java Oracle Cloud SaaS Extension and it doesn't have this problem. Whenever I try to open that webpage from any other device, it asks me for login credentials. I am currently working with Oracle Java Cloud. (it is not the SaaS extension version) that's why I have this problem.
Have you configured security for your application in JDeveloper? If not then your page and application is considered public and not private.
As for HTTPS, weblogic server uses 2 ports one for HTTP and an other one for HTTPS.
Regards

ASP.NET Core - Application not connecting to database after publishing

I created a simple ASP.Net Core application with user authentication (so all the Entity Framework has been preloaded into the web app template). It is connecting to my database with the connectionString that is located in my appsettings.json file, with "data source = {computerName}\\{serverName}" setup.
The database instance and Visual Studio are located on the same machine. This works fine in returning data to the web api while within development and debugging mode. When I publish it and try to go to the site from a domain name it does allow me to view the webpages that are not needing database connection but the rest that need data from the database returns pages like this:
Error.
An error occurred while processing your request.
Development Mode
Swapping to Development environment will display more detailed information about the error that occurred.
Development environment should not be enabled in deployed
applications, as it can result in sensitive information from
exceptions being displayed to end users. For local debugging,
development environment can be enabled by setting the
ASPNETCORE_ENVIRONMENT environment variable to Development, and
restarting the application.
I have tried to change the Environment Variables for ASPNETCORE_ENVIRONMENT from Development to Production to no success.
I have tried adding appsettings.Production.json to publishOptions in my project.json file, even though there is no file appsettings.Production.json, and this did not help. dotnet publish
Adding the evironment variable in the web.config file did not work Deployment
I need help getting the published web api to connect to my SQL Server database from outside the development Visual Studio setup.
The last thing I can think of is that maybe I am incorrect in how I understand the connection string. If the web api uses the connection string to connect to the database from the server-side then it should work just fine like it does when in development calling to http://localhost:port# since it's all on the same machine. But, if the database string needs to be based on a client-side call then it would have to be with domain names and IP addresses.
Can someone tell me which one it is?
The only thing else that comes to mind is that there is something I am not doing, and need to do, inside of IIS Manager. I see connect string there as well but unsure what that is for our does since the connection string is inside the application. Also maybe I am suppose to give the app some kind of authorization to communicate with the database server even though they are on the same machine???
After much research, finally googling "how to deploy a web api in iis" I was able to learn from Host ASP.NET Web API in IIS using Visual Studio Publish that I needed to add the security entity BUILTIN\IIS_IUSRS. Then placing a mapping to my database tables and giving db_datareader (and possibly db_datawriter) for the database to the IUSER to allow access from my self hosted IIS web api. This from the above mentioned link with the part stating
Accessing Database under IIS APPPOOL\ASP.NET v4.0
As we are using ASP.NET v4.0 App Pool make sure IIS APPPOOL\ASP.NET v4.0 is added to your Database Server -> Security -> Logins.

MYOB ODBC ASP.NET application issues during insert command from IIS 10.0

I am trying to develop a ASP.NET Web API for MYOB that runs within IIS. That will allow me to insert/update/select different pieces of information from a MYOB company file.
At the moment within development everything works perfectly from within VS 2015 using IIS Express. I can successfully execute a insert command on the MYOB ODBC connection in multi-user access mode while the company file is opened by atleast two other users.
However when run from within IIS no errors are displayed. However the ODBC driver returns successfully on the insert query despite no insert being completed and no records of errors in any log files.
Finally, i have given the application pool connected to the IIS Application/Website the identity of the system administrator account. So i am assuming this is not the issue.
Could someone please help me on this! Have I maybe setup the permissions and security protocols in IIS incorrectly? As this application works fine within IIS Express but not in IIS?
Thanks in advance for any help!
You eventually couldn't see an error because you are using Web API. You are just a client. But maybe the API has an error that you've couldn't be seen. is your API has a LOGS? or it has a return value when it might encountered an error?
Try to Double Check it.
I agreed there's a big difference between iis express and IIS itself(Not in VS, means other machine or in server)
Check it too.
1.) framework you are working mostly.
2.) make sure that your Web API is running.
3.) IIS set up.

Web Service error - Status 404 not found

I have created a web service in Visual Studio 2015 (web api) that listens out for requests via a barcode scanner. The barcode scanner links to a database that provides information such as stock quantities etc, but this is just for background information. The web service is currently installed on my local machine and works perfectly, returning the correct values and posts data to a database.
I attempted to install the web service onto a server, copying over similar settings in IIS (only have basic knowledge using this), such as the bindings and ensuring the permissions were set up correctly. However when running the web service I recieved a "404 not found error and 401 unauthorized". After that, I installed Visual Studio 2015 onto the server to ensure it wasn't a build or publish error...same problem.
Below are some of the 'fixes' I have tried to help narrow down the potential problem.
Ensured the correct version of .Net, 4.0, is installed on the server.
IIS Manager - Authentication: Annoymous Authentication set to enabled.
IIS Manager - Directly browsing: set to enabled.
Set the correct permissions using 'Edit Permissions', granted full control to 'Everyone'
This is my first time creating a web service so up until now I have been using tutorials and making it up as I go along. I think it could be to do with the application pools set up? But because the solution works on my local machine and not the server has me extremely confused. Thanks in advance.

ESB Management Console (ESB Toolkit 2.1) not showing data

I successfully installed the ESB Toolkit 2.1 on top of BizTalk 2010.
Everything seems to work fine.
I created a sample app following Peter Kelcey's "BizTalk ESB Toolkit 2.0--Part 1: Dynamic Routing and UDDI Integration" (http://msdn.microsoft.com/en-us/biztalk/ee819071.aspx).
The message fails, but my problem is that I don't see anything in the ESB Management portal (or in the BAM portal, in the itinerary view).
I don't have any exception or anything, just no data.
I also checked the EsbExceptionDb database in SQL Server. And the connection strings in the portal web.config seem to be ok.
I must say that I installed the portal from the samples source, by rebuilding the solution and verifying all the configurations in IIS as per the documentation.
Thanks for any direction
Cos
Update on this:
I saw that I couldn't access the ESB.Exception.Service app from either VS or browsing from IIS
I rebuilt and republished the ESB.Exception.Service app.
Now the localhost/ESB.Exceptions.Service/ responds properly.
Also, I used the sample test app that calls the localhost/ESB.ExceptionHandlingServices/ExceptionHandling.asmx and now it is able to write to the database.
The ESB Portal shows the fault data now.
Basically rebuilding it fixed it, but I don't know what was wrong to start with.
Cos

Resources