Rsconfig Command Format For Local Named Instance - Setting Up An Unattended Account
Dec 27, 2007
my local instance of reporting services is named and therefore I think causing me a problem when I issue the following command to set up an unattended account...
rsconfig -s localhostinstance name -e -u domain nameuser name -p password
the message I keep getting is "No Reporting Services instance found on local host.". I tried a couple of things including replacement of the word localhost with my computer name but to no avail. I tried single and double quotes around the -s parameter but no success.
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamicsFINANCE) using SQL authentication from local SSMS, I get below error message:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
I assigned a static port number to the named instance [dynamicsFINANCE] 1450. I also setup the firewall rule to allow access to Port 1450.
I noticed that when installing on a Windows XP machine, the installation results in a SQLServer instance which is configured with Built-in account = Network Service. However, with the same command line used on Windows 2000 machines, the configuration winds up being Built-in account = Local System. My understanding is that the default configuration is supposed to be Local System.
What can I do to ensure that the instance configuration is always Local System during the silent installation? This is required otherwise, under the Network Service configuration, it creates a messy situation to attach DBs.
We are seeing some very strange behavior on installation for our application when it is trying to enumerate the available SQL Server instances. On some machines (not yet determined why) the SQL Browser service is apparently able to locate remote instances but not the local instance. This does not seem to map to any firewall or TCP/IP settings which we can determine. We have gone to the extent of uninstalling all associated firewall and antivirus products, and the problem persists.
For the moment, we are working around this problem by interrogating the registry for the instances installed locally, but this seems unsatisfactory in the long run. Is there any possibility that other instances of SQL Server Express or MSDE have somehow disabled our ability to see local instances? I would really like to find a better solution to this problem.
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamics FINANCE) using SQL authentication from local SSMS, I get below error message.A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)I assigned a static port number to the named instance [dynamicsFINANCE] 1450. I also setup the firewall rule to allow access to Port 1450.
I was wondering if there was any way to set the service account on sql server 2005 express to Local System via command prompt.
To giva some background to this issue, I am installing 2005 express via command prompt, however, the default service account is network I believe. However, when running this, I keep getting an "error 3415" whenever I try to attach a database, which states that the files are "read only", which they are not. However, when setting the service account to local or set the security mode to windows authenticaiton, I can attach just fine.
The parameters I use to install are pretty standard:
So I was wondering if there was some way to set the service account to local system to local using some command prompt parameter. OR if there was another way around the error 3415 that will enable me to attach a database, that I do not know about that I can use, preferrably via command prompt, but anything will be fine at this point.
During install of SQL Server 2005, we can of course use a domain account or the built-in system account for running the services. I lean toward domain for obvious reaons but would like to know a +/- to each option and why I'd choose one over the other and what consequences or limitations one may encounter if I choose one over the other.
We cannot set the "Unattended Execution Account" on any Sql Server 2005 Report Server. This problem occurs on new installations and existing installations of Report Server. We have several servers that have the account already set from prior install and configuration, but now it cannot be changed. No domain policy changes have been applied, only MS Patches.
All attempts to set the account using the Report Server config tools return a UnauthroizedAccessException, as shown below. I have been unable to find any documentation on the permissions required for this action. Can anybody help?
System.UnauthorizedAccessException at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetUnattendedExecutionAccount(String userName, String password)
When doing a unattended install of Microsoft SQL Server Express, I have a problem specifing the service to installed to be run under the as local system account.
I'm using: SQLACCOUNT & SQLPASSWORD parameters but it just won't work.
As default SQL Server is installed using the NETWORK SERVICE account, this causes the database to be read-only. What I want is to specifiy in the script that the service should run under the LOCAL SYSTEM account instead. This must also be OS-language independent.
I've tried:
SQLACCOUNT=NT AUTHORITYSYSTEM SQLACCOUNT=NT AUTHORITYLOCAL SYSTEM SQLACCOUNT=NT AUTHORITYLOCAL SERVICE SQLACCOUNT=SYSTEM
SQLACCOUNT=BUILT-INSYSTEM
etc.
and even some different SID as:
S-1-5-18 S-1-5-19
All with no password with the SQLPASSWORD parameter:
SQLPASSWORD=
I still getting the same error while validating the service account.
Is there someone else who knows what I'm doing wrong?
Hi there,BOL notes that in order for replication agents to run properly, theSQLServerAgent must run as a domain account which has privledges to loginto the other machines involved in replication (under "SecurityConsiderations" and elsewhere). This makes sense; however, I waswondering if there were any repercussions to using duplicate localaccounts to establish replication where a domain was not available.Anotherwords, create a local windows account "johndoe" on both machines(with the same password), grant that account access to SQL Server onboth machines, and then have SQL Server Agent run as "johndoe" on bothmachines. I do not feel this is an ideal solution but I havecircumstances under which I may not have a domain available; mypreliminary tests seem to work.Also, are there any similar considerations regarding the MSSQLSERVERservice, or can I always leave that as local system?Dave
I am doing an unattended upgrade of Sql Express with Advanced Services SP1. Before the upgrade the services run under domain accounts. I use the following command :
However after the ugrade the service accounts are running under local system.
Documentation is unclear, i find the following:
; The services for SQL Server and Analysis Server are set auto start. To use the *ACCOUNT settings ; make sure to specify the DOMAIN, e.g. SQLACCOUNT=DOMAINNAMEACCOUNT ; NOTE: When installing SQL_Engine 3 accounts are REQUIRED: SQLACCOUNT, AGTACCOUNT and SQLBROWSERACCOUNT. ; SQLACCOUNT Examples: ; SQLACCOUNT=<domainuser> ; SQLACCOUNT="NT AUTHORITYSYSTEM" ; SQLACCOUNT="NT AUTHORITYNETWORK SERVICE" ; SQLACCOUNT="NT AUTHORITYLOCAL SERVICE"
To my knowledge the <> is not required. Can someone please help as i cannot get the services accounts to run under a domain user after upgrade.
I have a 3 node cluster on which I have installed SSAS as it's own insntance. I have created this as a named instance and can connect to it by serverinstance if I'm on the server itself. However from my desktop I get the error saying instance was not found on server name.
I have defined an alternate port and setup firewall rules and can connect via server:port but not serverinstance. Prior to making this change SSAS was running on default port of 2383 and I could connect just by servername.
I have read many articles for previous versions saying that clustered SSAS will always use 2383 and that you must connect just using servername. However and this is were it gets strange. I have a 2 node UAT cluster with SSAS setup exactly the same way I've described above and I can connect from my desktop as serverinstance.
Should I be able to connect as serverinstances for a named clustered instance in 2012 ?
Hi, I have a task in hand to migrate (upgrade) from SQL2K named instance to SQL2K5 default instance. There are many intranet applications touching current SQL2K. I would like to perform this upgrade such that I don't have to touch any application code - meaning I don't have to change the connectionstring to point to new Default instance. How can I achieve this?
So, in otherwords, here is what I want to achieve:
Current Server: SQL2K: SERVER_AINSTANCE_A (named instance)
If I have both default, I could achive this by setting up DNS alias after migration done so that any call for SERVER_A would point to SERVER_B. But in my case, I don't have SERVER_A, I have named instance. Is there any solution?
I am trying to set up a Named Instance of SQL 2000 on the same machine that has a default instance of SQL 7.0. The setup always completes and I am able to register the Named Instance of the SQL Server with which it was installed on. However, when I try to connect the users to the database, with both windows and SQL authentication, I receive a SQL server not found error. I have tried an alias setup as well as physically specifying the port number in settup up an ODBC connection. Has anyone ran into similar problems? Also, has anyone been able to successfully complete the process as mentioned above?
I have a server with sql server 2005 installed as the default instance -- I have a piece of software that needs SQL2000 to be the default instance. Is there a way other than install new sql2005 named instance and move databases to rename my SQL2005 instance from <machinename> to <machinename>sql05 for example?
I installed SQL Server 2005 recently on a cluster. I didn't go for the default instance and instead I named the instance option. Now I would like to migrate everything from the named instance to the default instance, which I haven't yet installed.
Is this an easy process? What about the logins and the maintenance plans and jobs? Is there anything else I need to be aware of?
I've never had to do this, but when I downloaded the Web Workflow Approvals Starter Kit, it requested that I install the database into a User Instance of .SQLEXPRESS.
Now the problem is, I've installed it onto a default instance, so I was wondering whether you can create a named instance on top of a default instance... and if so, how would you do that?
The box I am trying to connect to is running two instances of SQL Server. There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'. I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" /> However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried: <add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" /> but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used: <add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" /> but this doesn't work either.
Am I mssing something here? Any help much appreciated Thanks...
If you were asked to install SQL 2005 on a machine, would u install a default instance or a named one? And why would u choose one over the other?? Also, r there any issues with using a default instance?
I am running SQL2k SP3 with a default instance. I have recently added a second, named instance. When I try to connect to the named instance through Enterprise manager, it often times out. I never get a timeout accessing the default instance. Is there something I missed when setting up the second instance that is causing this access delay?
I am looking at some SQL in a stored proc and I noticed that theyuse a command called "contains". Can someone tell me more about this command. I can't find anything on it in the SQl books I own? SELECT distinct dmz.fileName, dmz.title, dmz.description, dmz.fileType, createdBy, createDateFROM Documents dmzWHERE d.pId like @PIDAND (contains(dmz.title, @SearchWords) or contains(dmz.description, @SearchWords) or contains(dmz.filename, @SearchWords) or contains(dmz.createdBy, @SearchWords) )
whats the simplest way to migrate a user account from a master development SQL server to local development sql servers and also to a production server?
we can recreate the SQL account everywhere, but if we take a backup from one machine and restore to another, we loose access because the accounts arent truly the same account.
Just spotted that some cowboys install a Live DB Server using Local System Account for the SQL Server Service. Gonna change it to a Domain Admin Account tonight. Anyone got any advice or warnings about any "gotchas" I might run in to during a job like this?
Is it possible to set up database mirroring between two servers that have SQL Service running under Local system? I tried to setup mirroring between two servers running under Local system but was running into the following error:
Server or Network address cannot be reached or does not exist.
What are the pre-requisites for setting up database mirroring if the service runs under Local system? Do I have to configure certificates? Is that mandatory? Can anyone please let me know. Any other gotchas?
Hi, all. To use Named instance on the same machine, Do I need to check any license issue? My Company has one server license and wants to use Named instance. thank you..
I did install SQL-server developer edition. During the installation it asked me the name of de instance. I let the installation create the default Named instance.
Now I want to add an instance with a new name. What is the best way to do this? Is this the same as creating a Notification service?
