Our production AOS server is configured to point to a remote SQL Server instance (per Server Configuration). there is also a local instance of SQL installed that may have been used at one point many moons ago, but definitely not anymore.
Every time we stop the local SQL instance, it also stops the AOS service, which affects production. If I go to services, and look at the properties of the AOS service, the Dependencies tab clearly shows that the service depends on the SQL instance.
We are trying to clean up unused instances of SQL, but I cannot find out where this dependency has been defined, thus can't stop it because it stops the AOS service too. Any idea?
Use sc.exe to configure service.
Example:
sc.exe config "AOS$01" depend= ""
PS: in PowerShell use / (forward slash) instead of empty string.
Related
I have an ASP.NET webservice which is deployed on Server2008 IIS7. We use two servers, Production and UAT (test server) and this webservice is deployed on both servers, the same compile is on both of them (no code changes, revisions etc, pure copy/paste from one to another).
The only difference between the applications is a connection string in web.config, one points to PROD database, the other UAT.
If I make a call to the test webservice I get an expected response and all is well, but when I do the same thing on the production webservice I promptly get and error
Server was unable to process request. ---> Object reference not set to an instance of an object.
I am suspecting there must be a configuration issue as the webservices are running under their own Pool which is run by a service account/user (local admin on the servers) and they are set to only run through SSL (https:// only) on a special port.
I tired sniffing with Fiddler and got two identical SOAP requests, the only difference being the server name in URL. I can access the WSDL of both webservices from IE browser, I can successfully refresh my web reference in Visual studio (for both prod and uat services).
Does anyone have any hints what should I be looking at, perhaps someone had a similar problem?
This is resolved. As I suspected the error was in production server configuration. When the sys team added a service user into the local Administrators they added it through Active directory groups, which as I am told requires a logoff/logon or a restart.
Server restart was the solution in my case.
I am installing donnetnukes.
below errors is showing.
"No valid default database connection detected. Standard Database setup option is unavailable"
ERROR: DotNetNuke requires SQL 2008 (express or full product) to work.
screenshot:
https://lh4.googleusercontent.com/-bODakjneIYg/UiMEjieEGxI/AAAAAAAAA4U/HkN5Wq_oZyk/w620-h553-no/Untitled-3.png
The error is not as straight forward as you may think, Chris. If you're sure you have at least SQL Express 2008 or later installed, ensure 3 other things.
Go to your Sql Sever Config Manager and
Ensure SQL Server 2005 is uninstalled
Ensure that SQL Server Browser is running.
Ensure that under SQL Sever Network Configuartion --> Protocols both Named Pipes and TCP/IP is enabled.
If you have trouble enabling SQL Server browser, first stop the SQL Server (SQLEXPRESS) services, right click on the SQL Server Browser --> Properties --> Services Tab --> Start Mode set to "Automatic". Then you can restart both services. This will not work if you do not stop the SQLEXPRESS Server. At least it did not for me. :)
That error is straightforward, you either need to install SQL Express, using the defaults (not a named instance), or you need to provide the IP address, database name, and user connection info for the SQL server you are using.
Another thing that got me - I installed on Windows Server 2012 and the site wasn't trusted in Internet Explorer.
There must be some client scripts that need to run at start-up which are blocked.
I had such a problem. If use the custom option and then active the SA user and password in your SQL server, you will be able to continue the process.
The reason is that this wizard gets the IIS pool user as a default one. Hence, if you create a user, you will be able to connect to that specific user & password without any problem.
I hope you find this text helpful.
I have developed a web application where in i've configured two <Resource> with proper parameters in server.xml of Apache tomcat server, Using JNDI connection pool. Among two resource tags in server.xml, first tag is having details of primary server and another tag contains the details of standby server. My idea is if i dont get connection from primary for certain time, I'll switch the datasource to standby and run the query from servlet. But when I ran the code, It gave me the error Cannot create PoolableConnectionFactory (DB2 SQL Error: SQLCODE=-1776, SQLSTATE= , SQLERRMC=1, DRIVER=3.57.82)
I googled lot but cant find any concrete answer about this, but one thing was common in all i.e. HADR(Hisgh Availability Disaster Recovery) configuration of DB2 server.
Please help me out.
Generally speaking, you cannot connect to the standby database unless it assumes the primary role after the take-over.
The correct way of setting up a DB2 HADR cluster is to configure a virtual IP address in your cluster management software that gets assigned to the new primary database after the take-over; while the change remains completely transparent for client applications.
You'll need to talk to your DBAs to learn how to configure the application.
In a HADR configuration, each time the database flips from primary to standby and the standby to primary, the Server will send ClientReroute Exception to each client connected to DB2 server, So I've caught it programtically and and tried the transaction again and it succeeded.
My whole project is a Default.aspx and a web.config. When I go to add new item > SQL Server Database, I get this error:
I have looked around the internet for the past couple of hours and I just can't find anything (please keep in mind I am still a beginner so simple, detailed explanations are very welcome).
This error means either:
a) You do not have Sql Server Express installed.
b) Sql Server is installed but isn't running, use Start -> View Local Services to start it up.
c) Sql Server is installed and running, but is not configured to allow connections. Use Start -> Sql server configuration manager to enable TCP/IP or named pipe connections.
d) Sql Server is installed and running and allows connections, but your firewall software is not configured to allow connections to Sql Server.
d) You have mistyped the Data Source value in your connection string, the default instance name for Sql Express is usually ".\SQLEXPRESS"
Configuration Tool Screenshot:
I'm trying to place a .mdf database on a Computer A and access it simultaneously on Computer B but I'm having an error that says I cannot access the mdf file because it's being used by another process.
The setup is, the database is hosted on a Public folder in Computer A. I have Visual Studio running on both computers, and Computer B accesses the database on Computer A.
Computer A Connection path string:
C:\Users\Public\database.mdf
Computer B Connection path string:
\192.168.254.8\Public\database.mdf
Is there some sort of setting that I do not know of to enable multiple access on a db? Or this is not possible?
EDIT:
Let me rephrase my question, sorry.
There are two computers connected via a network, and I want to access one Visual Studio solution/project website. I wanted to do this as a demonstration, is it possible?
You should have an instance of SQL Server (even express) running on the host machine.
All requests from the clients should use the standard mechanisms for connecting to that server instance. In other words, they won't run their own copy of SQL Server, instead they will connect to the instance running on the host machine.
Simultaneous or direct access to Database files under any DBMS control either a very bad practice or simply impossible.
Use proper DBMS tools to access the data.
And yes - its possible to access Web site project for demo.
Install SQL Server on the host machine (the one that you want to keep your database on).
Then in Visual Studio, use the "Server Explorer" to locate the remote instance of the database. From there, you can utilize the remote instance of SQL Server in your connection string, thus allowing you to connect multiple computers to a single database.
Using two instances of SQL Server to connect to the single .mdf file is a very bad practice.
Instead of specifying the MDF file in your connection string (which, I believe, uses a form of User Instancing), you should use SQL Server Management Studio (SSMS) to attach the MDF. Then connect to SQL Server, rather than to the MDF.
You may need to move the MDF and LDF files to a place where the SQL Server identity can access them, rather than keeping them in your VS project.
Most projects keep scripts to create the DB in their VS project, but not the binary MDF itself.
When you deploy, the process is similar: use SSMS to attach the MDF on your server.
Yes, If 2 or More Computers are connected by networks like LAN You can access the Database Database1.mdf (say) from another SQL Server by entering its user name / Password /by Visual studio connection.
Disadvantages:
If more than 7~8 systems are accessing same Database same time System response slows down and Hangs up or may result error like connection pool exceeded or Device not responding..
In Big Companies they use Huge Multi-core & Multi-Processer based sever which will respond faster.
Overcome: while writing Applications Use Connection Open and Close Particularly while executing the SQL queries in other time it should be closed.
Best Programer uses Transaction instead of using normal methods. Transaction Makes Every User Access Database With valid and successful Execution of queries. These Queries (Transaction Queries) mainly executes on client machine and later updates the same over Main server when it got Time slot for it(synchronize).