I'm wondering if I can use some command line command and a config file to setup my Reporting Services after I have installed it. You can do that to install SQL Server so I'm hoping for something that will allow me to have a set config file and then I can quickly do it for a computer/ multiple computers.
Why not just use the management console? Its possible using the bat to command the start and stop of the service:
I do not use this process but theoretically this would work:
INSTALL
sc create SQL Server Reporting Services (MSSQLSERVER)
binpath= "C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin\ReportingServicesService.exe"
net start SQL Server Reporting Services (MSSQLSERVER)
PAUSE
STOP
net stop SQL Server Reporting Services (MSSQLSERVER)
PAUSE
START
net start SQL Server Reporting Services (MSSQLSERVER)
PAUSE
UNINSTALL
net stop SQL Server Reporting Services (MSSQLSERVER)
sc delete SQL Server Reporting Services (MSSQLSERVER)
As for parameters and other directives, I do not have that list.
Related
I'm encountering a problem on Microsoft SQL Server. SQL Server Agent is not running, when I tried to start it and refresh the services.msc the SQL Server Agent is not running anymore. When I see the logs on event viewer. There are no errors but a message "SQLServerAgent service successfully stopped"
Here is the log.
SQLServerAgent service successfully started
SQLServerAgent service successfully stopped.
SQLEXPRESS does not include the SQL Server Agent aspect of the product.
You need to have SQL Server Standard Edition (or greater) to get the SQL Server Agent functionality.
That said, there may be other ways to achieve the results you desire. You could build a simple .NET app or PowerShell script to execute your query or stored procedure, and schedule that to execute via Windows own task scheduler. It is in many ways not as robust as SQL Server Agent, but it is also not as restrictive (you're running under a Windows process as opposed to SQL Server, so you have more options as to how the application may work).
I am not able to connect to the database engine. I have recently installed SQL Server 2012 after formatting my hard drive.
Operating system : Win 7 Enterprise 64-bit
When I try to connect to the database engine :
WN7X64-XXXXXXX, I get the following error message
A network-related or instance-specific error occured. Could not open connection to the SQL Server'.
I tried accessing using (localhost). It did not work.
I tried accessing using (localhost)/SQLExpress. It did not work.
I tried accessing using (localhost)/MSSQLServer. It did not work.
I tried accessing using MSSQLServer. It did not work.
When I checked the services. SQL Server status is starting, and it does not give me the option to start/stop. SQL Server Agent status is blank, when I start the service it gives
Error 1068 : dependency service or group failed to start.
Name Status Startup Type
SQL Full-text Filter Daemon Launcher (MSSQLSERVER) Started Automatic
SQL Server (MSSQLSERVER) Starting Automatic
SQL Server Agent (MSSQLSERVER) Automatic
SQL Server Analysis Services (MSSQLSERVER) Started Automatic
SQL Server Browser Started Automatic
SQL Server Distributed Replay Client Started Automatic
SQL Server Distributed Replay Controller Started Automatic
SQL Server Integration Services 11.0 Started Automatic
SQL Server Reporting Services (MSSQLSERVER) Started Automatic
SQL Server VSS Writer Started Automatic
I sometimes get SQL Server Express stuck in 'starting', in fact, just now, which is why I googled up this page. The solution is to kill the process and restart it.
Simplest way to do that is through Task Manager, which you can start by right clicking the Windows system tray (banner at the bottom of the screen where minised programs go). Processes tab, Sort processes by Name, find all beginning 'SQL...' and stop them.
To restart SQL Server right click the Windows Start button, start Control Panel, Administrative Tools, Services, scroll to all services starting 'SQL...', right click to refresh, and stop any that are running, then start the 'SQL Server' service, followed by any others that are set to Auto or Manual start.
I had the same issue and MSDN Documentation did not help. https://support.microsoft.com/en-us/kb/307288.
It was to do with that there was an orphan Sql related service i.e SqlWriter was hanging around. Go to task manager and killed it. Then the error went away.
To connect to a SQL Server default instance (not Express), you can use:
just a . (dot)
just a (local) (be aware: in round brackets)
just a localhost (be aware: NO brackets)
See the official MSDN documentation on Logging In to SQL Server for more details and explanations, and for even more options how to connect.
Try localhost or (local). Not (localhost).
I had the same issue . go to task manager , search for "SQL Server Windows NT" then end the task . after that , go to your services (Run services.msc) and restart your sql server instance .
Solution works for me in MSSQL Server express edition with Windows 10 environment .
I have an SSIS job that contains a WMI File Watcher task, which monitors a folder on another machine and processes files as they are placed in the folder.
This job, including the WMI File Watcher task, works perfectly in SSIS. However, when the same package is executed through the SQL Server Agent it returns with a status of successful but does not process the file.
Is there anything that needs to be configured through the SQL Server to allow the WMI File Watcher task to see the incoming file?
Any help would be greatly appreciated, thanks for your time.
Misc. Details:
The package is setup with a protection level of EncryptSensitiveWithPassword
The WMI File Watcher task has valid credentials with access to the remote machine
The Server environment is: SQL Server 2008 R2 on Windows Server 2008 R2
The Remote Machine is running Windows XP
try running the sql server as administrator
start->sql server->right click->run as admin
Or
restart the sql server agent
run->services.msc->sql server agent->restart
Is there any possible way to create a setup in for my program written in vb.net using sql server as the backend.I have a module which creates the database code and i have also created a setup in vb.net for my project but i want this setup to run properly even in a system which doesnt have visual studio and sql server installed.I tried running it on a system which doesnt have both but the error i get is sql server 2005 doesn't allow remote connections in default settings,i tried changing some settings but nothing seems to work.Is it necessary for a server to be there for creating the database?
a little Google always does the trick...
To configure SQL Server 2005 to allow remote connections, you must complete these steps:
1.) Enable remote connections on the instance of SQL Server that you want to connect to from a remote computer.
2.)Turn on the SQL Server Browser service.
3.) Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser service.
How To Configure Sql 2005 to allow Remote Connections
When I write programs that require SQL Server to be installed on the client, I use the following logic :
Determine if SQL Server is installed on the client machine
If it is not installed, I prompt the user to download it (or download it for them using your installer script. I use NSIS installer). Make sure to install the appropriate version for the user based on your requirements (and the client's operating system). I typically use SQL Sever 2008 R2 Express Edition, SP1.
I then execute the SQL installer using my installer script command. In NSIS, it's ExecWait. In VB.Net you have something like this. You'll have to install it via command line parameters. Here are the list of command line parameters: http://msdn.microsoft.com/en-us/library/ms144259(v=sql.100).aspx
Here's what I use:
C:\PathToMySQLDownload\SQLEXPR.exe /QUIETSIMPLE /SkipRules=RebootRequiredCheck
/ACTION=install /IACCEPTSQLSERVERLICENSETERMS=1 /FEATURES=SQL
/INSTANCENAME=MSSQLSERVER /SECURITYMODE=SQL /SAPWD=MySAPassword /NPENABLED=1
/TCPENABLED=1 /SQLSVCACCOUNT="NETWORK SERVICE" /SQLSYSADMINACCOUNTS="NETWORK SERVICE"
/AGTSVCACCOUNT="NETWORK SERVICE" /ASSVCACCOUNT="NETWORK SERVICE"
/RSSVCACCOUNT="NETWORK SERVICE" /ISSVCAccount="NETWORK SERVICE"
/ASSYSADMINACCOUNTS="NETWORK SERVICE
You can include SQL Server Express in the Pre-requisites for your setup project.
When you build the setup project, it will pick up the packages that are required for the installation from C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages
You can then amend the package.xml file for SQL Express to change how it is configured by the installation. Look for the Command Arguments element, and then to switch on Mixed mode authentication add SECURITYMODE=SQL
to enable remote access add DISABLENETWORKPROTOCOLS=0
(or for SQL 2008 r2 it's /tcpenabled=1 )
When the end user runs the isntallation, SQL Express will be installed first, with the options you have specified.
I'm trying to set up a Report server on my local machine, but I cannot get past the Database Setup step in the Reporting SErvices Configuration Manager.
I have SQL Server 2005 on my machine, which runs XP SP3.
I have reporting services installed, and the service is running, but anytime I try to setup the Reports and ReportServer database, I get the following message:
The feature "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services
Any help would be greatly appreciated.
Can you run the SQL Server Installation Tool.
Under Tools Select Installed SQL Server Features discovery report.
Tell us what this says.