I can't find any information that is relevant to my specific situation. Around a month ago I had created my own application server which has become my local development machine. The tutorial I followed was available here: https://blogs.sap.com/2016/11/03/sap-nw-as-abap-7.50-sp2-developer-edition-to-download-consise-installation-guide/
This has been working fine until this morning. Last night I shut SAP down using stopsap and shutdown the VM via shutdown -h 0. When I used startsap this morning it hung infinitely when trying to start the database.
linux-nsts:npladm 92> startsap
Checking syb Database
Database is not avaliable via R3Trans
------------------------------------------
starting database NPL ...
Log file: /sybase/NPL/startdb.log
Checking that log file I find the following messages:
------------------------------ Thu Jul 6 09:35:22 CEST 2017
/usr/sap/NPL/SYS/exe/run/startdb was killed or interrupted. Terminating.
In the trace file in the home directory
Running /usr/sap/SYS/exe/run/startdb
DB startup failed
I can't find any other articles that are relevant to my situation. My host file is perfectly fine and the IP can be pinged. I only have one linux user, npladm for starting SAP. The only other command I could find was R3trans but I'm not sure if this would be the right program in this instance.
linux-nsts:npladm 7> R3trans -d
This is R3trans version 6.25 (release 745 - 30.10.15 - 12:47:42 ).
unicode enabled version
2EETW169 no connect possible: "DBMS - SYBASE --- "
R3trans finished (0012)
As for the operating system itself I'm not aware to any changes I could have made that could have caused this. The only command I run on the server is startsap and stopsap.
I'm out of ideas where to look, can anybody offer advice?
EDIT: The license for SYBASE expired and it needed to be updated in my case. There is a link in the tutorial explaining how to switch it and where to download a new one.
I stumbled upon by accident the folder /sybase and found a number of log files in there. My server isn't starting because my database no longer has a license. It expired today, actually.
https://mdocs.sap.com/mcm/public/v1/open?shr=dRhHsVYVLc5c1UDveogwtXBdL9m82JccRlvvBXO6K5Q
00:0000:00000:00000:2017/07/06 10:08:09.37 kernel SySAM: Using licenses from: /sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_DE.lic:/sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_TestDrive.lic:/sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_XE.lic
00:0000:00000:00000:2017/07/06 10:08:09.42 kernel SySAM: Failed to obtain license(s) for ASE_CORE feature from license file(s) or server(s).
00:0000:00000:00000:2017/07/06 10:08:09.42 kernel SySAM: Licenses exist for ASE, but a license containing the configured (PE=EE;LT=AC) attributes could not be obtained. Verify that ASE is configured to use the correct type of license, and either reconfigure; or generate and deploy the desired license from the Sybase Product Download Center.
00:0000:00000:00000:2017/07/06 10:08:09.42 kernel SySAM: Feature has expired.
00:0000:00000:00000:2017/07/06 10:08:09.42 kernel SySAM: License feature name: ASE_CORE
00:0000:00000:00000:2017/07/06 10:08:09.42 kernel SySAM: Expire date: 30-jun-2017
00:0000:00000:00000:2017/07/06 10:08:09.42 kernel SySAM: License search path: /sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_DE.lic:/sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_TestDrive.lic:/sybase/NPL/SYSAM-2_0/licenses/SYBASE_ASE_XE.lic:
00:0000:00000:00000:2017/07/06 10:08:09.42 kernel SySAM: FlexNet Licensing error:-10,32
00:0000:00000:00000:2017/07/06 10:08:09.42 kernel SySAM: For further information, refer to the Sybase Software Asset Management website at http://www.sybase.com/sysam
00:0000:00000:00000:2017/07/06 10:08:09.42 kernel There is no valid license for ASE server product. Installation date is not found or installation grace period has expired. Server will not boot.
Related
Details:
SQL Server 2017 (Developer or Express edition)
Windows 2011 OS
I have followed this article already but no avail https://blog.sqlauthority.com/2017/01/27/sql-server-sql-installation-fails-error-code-0x851a001a-wait-database-engine-recovery-handle-failed/
Feature: Database Engine Services
Status: Failed
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
WHAT IS THE CAUSE?
this is caused by the sector size of the disks.
During service startup, SQL Server begins the database recovery process to ensure database consistency. Part of this database recovery process involves consistency checks on the underlying filesystem before attempting the activity of the opening system and user database files.
On systems running Windows 11, some new storage devices and device drivers will expose a disk sector size greater than the supported 4 KB sector size.
When this occurs, SQL Server will be unable to start due to the unsupported file system as SQL Server currently supports sector storage sizes of 512 bytes and 4 KB.
You can confirm that you encounter this specific issue by running the command:
fsutil fsinfo sectorinfo E:
Look for the value PhysicalBytesPerSectorForAtomicity, returned in bytes. A value of 4096 indicates a sector storage size of 4 KB.
HOW TO FIX IT!
Simply follow the instructions on this page.
https://learn.microsoft.com/en-us/troubleshoot/sql/admin/troubleshoot-os-4kb-disk-sector-size#resolutions
if you don't want to change the os, you should try this resolution on the above site.
You can add a registry key which will cause the behavior of Windows 11 and later to be similar to Windows 10. This will force the sector size to be emulated as 4 KB in size. To add the ForcedPhysicalSectorSizeInBytes registry key, use the Registry Editor, or you can run one of the following commands in Windows command prompt or PowerShell, executed as an administrator.
After you change the registry, you must restart the device and then reinstall the program. Otherwise, this method will not work!
I am receiving a backup failed error since 6/20/2020 within my Azure backup policy.
I also noticed within the Properties section under Settings of the Virtual Machine instance the "Agent status" is in a "Not Ready" state.
When I click the Backup section under Operations the Backup Status shows 2 entries.
Backup Pre-Check Warning
Last backup status Failed
I can click the Warning option and the link takes me to a page that reads:
Issue Description
VM agent is unable to communicate with the Azure Backup Service.
Suggested Action(s)
Ensure that VM agent is latest and running. Allow access to IP 168.63.129.16
Per the Suggested Actions, I created the Outbound Rule to the IP Address 168.63.129.16 within the network interface of the Virtual Machine instance that is having the backup failed issue.
That did not solve the problem. I also performed the below troubleshooting steps as well with no solution:
I also Verified the Windows Azure Guest Agent service is running within services on the affected VM OS (ACMVI002).
Stopped the VM instance from the Azure Portal. I then turned the VM instance back on. Issue persisted.
Does anyone have a solution to this Backup Failed issue?
You probably still don't have access to 168.63.129.16 or your agent is too old, this is a global Microsoft IP used to facilitate a communication channel to Azure platform resources, more details you can read this article.
Azure Backup needs Azure Agent up to date, you can have an old Agent, but depends on how old it is, you can have issue, please refer to this page for more details.
You can try to update your Azure Agent manually, here it is information about it.
From C:\WindowsAzure\Logs\WaAppAgent.txt you see some options to try to identify your issue, version of your Agent appears.
[00000006] [06/25/2020 20:31:00.34] [INFO] WindowsAzureGuestAgent starting. Version 2.7.41491.971
From C:\WindowsAzure\Logs\WaSecAgent-startPoll.txt you see logs from your VM to 168.63.129.16
[2020/06/25 20:31:02:176] Info:WaSecWireServerProxy:: Will start polling for Uri 168.63.129.16 , poll time 900000 ms, running time 21600000 ms
[2020/06/25 20:31:02:176] Verbose:WaSecWireServerProxy:: - WireServerProxy::StartCACertsUpdater
[2020/06/25 20:31:02:176] Info:WaSecWireServerProxy:: Current process is the primary process for polling
[2020/06/25 20:31:02:176] Info:WaSecWireServerProxy:: CA certs polling called for 168.63.129.16, poll interval 900000
[2020/06/25 20:31:02:176] Verbose:WaSecWireServerProxy:: - WireServerProxy::StartCACertsUpdater0x0
[2020/06/25 20:31:02:176] Info:WaSecWireServerProxy:: Starting CA Cert Polling Thread
From the same file C:\WindowsAzure\Logs\WaAppAgent.txt you see logs about RecoveryServices
[00000010] [06/25/2020 20:58:15.54] [INFO] Initialize ExtensionWorkflow for 'FastTrack GS: SeqNo=3'.
[00000009] [06/25/2020 20:58:15.57] [INFO] Plugin Microsoft.Azure.RecoveryServices.VMSnapshot 1.0.65.0 not found in cache.
[00000010] [06/25/2020 20:58:15.57] [INFO] Plug-in Microsoft.EnterpriseCloud.Monitoring.MicrosoftMonitoringAgent 1.0.18038.1 found in cache.
[00000009] [06/25/2020 20:58:15.59] [INFO] Starting download of plugin version manifest Microsoft.Azure.RecoveryServices.VMSnapshot from location: https://zrdfepirv2bl4prdstr03.blob.core.windows.net/80afa74b14194a679c6347109557b7ee/Microsoft.Azure.RecoveryServices_VMSnapshot_useast_manifest.xml
[00000009] [06/25/2020 20:58:15.59] [WARN] Downloading version manifest via HostGAPlugin for plugin Microsoft.Azure.RecoveryServices.VMSnapshot from https://zrdfepirv2bl4prdstr03.blob.core.windows.net/80afa74b14194a679c6347109557b7ee/Microsoft.Azure.RecoveryServices_VMSnapshot_useast_manifest.xml.
[00000010] [06/25/2020 20:58:15.59] [INFO] Test extract the plugin zip file to the temp folder C:\windows\TEMP\b4162b75-fe14-4669-8ed5-e283671cb293
[00000009] [06/25/2020 20:58:15.62] [INFO] Download finished for plugin version manifest Microsoft.Azure.RecoveryServices.VMSnapshot.
Some logs here too
C:\WindowsAzure\Logs\Plugins\Microsoft.Azure.RecoveryServices.VMSnapshot\1.0.65.0
In case anything helped, consider open up a ticket to Microsoft, it could be a issue on Microsoft side that we don't have access to investigate it further.
You would need to re-install the Backup extension. Take a backup of whole registry then use following steps:
Login to the affected machine.
Open Registry Editor.
Remove VMSnapshot registry keys at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure\HandlerState
Remove or rename VMSnapshot Plugin Folders at C:\Packages\Plugins.
Now, open command prompt as admin and run below commands to force the extension installation:
REG ADD "HKLM\SOFTWARE\Microsoft\BcdrAgent" /v IsProviderInstalled /t REG_SZ /d False /f
REG ADD "HKLM\SOFTWARE\Microsoft\BcdrAgentPersistentKeys" /v IsCommonProviderInstalled /t REG_SZ /d False /f
Restart the Service "WindowsAzureGuestAgent".
Trigger a manual backup. As a part of backup, extension will be re-installed automatically.
the cmd execution of registerRExt.exe
I am trying to install RRE(Revolution R Enterprise) v7.5 with RR0 3.2.2(Revolution R Open) on a SQL Server 2016 RC0 default instance. All the steps shown in the https://msdn.microsoft.com/en-us/library/mt590808.aspx have been completed and the error occurs in the Post installation Server configuration scripts. The script has also been replaced by the updated script for RC0 shown on the msdn site but still I get the same error on running the registerRExt.exe file.
The site shows while installing the instance the account name for Server Database engine has to be MSSQLSERVER, however this had also resulted in an error stating wait on database recovery handle failed which was sorted by changing the account name of Database engine to NT AUTHORITY/SYSTEM(I provided this info as it can also be the cause of the problem) . Now I need to sort the user pool failure. Any help would be appreciated..thanks in advance
SQL 2016 RC1 was just released https://blogs.technet.microsoft.com/dataplatforminsider/2016/03/18/sql-server-2016-release-candidate-1-now-available/.
SQL RC1 has a newer version 8.0.1 version of RRE. I suggest your try to install it and reply to this thread again if you hit the same failure. https://msdn.microsoft.com/library/mt590809.aspx has the details on where to find Microsoft R Open 8.0.1 and Revolution R Enterprise 8.0.1.
If the issue persists RevoScaleR\rxLibs\x64\registerrext.log would have more details on the exact failure - do share that.
I was able to sort out the issue..It was because I was installing the SQL server on domain controller and ignored the warning while install, but then changing some rules and demoting it from Server Manager worked and the install was successful.
However I do know there may be some better solution to that as all the other user accounts got reset in the process.
I've a recurring issue on a number of 2008 R1 servers. Replication stops completely, and any attempt to run any AD-related snap-ins or diagnostics fail.
For example:
C:\Windows\system32>dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = MYDC
Ldap search capabality attribute search failed on server MYDC, return
value = 81
Other tools also fail in the same manner:
C:\Windows\system32>repadmin /showreps
[d:\rtm\ds\ds\src\util\repadmin\repbind.c, 444] LDAP error 81 (Server Down) Win32 Err 58.
LDP can't connect to the server either:
ld = ldap_open("mydc", 389);
Error <0x51>: Fail to connect to mydc.
There are a couple of event log entries, but frankly I'm not sure if they are a cause or a symptom.
Event 1311:
The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
Directory partition:
CN=Configuration,DC=ad,DC=mydomain,DC=co,DC=uk
Event 1566:
All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.
Site:
CN=MYSITE,CN=Sites,CN=Configuration,DC=ad,DC=mydomain,DC=co,DC=uk
Directory partition:
DC=ad,DC=mydomain,DC=co,DC=uk
Transport:
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=ad,DC=mydomain,DC=co,DC=uk
A reboot always clears this up, and always after a month or two the same problem will crop up again on a different server. I've seen it on 5 different servers in different domains so far. Reboots are fine, but it always feels like a bit of a blunt instrument. I was hoping someone might have come across this before and be able to offer a fix.
thanks...
Is this related to: "All the TCP/IP ports that are in a TIME_WAIT status are not closed after 497 days from system startup in Windows Vista, in Windows 7, in Windows Server 2008 and in Windows Server 2008 R2" http://support.microsoft.com/kb/2553549
Can someone please send me the download link for Domino Server 8.5 trail version as I want to test Domino Server and Client connectivity.
Since Yesterday I am searching for the appropriate link but could not find the relevant download.
Any help is appreciated.
Regards,
Haseena
Lotus Domino server trial/demo is currently not available. At least not in a usual (download - install - expire) way.
Previously Domino was available for download here (who knows, maybe IBM will change this policy tomorrow):
http://www.ibm.com/developerworks/downloads/ls/lsds/index.html
List of available trials from IBM:
http://www14.software.ibm.com/webapp/download/byproduct.jsp
If you must have it your options are either to buy:
SMB: http://www.ibm.com/software/lotus/products/dominoexpress/
http://www.ibm.com/developerworks/downloads/ls/lsds/buy.html
or to evaluate it in the cloud:
http://www.ibm.com/developerworks/downloads/ls/lsds/cloud.html
https://www.lotuslive.com/en/