Engine service stops - AD
I have been fighting to get this back up and running for a week now. I finally gave up and reinstalled the server (2008 R2). I have tried both 3.0.2 and 3.0.1 and neither will work. After installing the engine the service stops before I can run the setup with NSMAdmin. Here is the event from the event log. Any ideas?
Faulting application name: NSMEngine-AD.exe, version: 3.0.1.43, time stamp: 0x4d5d7ab7
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b
Exception code: 0xc0000005
Fault offset: 0x00000000000159ad
Faulting process id: 0x194
Faulting application start time: 0x01cc419314b4fbe8
Faulting application path: C:\Program Files\Novell\Storage Manager\Engine\NSMEngine-AD.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 8145e7e0-ad86-11e0-9326-005056a10c86
dyoungb,
Please contact storagemanager-at-novell.com to more specific help with
your system.
thanks,
NSM Development
On 7/13/2011 4:06 PM, dyoungb wrote:
>
> I have been fighting to get this back up and running for a week now. I
> finally gave up and reinstalled the server (2008 R2). I have tried both
> 3.0.2 and 3.0.1 and neither will work. After installing the engine the
> service stops before I can run the setup with NSMAdmin. Here is the
> event from the event log. Any ideas?
>
> Faulting application name: NSMEngine-AD.exe, version: 3.0.1.43, time
> stamp: 0x4d5d7ab7
> Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp:
> 0x4a5be02b
> Exception code: 0xc0000005
> Fault offset: 0x00000000000159ad
> Faulting process id: 0x194
> Faulting application start time: 0x01cc419314b4fbe8
> Faulting application path: C:\Program Files\Novell\Storage
> Manager\Engine\NSMEngine-AD.exe
> Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
> Report Id: 8145e7e0-ad86-11e0-9326-005056a10c86
>
>
Similar Messages
-
Hi
Jcontrol.exe is stopped. I checked in server0 log file.
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection:
Caused by: com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2043][11550] Exception java.net.ConnectException: Error opening socket to server
Caused by: java.net.ConnectException: Connection refused: connectCommunication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error
com.sap.caf.eu.gp.mail.cf.core.exceptionhandling.MailCFExceptionHandler.throwMailCFRuntimeException(MailCFExceptionHandler.java:92)
#1.5 #0022198E9491001F000000130000390C00046999A2B0692D#1242008487314#com.sap.jms##com.sap.jms####n/a##6e72d7203dd211decd7d0022198e9491#SAPEngine_System_Thread[impl:5]_90##0#0#Error#1#/System/Server#Plain#JMSServerContainer.onServiceJoin##Configuration problem occurred while accessing JMS configuration resources.#
#1.5 #0022198E9491008E000000010000390C00046999A5B43D17#1242008537907#com.sap.sql.jdbc.direct.DirectPreparedStatement##com.sap.sql.jdbc.direct.DirectPreparedStatement#Guest#0##n/a##8c9ab8303dd211de99680022198e9491#SAPEngine_Application_Thread[impl:3]_2##0#0#Error#1#/System/Database/sql/jdbc/direct#Java#com.sap.sql_0003##SQL error occurred on connection apsgdc01hwebd:BPE:SAPBPEDB: code=-4,499, state="null", message="[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error";
SQL statement is "SELECT "RESEND_INFO_UUID","SENT_MAIL_UUID","RI_START_TIME","RI_DELAY" FROM "CAF_GP_RESEND_INFO" ORDER BY 4".
[EXCEPTION]
#6#-4499#<null>#[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error#apsgdc01hwebd:BPE:SAPBPEDB#SELECT "RESEND_INFO_UUID","SENT_MAIL_UUID","RI_START_TIME","RI_DELAY" FROM "CAF_GP_RESEND_INFO" ORDER BY 4#com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error
Regards
RaoHi, Please let me know if you managed to solve the problem.. We are facing the same issue
Regards
PN -
Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"
I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server -
Hi,
When a service is down in XI server, how do we raise an Alert and send it to the External Id.
For Example: Adapter Engine is stopped for some reasons and I want to raise an alert and send it to the External system.
Can some one help me in answering this question please?
Thanks
ShaikHi refer these links may be it helps you ...
refer these link for more details about Alert
For email alerts
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
You have to do SMTP Configuration for EMail and SMS.....
http://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/content.htm
Alerts
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-stepCheck out these:
RWB- Alert Configuration LInk isnot working
Unable to login into Alert configuration
Get all the details here
CCMS ALERTS
/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
/people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
Alerts
transaction handling in XI
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
Auto triggering of alerts
transaction handling in XI
SCOT
not sending email from alert inbox
See this link : http://help.sap.com/saphelp_nw70/helpdata/en/da/a3a7408f031414e10000000a1550b0/frameset.htm
heck this weblogs on creating them and troubleshooting:
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9418d690-0201-0010-85bb-e9b2c1af895b
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
Further reference
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
Also suggested go through the blog:Alerts with variables from the messages payload
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
/people/ginger.gatling/blog/2005/12/02/innovative-ways-to-use-alerts
/people/matt.kangas/blog/2006/06/27/personalized-alert-delivery
U may proceed in the following ways:
1. Reduce the securit settings of ur browser and enable the cookies
2. Try to SSO enable ur scenario
Have a look here:
SAP Note 840849
The configuration required as per ur patch level
SAP Note 913858
Check out these:
RWB- Alert Configuration LInk isnot working
Unable to login into Alert configuration -
SAP WAS service stopping while started.
Hi All,
I am not able to start the SAP J2EE engine service.It is stopping immediately giving the below message.
"The Service on local computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."
I think thats the reason there is no systems displayed in MMC.
The Sharing for the folders saploc and sapmnt was removed recently and it was working fine before that.Even if i have shared the folder again, the service is not starting.
Please suggest any solution.
Regards,
SmitaWhat is your even log file saying? Check the status of the service file from command prompt
ntscmgr.exe query <service_name>
you can check SAP OSS Note 82751
Why did you delete those shared folders?
can you delete that particular service and then restart server and then register the service once again. -
Windows could not start block level backup engine service
Hello,
Im
trying to perform system state backup for one of the server its unable to run. Last week we have performed the system state backup without any issue.
Operating System:2008
OS Version: R2 Small Business Server 2011 x64 Edition Build 7600
RAM-32 GB
Following event ID is reported in the logs;
Log Name: Application
Source: Microsoft-Windows-Backup
Date: 7/2/2013 2:25:35 PM
Event ID: 754
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: ABC
The Block Level Backup Engine service has stopped.
When we try to restart the Block Level Backup Engine service we get error as “Windows could not start the Block Level Backup Engine Service on Local Computer.
Error 0x800700b7: Cannot create a file when that file already exists.”
I have already restarted Virtual disk and Volume shadow copy service, but no luck.
Any help in resolving this issue will be much appreciated.
Thank you.
KeshavaAll,
Here is the solution which worked for me ;
Services.msc >properties page of Block Level Backup Service Engine
Changed to Log On tab
Instead of Log On as Local System Account changed to Log On as
[email protected] (select the account with admin creds), entered the password of admin and closed the properties page.
Now restart the Block Level Backup Service Engine and re-run the job, backup completes without any issue.
Thank you
Keshava -
Failed to retrieve Analysis Engine Service How to fix
my Shorepoint is 2013 And i now is search is have proplem
On event logs show Failed to retrieve Analysis Engine Service
how to fix it please help me T_T
Best Regrads
chatchai-netdHi,
Per my knowledge, SharePoint 2013 Search services should not be required to the SQL analysis service, however, you can try to install it in SQL Server 2012 with SP1.
For this issue, you can try to just Ctrl+F5 and reset the index, also check if there is any URL not exist in the Start Addresses of the Local SharePoint Sites.
http://techchucker.wordpress.com/2013/04/12/sharepoint-2013-search-stopped-working/
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS-SharePoint/Q_28095194.html
And, you can recreate a new search service application in the Central Administration.
If it not works, you can use the PowerShell to recreate the search service application as below.
http://jsuhail.blogspot.com/2014/01/search-has-encountered-problem-that.html
http://microsoft-techies.blogspot.com/2014/03/search-has-encountered-problem-that.html
What’s more, to quickly and accurately find the issue, you can check the event log and ULS log to see if anything unexpected occurred.
For SharePoint 2013, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS.
For more information, you can refer to:
http://sp-vinod.blogspot.com/2014/02/getting-results-failed.html
https://social.technet.microsoft.com/Forums/exchange/en-US/3f1e94ce-aa3e-4a0a-ab14-8d1e3bee5e78/sharepoint-2013-search-has-encountered-a-problem?forum=sharepointdevelopment
https://social.technet.microsoft.com/Forums/exchange/en-US/73019f94-54f5-4308-9cf8-a7025ecd3228/search-has-encountered-a-problem-that-prevents-results-from-being-returned-if-the-issue-persists?forum=sharepointsearch
https://social.technet.microsoft.com/Forums/exchange/en-US/88fc7028-290f-4a09-9e47-ec7b0bf2c980/search-has-encountered-a-problem-that-prevents-results-from-being-returned?forum=sharepointsearch
Thanks,
Yumi Fu
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]. -
Hi. We are on ep5. currently, I noticed the World Wide Web Publishing Service stops running, and so with the IIS admin service. But the SAP J2EE Engine service is still running.
May I know what's the reason the services stop? is there any way to detect when the services stop, alert someone and auto restart? May I know how to do it?
thanks.Hi,
IMHO it's clear that you have an issue with IIS, not J2EE or EP5 itself. You could possible also have an issue with the ISAPI filter (SAPJ2EE / IisProxy) which can cause IIS to crash.
Although it is possible to detect IIS outages and restart automatically if necessary (you could use WMI and a scripting language such as VBScript to accomplish that) I think a better approach is to dig into the root cause of why IIS is crashing (you can to IIS thread dumps as well - don't ask me exactly how) and fix the issue instead of working around it.
Good luck! -
We have installed a new PI 7.1 system and at he moment I have the problem that I can't login into the IB tools. I found a lot of threads with this problem but I can't find a solution for my specific problem. Have a look at the well known error log:
com.sap.aii.utilxi.misc.api.ReconnectRuntimeException: Cannot connect to server using message server: ms://MYHOST:8100/P4
at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:668)
at com.sap.aii.ib.clsif.login.EJBHomeFactory.connect(EJBHomeFactory.java:461)
at com.sap.aii.ib.clsif.login.EJBHomeFactory.initRemoteFactory(EJBHomeFactory.java:133)
at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:176)
at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:121)
at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:109)
at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginController.doTrial(SplashLoginFrame.java:960)
at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginAction$1.run(SplashLoginFrame.java:832)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext.
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:488)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:653)
... 15 more
Caused by: com.sap.engine.interfaces.cross.EXTstinationException: cannot establish connection with any of the available instances:
MYHOST.DOMAIN.EXT:50104 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.24.205.193 and port: 50104
at com.sap.engine.interfaces.cross.EXTstination.getNextAvailableBroker(Destination.java:59)
at com.sap.engine.interfaces.cross.EXTstination.getRemoteBroker(Destination.java:35)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:352)
... 20 more
As you can see I call the IB via a pure hostname "MYHOST". But in the last step you can see the the FQDN "MYHOST.DOMAIN.EXT"was used. That brings me into trouble because these are different IP's. I can't reach the MYHOST.DOMAIN.EXT IP and that's why I can't login into the IB.
If I add an entry in my local host file for MYHOST.DOMAIN.EXT with the IP address I can reach all works fine but this solution is unacceptable.
The key question is why the IB uses this FQDN. I can't find any setting where this FQDN is used. I have checked the complete exchange profile, the sld and and and u2026. I always find only the pure hostname MYHOST.
Additionally I have to say that we have already a PI 7.1 system (DEV) whre I can use all tools. But this is a migrated system (from 3.0). I have only problems with that new installed empty system.Thanks Barry. I've checked all connections. They all use the short name and all work.
Thanks Joel, but I think you get me wrong. That's why I will explain it a little bit better.
I can use the IB if I manipulate my own hosts file but this is in my eyes not the right way. As I have written I can use my PI dev system without that kind of manipulation.
My new PI system is at our computer centre. The PI machine has two network interface and I can use only one of these two. As you can see at the error log the full name points to 172.24.205.193 but I only can reach the 172.20.02.193 address. For this second IP we have an entry at our DNS server. The other one (FQDN) comes from the computer center DNS server. Of course I can overwrite it with an entry in my local hosts file but I think that isn't a good solution.
The key question is: Why the full qualified domain name "MYHOST.DOMAIN.EXT" is used instead of the short name.
I call the IB via the web page
http://MYHOST:50100/dir/start/index.jsp
And as you can se at the log the first call goes to this address. But then a second call goes to MYHOST.DOMAIN.EXT:50104. And I can find any setting (exchange profile and so on) where this full qualified domain name is specified. -
Sql reporting services stops every 24 hours for a short time then restarts
I have noticed that recently in sccm 2012 sp1 the sql reporting services stops every morning at 7:58 am and restarts after a minute or two. The only entry in the event logs is when it stops. I don't see anything tied in with it that stops or
starts at the same time and there are no tasks or anything like that which would point to this time frame. I just thought I would throw this out there to see if anyone had any ideas. Usually with something of this nature there are some corresponding
log entries that go beyond the service stopping, but in this case there isn't. Thanks for any help you can provide.I think I found out what was going on. I approached this from a different angle and was directed to the sql reporting services logs and found information on the reporting web server stopping. Researching that yielded the following information.
It appears that this is a result of the SSRS Web Server recycling the App Domain, which is supposed to be a pretty normal process. In fact, the configuration file for this process defaults to recycling the app domain twice daily. This lines up
with the time frame that the reporting service is stopping. It restarts it in less that two minutes and logs the recyling in the reporting services log twice daily so why I'm not seeing this entry in the event logs twice daily or even every day must
be a timing thing. I think if it takes an extra millisecond or two to recycle the app domain, it dumps an entry into the windows event logs and the sccm component status monitoring.
http://ask.sqlservercentral.com/questions/97176/reporting-web-server-stopped.html -
Error message: Host process for windows services stopped
I recently had to install a new hard drive into my laptop. I am running windows vista and have installed all updated drivers. After installing itunes and uploading my backed up library, I went to play a song and I got the error "host process for windows services stopped working and was closed." Movies play fine. I have searched but have not found anything. Any help would be greatly appreciated.
Q I just upgraded to a new mobo and CPU, the EVGA X58 SLi and i7 920, and this issue still persists! That means it is either the sound card or Steam. The drivers on the CD have no issues, only the newer ones do. So by deduction there is something wrong with the new drivers, but I need them to not BSOD in OpenAL!
-
A135-S4527 Host Process for Windows Services stopped...
I have started getting a Windows error: Host Process for Windows Services stopped working and was closed. Laptop runs fine except my network connection says Connection Status: Unknown The service to detect this status is turned off and McAfee stopped working. Can't run any of the MS tools either. I am suspicous of conficker e but don't know how to detect or remove it. Have seen the b variant on an XP machine at work, but the tools we used on it don't work on Vista.
I am running Vista Home Edition (came on Laptop) upgraded to SP1 with auto-updates on. McAfee was also set for auto-updates and nightly full scans, active e-mail and internet scanning. No recent software downloads except for updates.
Have been having the issue since about April 28. Tried to restore but no dates exist past May 5. Tried the F8 Startup recovery no problems found. Have tried restarting services but they quickly stop again. Uninstalled McAfee and tried AVG. It allowed defintion updates and I scanned all files. No viruses, trojans or malware detected.
Any suggestions? I have a tasklstserv file I can copy and paste if it will help.That's a bad-sector event. At a command prompt (cmd.exe), run chkdsk /r.
Event ID 7 Source Disk
But it doesn't seem likely that's the cause of the message. When you get another one, note the time and check the Application and System logs for entries at that exact time.
Thanks for the detailed information.
What virus protection do you use?
-Jerry -
Error: com.sap.engine.services.jndi.persistent
Hello All,
I am getting below error when trying to work with the Module parameter in the sender File Adapter
Attempt to process file failed with com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of RequestResponseBean.
-RajeshHello Shabarish,
I am working on PI 7.0 SP 09 .
Can i make use of the bean RequestResponsebean in this version?? Please let me know -
Hi Subhra/ Asit,
The following is the main information form the log file and attched logfile with full info for your reference.
#1.5#00188B874AFD00320000000A000007B4000447710E97B363#1204450808802#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
usr
sap
SPP
JC01
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.portal.layouts.default
jsp
fullWidth.jsp [email protected]a6d4d7#
#1.5#00188B874AFD00320000000B000007B4000447710E97BD23#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#Thread[PRT-Async 0,5,PRT-Async]##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]a6d4d7#
#1.5#00188B874AFD00200000000B000007B4000447710E97C15A#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] Getting JSPResource : E:
usr
sap
SPP
JC01
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.portal.layouts.framework
jsp
WAandNavPanel.jsp [email protected]16c192#
#1.5#00188B874AFD00200000000C000007B4000447710E97CCCC#1204450808818#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#prasadkr#149##nzakleafn052_SPP_16099250#prasadkr#8d7e2ad0e83c11dcafd200188b874afd#SAPEngine_Application_Thread[impl:3]_6##0#0#Warning#1#/System/Server#Plain###[PortalComponentItemFacade.service] done. [email protected]16c192#
#1.5#00188B874AFD002900000049000007B4000447710EA4FBF8#1204450809677#com.sap.tc.webdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.
[EXCEPTION]
#2#fonterra.com/cmtuwlcmir~dispform/CMIRCreateNotificationDisplay#java.lang.NullPointerException
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00188B874AFD00290000004A000007B4000447710EA7E5F6#1204450809865#com.tssap.dtr.client.lib.protocol.session.Cookies#sap.com/tcwddispwda#com.tssap.dtr.client.lib.protocol.session.Cookies.setCookie(Cookie)#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Java###rejecting invalid cookie for domain "": #2#.fonterra.com#JSESSIONID#
#1.5#00188B874AFD00290000004B000007B4000447710EA8000D#1204450809880#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Processing HTTP request to servlet [dispatcher] finished with error. The error is: java.lang.NullPointerException
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:256)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
at com.fonterra.wdp.mdl.getnotificationinfo.Z_Sd_Get_Notifiy_Status_Input.<init>(Z_Sd_Get_Notifiy_Status_Input.java:51)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.getNotificationData(CCTGetNotificationDetails.java:123)
at com.fonterra.wdp.comp.CCTGetNotificationDetails.isCompleted(CCTGetNotificationDetails.java:145)
at com.fonterra.wdp.comp.wdp.InternalCCTGetNotificationDetails.isCompleted(InternalCCTGetNotificationDetails.java:162)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doIsReadOnly(CCMaintainCMIRInterface.java:137)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doIsReadOnly(InternalCCMaintainCMIRInterface.java:143)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRdetails(CCTCMIRGet.java:222)
at com.fonterra.wdp.cct.CCTCMIRGet.doReadCMIRInfoFromNotification(CCTCMIRGet.java:132)
at com.fonterra.wdp.cct.wdp.InternalCCTCMIRGet.doReadCMIRInfoFromNotification(InternalCCTCMIRGet.java:1041)
at com.fonterra.wdp.comp.CCMaintainCMIRInterface.doSetNotificationAndRead(CCMaintainCMIRInterface.java:184)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:155)
at com.fonterra.wdp.comp.wdp.InternalCCMaintainCMIRInterface$External.doSetNotificationAndRead(InternalCCMaintainCMIRInterface.java:321)
at com.fonterra.wdp.comp.VIEWCMIRFormDisplayView.wdDoInit(VIEWCMIRFormDisplayView.java:99)
at com.fonterra.wdp.comp.wdp.InternalVIEWCMIRFormDisplayView.wdDoInit(InternalVIEWCMIRFormDisplayView.java:122)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:653)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:243)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00188B874AFD00290000004D000007B4000447710EA803B8#1204450809880#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: java.lang.NullPointerException: null
Exception id: [00188B874AFD00290000004B000007B4000447710EA8000D]#
#1.5#00188B874AFD00290000004E000007B4000447710EA82DD2#1204450809896#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:168)
at javax.servlet.ServletOutputStream.print(ServletOutputStream.java:135)
at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.sendBodyText(HttpServletResponseFacade.java:957)
at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:948)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00188B874AFD002900000050000007B4000447710EA82F56#1204450809896#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#prasadkr#150##nzakleafn052_SPP_16099250#prasadkr#8e0d2460e83c11dca34d00188b874afd#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)].The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
Exception id: [00188B874AFD00290000004E000007B4000447710EA82DD2]#
Regards
Krishna Kkinldy let me know what was the solution to this problem
-
We are using VS2013 Premium. i have installed vs2013 Test controller in my dev environment. While i am configuring (https://msdn.microsoft.com/en-us/library/hh546459.aspx) getting error message in
the Configuration summary dialog box displaying following error's : 1. Failed to Configure TFS Team Project Collection, 2. Could not complete operation as the time out expired. ''
I have checked the "visual Studio Test controller " in the
Services --> Administrative. Its automatically stopped the service. When i started the manually its showing message like as 'The visual Studio Test controller
service on local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs'
Please guide me how to resolve this problem.
Thanks in Advance...Hi Divakar,
What’s the version of your TFS?
How do you configure the test control?
Please make sure you are specify the team collection instead of team project.
On the other hand, you may enable test controller logs. (You could share the log file on the OneDrive)
# How to enable test controller logs
http://blogs.msdn.com/b/aseemb/archive/2009/11/28/how-to-enable-test-controller-logs.aspx
Regards
Starain
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.
Maybe you are looking for
-
On a Mac Chrome no longer works with Webmail
Getting the following error when trying to log into webmail using Chrome: Not Supported Method Any thoughts? Safari and Firefox all work. This only began in the last few weeks.
-
File content conversion is not creating the exact strcuture as Datatype
Hi, We are facing issue . I have sender DT type <FIle_DT> < HeaderDetail> <Field1> <Field2> <Linietemdetails> <Field1>
-
I have Acrobat 9 and I'm trying to get a document to embed the asian language set and cyrillic. Any idea how I can do this? I have embedded ALL in the joboptions, but it doesn't seem to take the asian or cyrillic? Thanks
-
Performance issue while inserting data
I have a .dat file containing the required data for the table.It has almost half a million rows.When i inserted the data using SQL LOADER it took almost whopping 70 minutes .How can i insert the data fast.what should i include in my control file to i
-
The server "server iMac" may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again. I get this message when I turn on My imac or macbook. I connected them to transfer fil