I have a sharepoint server on the DMZ and a SQL2008 server in the local domain.
When I try to get the list of .NETUsers for the Central Administration site from IIS (version 7.5) i get thrown error:26! I have tried all possible combinations in specifying the connection string.
I have also followed all directions on these links to resolve the isssue but it continues to persist.
http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx
AND
http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx
Please advise.
Thanks
Firstly, could you check the versions in your question. IIS 6 runs on Windows 2003, but it is not possible to install SharePoint 2010 on Windows 2003.
This is a connection error, there are 2 possibilities:
The call from the SharePoint server is blocked before it arrives at the database
The call is being refused when it arrives at the database
You should start by making a drawing of the route between the Sp server and the database server. make sure to include all firewalls.
Then check the logs to see how far the call got.
You could also try monitoring the network traffic with wireshark to see exactly what is happening.
Going from the Error itself, it turned out be a quite a complicated issue that ended up being resolved after a few days on the phone with Microsoft. The error read "The RPC service is Unavailable". There were issues with the way NetBios and DNS was qualifying the site and server names.
Related
I have an application (packaged software from a vendor) that runs on Oracle WebLogic.
There are few operations that, if I try them, I consistently get the following error page:
(WebLogic Bridge Message) Failure of Web Server bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.
The error occurs consistently almost exactly five minutes after I try the operation.
The page does not look like the typical error page you get when the application logic fails. It looks like something to do with the infrastructure (e.g., WebLogic configuration).
I am pursuing the issue with the software vendor, but that's not going well.
Has anyone seen this message and/or suggest an approach for diagnosing the root cause here?
Looks like you are using a Proxy Server between Browser and Weblogic Server. By seeing the error it's evident that proxy server unable to connect to back-end WLS server. You may have to enable proxy debugs to get more info.
I am currently running a virtualized environment for my web and db server. When I access the web server or the MySQL server individually, they are both fast. I also have websites running on the web server that do not require the db server and those all load quickly. However, when I access my hosted website that requires the web server to call from the db server, there is about a 5-7 second latency for every page load. This has been confirmed with both a very simple site and with a Word Press setup as well. Here is the config:
Web server - CentOS 6.5, Apache 2.2.15
DB server - CentOS 6.5, MySQL 5.1.73
My question is, are the servers continuously authenticating with one another (and thus causing latency) on every single db call? If that is the case, does anyone know how to permanently authenticate between the two?
I might be way off on this assumption and authentication could have nothing to do with it. I am completely open to any and all ideas at this point. Thank you very much.
V/R,
Tony
To me it seems to be a network issue.
and obviously the db-server will need authentication every time there is a hit.
Environment SQL Server 2012 on Windows Server 2008 R2 on a development environment.
After installation of the Database, SSRS, SSAS (OLAP) and Tabular (Separate instance), and SSIS everything was fine and accessable.
Several weeks later, a power user (with local admin privs) reported that he received the 'Access is Denied' message when attempting to log into SSIS. This happened at very nearly the same time as when a log mount point filled up. I immediately shrunk the log and resolved the issue behind the log filling but I then also received the same message when attempting to log on to SSIS.
The common end-point to resolve this issue is the URL Connect to a Remote Integration Services Server (SSIS Service), which is to add any non-local admin to the DCOM User group. But since this user and I are both members of the local administrator group this is not a resolution. And another power user with local admin privs worked just fine prior to the issue but not after.
I performed the standard restart to no avail followed by an uninstall/reinstall of SSIS, again to no avail. My next option would be to reinstall SQL Server. Although this would be a possibility it would not alleviate having to do it all over again if the problem recurs.
Has anyone run into this or do you have any suggestions?
This will almost certainly be a DCOM issue. If you want to resolve these issues through the registry, then the keys are as follows: Sorry, I don't know the GUIDs.
HKEY_CLASSES_ROOT\AppID\{GUID}\AccessPermission
HKEY_CLASSES_ROOT\AppID\{GUID}\AuthenticationLevel
HKEY_CLASSES_ROOT\AppID\{GUID}\LaunchPermission
I have an ASP.NET 4 application that has been in production for years running on Windows Server 2008 R2. It sends email, and is currently configured to send to a specific SmartHost.
I would like to eliminate the dependency on that SmartHost server (it might be going away). As I see it, I have two options:
Find another SmartHost - possibly in the cloud? Which concerns me because it's another point of failure and dependency.
Install & configure SMTP server on the same box as the application. I'm not wild about installing the 'IIS6-bits' that seem necessary to do this.
What's the best practice here? Are folks using external servers via SmartHost more or are you installing local SMTP servers?
I have chosen option 2, because, as you wrote, this eliminates another point of failure, namely the network path between your server and the smart host. Administering a send only mail server is not a big deal. I set up a local send only mail server about two years ago, and except an upgrade I did not do anything with it. Even the upgrade was not strictly necessary. I have to add that I was not completely new to configuring a mail server, and we already had a second mail server, giving additional safety.
On the other hand I have no experience with the SMTP server included in IIS (I only tried it once, several years ago, without success, and gave it up immediately), and I also found then that the choice of open source mail servers on Windows is limited.
I don't see anything wrong with IIS6 SMTP Server although I've only used it to relay to another SmartHost (GMail) and not had it send mail itself. It's a little tricky to set up but not that hard and has worked well for me.
Note: The IIS bits are still there even in Server 2012 and although deprecated Microsoft has provided no replacement. See my thoughts on What replaces IIS SMTP server in Windows Server 2012 on ServerFault.
I'd recommend using both IIS6 bits in conjunction with an external SmartHost (I use Gmail) for the benefits in the above referenced ServerFault answer of mine. I would think that setting up your own SMTP server is going to end up being more complicated and you may risk being blacklisted if you're not careful.
I want to send email with Exchange by using telnet to port 25. Until two week ago I was able to, but now a "security fix" from Microsoft has removed this possibility.
When I try, I get this message:
421 4.3.2 Service not available, closing transmission channel
What can I do?
I use a service (Message Labs (ML)) to filter out all the spam. We got a new internet connection and in the process of re-configuring ML's inbound/outbound services to the new IP, I got an error. So, I tested it from external by telneting to the IP on port 25 and got the "421 4.3.2 Service not available, closing transmission channel" error. What I didn't realize at first was that the reason it failed was because I had set a specific grouping of IPs on the 2007 edge server receive connector (for the ML servers). So, I added my lan network & additionally another IP for the external host I was testing from and low and behold, I could connect from both.
What I figured was happening with ML was that their server that was testing the connectivity was on an address that was excluded from the edge server.
So, I removed my testing IPs and created a new, temporary, receive connector on the edge server, accepting from all addresses (0.0.0.0 - 255.255.255.255). I then submitted the change to ML again and guess what...this time they accepted it. Now, I'll simply remove the test receive connector and everything should be golden.
SMTP is the protocol that is used to receive email from the rest of the world so I doubt that Microsoft has dropped that. There must be some other misconfiguration on your server.
Try double-checking your relay-settings and the event-log on your exchange-server.
I found the answer at website:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2900802&SiteID=17
Thanks for your help!
Basically, this functionality was removed by default and it could be restored by means of an ad hoc configuration - but with no guarrantee that further "updates" break the system again. Thanks, Microsoft.
After more than 5 years of flawless working, the 2010 EDG server suddenly stopped accepting with "421 4.3.2 Service not available". The SmtpReceive log (Get-TransportServer | select ReceiveProtocolLogPath) confirmed that it was indeed the edge server generating this error.
The EDGE server had two ip-addresses on a single NIC. After the following steps all worked fine again:
remove one ip-address from the nic on the edge server
update the static entry in DNS to point the second ip-address
on the Default internal receive connector allow to receive mail on all available IPv4 addresses.
Notice: this setup is not a security best practice for a DMZ. Better to use two NICs each with a leg in a different zone.