I have a WCF Service for a Silverlight Application that can perform a few thousand inserts to an SQL Server database. Normally everything works fine but when we have a large set of data the service takes a longer time to do the work.
On my local IIS server (Win XP, IIS 5) and my ASP.Net dev server (even when not in debug mode) I can run the request for a long time until the job is done. I have set the Client side silverlight EndPoints timeouts/buffer sizes to a large amount (20 minutes etc..).
When we deploy to live (IIS 7 / Win 2008 Server) for some reason the service times out dead on 2 minutes. It's not the service thats stopped running because the log file is still being written to whilst Silverlight shows a "Not Found" error for the async callback method.
Where on earth is the setting on IIS that controls the timeout? I know their are 5 or so different setting for timeouts that can be set in the web.config. However, no setting I change in IIS has any effect (forms authentication has a timeout, wcf has one etc..).
Please bare in mind that this app and web.config works perfectly ok on IIS 5 / Win XP. Finally, do I have to restart IIS for any timeout changes to to effect? I am reluctant to do this because its a live server and there are other applications running on it.
Try changing the connectionTimeout for the web site. Looks like the default is two minutes.
Related
I'm having a small issue and starting to tear my hair out unfortunately.
Please excuse me if this has been answered before but I've been searching for two days and nothing is working.
I have 2 computers, one is windows 7 which is the "Server" ( 3 administrator accounts, A,B,C)
The other windows 8.1 we'll call this "Client" (1 admin account same name as C)
The Server is running MSSQL express - 2014 with SSRS on Acc:A. I'm using the BIDS (on the server Acc:B) to create reports and deploy them onto the report server happily.
What I am needing to do is to be able to access the reports from my client pc but I cant seem to be able to find what is restricting me from accessing the reports or accessing it as a service reference in VS2013.
When I Log onto accounts (useing RDP) B,C I can access the reports server happily but I try to access the reports server from the client using "Server\C" as windows login credentials it says I don't have the privileges for the home page but I can access the Site Settings.
I have a nasty feeling this is all because I'm not running on a windows server environment with domains and such which I would rather not need to use till I deploy this (when I buy a proper server) as at the moment this is all trial and proof of concept stage.
Any help anyone can give would be absolutely amazing! Thanks
Finally managed to get it working after ages, it'll be different when I deploy it but, I simply disabled the ntlm authentication and went for windows basic authentication by doing step 4 in this documentation!
Thanks for all the help!
https://msdn.microsoft.com/en-us/library/8faf2938-b71b-4e61-a172-46da2209ff55(v=sql.110)
I have a pc with windows server 2008 (but it also happens with Windows Server 2003) and IIS, with different installed sites, which normally function properly.
Sometimes (2-3 times a day) it happens that the mdb connection of the server stalling, in the sense that all the sites that read mdb database come into a kind of loop, since the browser returns the classic timeout error.
Not depend on the database or from the site, but occurs on all sites on the server. In general, they are sites in asp with classic ADODB connection. The web access continues to operate, it's just the mdb connection that goes into loop.
It’s sufficient to restart the service of web publishing or restart IIS, to run again the connection, but I want to prevent the problem, not solve it every time someone report it.
May depend on what? Some of the sites that does something that is blocking the mdb connection on entire server? A hacker attack of some kind? How can I monitor any abnormal behavior of the sites or external attacks?
Thank you.
Stop using an Access database file (.mdb or .accdb) as a back-end database for a web application.
Microsoft strongly recommends against it; it is simply the wrong approach for a number of reasons.
We are developing a disconnected app for some of our tablet users (Windows 8.1) who do field work. We are a WPF shop for internal apps and my design is to use WPF and a SQL server express database that we can then synchronize when a connection is available.
An objection has been raised to this that running SQL server express could affect battery life. Google has let me down here. I am unable to come up with any specs on how running Express may affect battery life. I suppose I could shut the service down and restart it when the app opens and closes, but we will probably be building more of these apps for the tablets and i would prefer to leave it running. battery life is a bit of an issue for our users.
Is there any info out there about how many minutes per day of battery life we can expect to loose just by having SQL express running in the background? My assumption is that it is minimal, please confirm. Are there ways (settings) to minimize its effect?
I have a web VM and a database VM on the same physical server (Windows Server 2012 Hyper-V). The web site is a classic ASP site on a Windows 2012 server, and the database is on SQL Server 2012, also on Windows Server 2012.
My colo has a DNS server (not used for these VMs), and when it goes down, the site experiences Script Timeout errors -- the pages take 180+ seconds to process. When inspecting the site profiling, many of the database calls are taking several seconds each.
However, the SQL profile shows no performance issues -- all queries take only a few milliseconds to process. Putting a filter of 1,000+ milliseconds shows no matching results. So this leads me to believe the latency is between the web and database VMs.
However, this makes no sense for several reasons:
The DNS server does not host and entries related to this site or database.
All connections use IPs, not domain/machine names.
The latency is between the two VMs, but these are on the same server, so network issues should not impact the communication between the VMs. I verified this by running Wireshark, no web-to-DB traffic hits the NIC.
What could be causing this?
Edit:
Forgot that the DNS server does have a reverse DNS for the IP and site domain. But still can't imagine how this would result in the latency between the web and DB VMs.
Additional details in response to comments:
The MDAC version, according to this article, is 6.2.9200.16384. I don't remember installing MDAC separately, so I'm assuming it's what comes installed w/ Windows Server 2012.
They are on the same subnet. A tracert shows a direct route from the web server to the DB server.
Here is the connection string:
Provider=SQLNCLI11;Server=[DbServerIp];Integrated Security=SSPI;Network=DBMSSOCN
This is not running VMWare, but instead is Windows Hyper-V. Thought I mentioned that before, but I see now that I didn't (have now added it above).
I think the following link may resolve your very issue:
Read thread to the bottom to disable the NETBIOS Helper
Essentially, as odd as it sounds, try disabling NETBIOS on your network adapter(s):
Database: Sql Server 2005
Webserver: IIS 5.0
IDE: Visual Studio 2010
I've created a Silverlight RIA application which will allow users of our intranet query one of our databases.
In the config I have set the authentication to windows and enabled impersonation.
In IIS i have disabled anonymous access and only enabled windows authentication.
This all works fine in my development environment and when running it from VS2010.
When i publish it to my local web server and connect to it from my local pc it works too.
However if i access the URL to the application on my local web server from another machine the application does not work. It gives the following error: "Load operation failed '[QueryName]'. Exception type 'System.ServiceModel.DomainServices.Client.DomainOperationException' was thrown.
The database sits on its own server. However i have the same database locally and if i change the connectionstring to local at the local version of that database it works fine.
IIS on my PC does not seem to forward requests to the SQL Server machine. As im running profiler to see what requests come in.
Any help on this would be greatly appreciated. Im sure im missing something.
Thanks
this was an issue was a classic double hop problem when using windows authentication. instead i used annoymous access on IIS and set the App Pool to an account that had access to the database on SQL Server