Muhammad Asif: May 2019

Saturday, May 18, 2019

WDS Boot PXE: Fix the 0xc0000001 Error

Symptom

When you try to start a computer in PXE from a WDS server, the following error is displayed when loading the image:

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click “Next.”
3. Click “Repair your computer.”
if you do not have this disc, contact your system administrator or computer manufacturer for assistance.
Status: 0xc000000l
Info: A required device isn’t connected or can’t be accessed

The problem appears after you install the March 2019 updates (KB4489883 or KB4489891).

Resolution

The maximum block size of the TFTP server must be changed.

1. Open the WDS console, right click on the server 1 then click on Properties 2.

2. Go to the TFTP 1 tab, block size enter 4096 2. Uncheck Enable Variable Window Expansion 3 and click Apply 4 and OK 5.

3. Restart the WDS service. Right click on server 1 / All tasks 2 / Restart 3.

Install and Configure Windows 2016 AD-DNS-DHCP-DWS

Windows 2016 Server

AD - Active Directory
DNS - Domain Names Services
DHCP - Dynamic Host Configuration Protocol
DWS - Windows Deployment Server

Tuesday, May 7, 2019

Install SQL Server 2019 Management Studio

Download from SQL Server 2019 Management Studio from below site

https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017

Click on Download SQL Management Studio

Once its download u have to install.

Restart the windows.

Start SQL Server Management Studio

SQL Server 2019 Installation Steps

SQL SERVER – 2019 FIX: Install – Rule “Oracle JRE 7 Update 51 (64-bit) or higher is required” failed

While installing SQL Server 2019 getting below error.

SQL SERVER – 2019 FIX: Install – Rule “Oracle JRE 7 Update 51 (64-bit) or higher is required” failed

Go to https://www.oracle.com/technetwork/java/javase/downloads/index.html
Click on Download on JRE as highlighted below
Then click on “Accept License Agreement” as shown below
Once accepted, I have downloaded the one which says Windows x64 because my operating system is windows 64 bit. Note that version (8 update 212) will change in future but steps would remain same.

Windows x64

75.98 MB

jre-8u212-windows-x64.exe

After installing, I was able to move forward and install SQL Server 2019.

Hope this helps those trying to install SQL Server 2019 with Polybase features. I am sure you will be able to solve this.

Wednesday, May 1, 2019

Start / Stop the WebLogic Server Domain

Start / Stop the Weblogic Server Domain

[oracle@wls base_domain]$ pwd
/ora/oracle/Desktop/wls12213/user_projects/domains/base_domain/bin

[oracle@wls base_domain]$ ./startWebLogic.sh

.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000
.
CLASSPATH=/ora/oracle/Desktop/jdk1.8.0_211/lib/tools.jar:/ora/oracle/Desktop/wls12213/wlserver/server/lib/weblogic.jar:/ora/oracle/Desktop/wls12213/wlserver/../oracle_common/modules/thirdparty/ant-contrib-1.0b3.jar:/ora/oracle/Desktop/wls12213/wlserver/modules/features/oracle.wls.common.nodemanager.jar::/ora/oracle/Desktop/wls12213/wlserver/common/derby/lib/derbynet.jar:/ora/oracle/Desktop/wls12213/wlserver/common/derby/lib/derbyclient.jar:/ora/oracle/Desktop/wls12213/wlserver/common/derby/lib/derby.jar
......
......
.<May 1, 2019 7:11:19,026 PM GST> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>
<May 1, 2019 7:11:19,047 PM GST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>

----------------------------------------------------------------------------------------------------------------------

[oracle@wls base_domain]$ pwd
/ora/oracle/Desktop/wls12213/user_projects/domains/base_domain/bin

[oracle@wls base_domain]$ ./stopWebLogic.sh

[oracle@wls bin]$ ./stopWebLogic.sh
Stopping Weblogic Server...

Initializing WebLogic Scripting Tool (WLST) ...

Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Connecting to t3://wls.localdomain:7001 with userid weblogic ...
This Exception occurred at Wed May 01 20:26:03 GST 2019.
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3://wls.localdomain:7001: Destination 192.0.0.120, 7001 unreachable.; nested exception is:
java.net.ConnectException: Connection refused (Connection refused); No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination. [Root exception is java.net.ConnectException: t3://wls.localdomain:7001: Destination 192.0.0.120, 7001 unreachable.; nested exception is:
java.net.ConnectException: Connection refused (Connection refused); No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.]
Problem invoking WLST - Traceback (innermost last):
File "/ora/oracle/Desktop/wls12213/user_projects/domains/base_domain/shutdown-AdminServer.py", line 3, in ?
File "<iostream>", line 19, in connect
File "<iostream>", line 553, in raiseWLSTException
WLSTException: Error occurred while performing connect : Error getting the initial context. There is no server running at t3://wls.localdomain:7001 : Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3://wls.localdomain:7001: Destination 192.0.0.120, 7001 unreachable.; nested exception is:
java.net.ConnectException: Connection refused (Connection refused); No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.
Use dumpStack() to view the full stacktrace :

Done
Stopping Derby Server...
Derby server stopped.
[oracle@wls bin]$