I have installed SAP BOBJ server in Portable SSD(External Disk) with the help of SAP consultant. But, when I start the service(BI Agent Windows Service), showing status as "Running" for few seconds, but not started. Where to check the server logs? I am seeing below path under "Path to Executable" in BI Agent service.
H:\bobj_installation\AdminConsole\Agent\CreateService.exe //RS//BOEXI40Agent
After reading some documentation, found solution.
1) First need to start the "Server Intelligent Agent" Service under Services.
2) Start the "Apache Tomcat for BI 4" service under Services.
Related
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 am new to this SSAS. I have developed a small SSAS cube. When I try to deploy it causes an error:
Error 14
The project could not be deployed to the '.' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running.
After seeing the above error msg. I try to start the SQL Server Analysis Services manually in services utility in windows but I'm not able to start them.
Please help me how to start the SQL Server Analysis Services manually
Connect to the machine, open "SQL Server Configuration Manager", search for "SQL Server Analysis Services", right click and select "start".
Try the following steps
1)Check the SSAS service account... does the password expired for that account?
2)Run Service console using "Run as administrator" option.
We are trying to configure continuous integration with TFS 2012. While queuing a new build, the publish fails with the error:
Build FAILED.
"C:\src\ProjectName.sln" (default target) (1) ->
"C:\src\Website\ProjectName.csproj" (default target) (2) ->
(MSDeployPublish target) ->
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(4377,5): msdeploy error ERROR_COULD_NOT_CONNECT_TO_REMOTESVC: Web deployment task failed. (Could not connect to the remote computer ("ServerName") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC)**
I checked all the points mentioned in the IIS.NET documentation for this error. Both services mentioned, Web Management Service and Web Deployment Agent Service, are running fine. A restart of those services has no change in behavior.
Windows Server 2008 R2 with IIS 7.
Web Deployment Agent Service is running on port 8172.
Web Deploy 3.0
Windows Firewall is not blocking any port on the server.
How can this be fixed?
If you install Web Deploy 3.x BEFORE Web Management Tools are installed, you'll have to re-install Web Deploy. I beat my head against the wall for hours on this.
Install the Web Management Services ("Turn Windows Features On/Off"/Roles -> Web Server -> Management Tools -> Management Service)
Then uninstall Web Deploy (repair didn't work) via the usual Add/Remove Programs control panel
Install Web Deploy 3.x again using Web Platform Installer.
Fixed. /Sigh
Double check in your Web Deploy settings that the name of the website is exactly that of what's in IIS.
Ben Day blogged more about it.
Fix that i saw on another website:
Fix it by adding “http://” to server.
In other words, when server is www.xxxx.com would get the 403 error, but when server is http://www.xxxx.com, then it works.
You need also to indicate the app name e.g 'Default Web Site/MyApp'
That was my error. Once I added /MyApp, it worked.
I got this error when using msdeploy, not TFS. In my case I needed to make sure the user msdeploy is using had permission to deploy to the website.
Find the website in IIS manager, right click and go to Deploy, then Configure Web Deploy Publishing. Find the user used by Web Deploy and setup for this website.
In my case the Internet proxy was enabled on source - which made msdeploy to reach out to internet instead of local ICN.
You should check the logs on your IIS first - see that you actually get to the server, and then you can locate the exact error here - https://support.microsoft.com/en-us/help/943891/the-http-status-code-in-iis-7-0-iis-7-5-and-iis-8-0
Uninstalling and re-installing (not repairing!) after setting up IIS did most of the magic for me.
There is another possible cause of the error. IIS Managemente Service have its own configuration for IP Address Restrictions, which default value is Deny Access for unspecified clients (Windows Server 2012 R2 with IIS 8.5).
You must set this value to Allow or add access to your specific IP address/IP address range using the Allow... button.
Remember, you must Stop the Management Service previously to change this configuration.
Has anyone accomplished pushing files to a BOE server using SSIS? I am trying to develop a SQL Server 2008 SSIS package that will push report (Excel) files to our Business Objects Enterprise (BO XI 3.1) server. Via a Script Task, I am using the Business Objects .NET SDK components to authenticate and connect to the BOE Server.
I have a copy of the package deployed to a local instance of SQL Server 2008 running on my Windows XP desktop. The package executes successfully (via a SQL Agent Job) and delivers the file to the designated location on the BOE server.
When I deploy the package to our development SQL server (SQL Server 2008 on Windows Server 2008 64-bit) and attempt to execute the package via a SQL Agent job, I receive the error message "File Repository Server Input is down" when the script task attempts to "Commit" the file to the BOE server. The package is able to open a session with the BOE Server, create a new info object, but fails on the infoStore.Commit command.
I have another SSIS package that executes successfully from our development SQL server - it communicates with the BOE server and searches for user sessions. It does not communicate with the Input File Repository - that seems to be the key distinction.
I have found limited information related to this error that indicates firewalls and ports between the SQL Server and BOE server may be the cause. I have reviewed the BOE Administrator's Guide to no avail (most likely due to my lack of understanding related to firewalls and ports). Both servers are within the same subnet and neither server has the firewall turned on. The ports for the BOE CMS servers and the Input/Output File Repository servers have been set to static port ids. Our network guy indicates there should be nothing preventing communication between the servers based on firewall or port settings.
Any help would be greatly appreciated!
Have you tried all the usual 'run as 32 bit' solutions? I guess yuor SDK is a 32 bit one, not a 64 bit one.
http://www.bidn.com/blogs/ShawnHarrison/ssis/2362/ssis-basics-running-a-package-in-32-bit-mode
However the fact the the SDK works for different services implies that it runs OK in 64 bit. So if you want to troubleshoot ports, I found this link http://scn.sap.com/thread/2027785 which indicates that the BOE ports are 6400 to 6411. To check that a given port is open, you go to a DOS prompt and type
TELNET hostname port
So if your BOE server is BOESERVER then you'd try this:
TELNET BOESERVER 6400
to test port 6400. You should get a black screen to indicate it's connected.
However, again, the fact that you seem to be able to connect and operate but not commit implies there is not a port problem as you can connect, just can't commit.
Are there any logs in the BOE side to give you a better idea of the issue?
A resolution to this issue has been identified and verified. The Windows AD account used by the proxy the SQL Agent job uses to execute the SSIS package did not have sufficient privileges on the network. Our DBA gave the account local Windows administrator privileges on the SQL server and this resolved the "File Repository Server Input is down" error I was receiving.
Thanks to those who responded and gave me other ideas to investigate.
We installed SP1 on our Team Foundation Server 2008 server. Everything seems fine after the install, except there is a red X on the Reports folder in the Team Explorer in Visual Studio. If we attempt to access the Reporting Services web site, we get a message that says that the "report server is unavailable". There were no errors during the installation.
The Reporting Services service started up fine and left no errors in the event log. We looked at the Reporting Services Configuration Tool and everything shows as OK. We tried restarting the RS service and rebooting the machine. Again, no errors but still no report availability.
The SQL Server instance where our data lives is up and running fine and we can query the OLAP cube and the relational side with no problem. All of our developer machines are already at VSTS 2008 SP1. Visual Studio is not installed on the server.
We looked at the logs files in the RS folder and the only errors that show are the ones that we get when we try to access the web site from IE, but that don't seem to contain any more info about the root cause.
Any help would be greatly appreciated. I'll post any updates on other things we try here.
UPDATE: There is a login error showing up the ReportServer(timestamp).log file. The login on the reporting services service is not the login that is showing up in this error, so I'm not yet sure what process is actually trying to make the connection to the db.
We got this resolved. It appears that the TFS 2008 SP1 install process decided to change the identity setting of application pool for the Reporting Services web site. To resolve we needed to:
Open Internet Information Server Manager
Go into Application Pools
Right click on the Reporting Services application pool
Click on the Identity tab
Change the account from NetworkService to our TFS domain account
Edit the rsreportserver.config located in "\Program Files\Microsoft SQL Server\MSSQL.1\Reporting
Change the "NT Authority\NetworkService" to "OurDomain\TFSDomainAccount"
Restart IIS
Hope this saves someone else some time.
Check the IIS application pools. My feeling is that reporting services doesn't play nice with other web applications (usually I've fixed this in the past by setting a seperate pool for the other applications).