Prerequisites check phase fails while installing SOLMAN 7.1 SP13 on windows server 2012 R2

[Former Member]

Hello Experts,

While installing solman 7.1 sp13 in windows server 2012 r2 edition ..we came up with an error that shown below..

We did download the hotfix that microsoft provides in the link
http://support2.microsoft.com/kb/2820470 as well as we did the windows update..

although Nothing that really matters..Please help..

[Former Member · Accepted solution]

Hey Experts,

The Issue was solved .Im closing this thread..

Thanks anyway..

[Former Member · Accepted solution]

how to solve this problem?

i have same issue...

[Matt_Fraser · Accepted solution]

Hi Anoop,

You should share your solution when you close the thread, since you solved it yourself.

However, I know the solution, having just gone through this myself. It's really quite simple. For Windows 2012 R2, there is no hotfix to download and apply (the hotfix in the KB is for Windows 2012, not 2012 R2). In Win 2012 R2 there is a minor registry change to make manually, and it is completely and fully described in the Microsoft KB article. Add the registry key mentioned, and the prerequisites check will pass. This is a new check in the latest versions of SWPM -- earlier versions didn't check for this registry key.

Cheers,

Matt

[Former Member · Accepted solution]

i added bilow registry key,  but same error!!!!

have you another solution?

1. Locate and then tap or click the following registry subkey:     

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkStation\Parameters    

  On the Edit menu, point to New, and then tap or click DWORD Value.     

  Type DisableCARetryOnInitialConnect.  

  Press and hold or right-click DisableCARetryOnInitialConnect, and then tap or click Modify.     

  In the Value data box, type 0, and then tap or click OK.     

[Matt_Fraser · Accepted solution]

That was the solution for me. You probably have something else going on. I suggest you start a new thread and put in all the details, including some screenshots of the error and the registry key you entered, rather than continuing on this old thread.

[Former Member · Accepted solution]

The value of DisableCARetryOnInitialConnect must be set to 1 !!!

CARetryOnInitialConnect does block the SMB access on a Windows Server 2012/ 2012 R2 for 60 seconds until returning an error code (share does not exist) if you access a not existing share on a Windows 2012/2012 R2 Server with activated Failover Cluster Feature (FC does not need to be configured!).

Q&A:

Q: Why does SMB 3.0 wait up to 60 Seconds?

A: During the failover of Fileserver the share is not visible during the failover time. Hence Windows can't test in this timespan whether the share does not exists or wether it is temporarily unavailabe due to a failover operation. CA (Continous Availability) is a feature which allows open fail handles from SMB 3.0 clients to survive a failover of an SMB 3.0 destination.

Q: what are the side effects of DisableCARetryOnInitialConnect  =1

A: Windows will immediately return with an error message if a share is not existing.

If a share is temporary not available Windows will fail immediately if the share was never accessed since booting the server. Windows will block for 60 seconds if the share was already successfully accessed and is currently not available due to a failover operation.

I strongly recommend to activate DisableCARetryOnInitialConnect  =1 on all Windows Server 2012 or later and Windows 8 and later computers (not only the cluster nodes), if there is a chance that they will access Windows Server 2012 or later servers via SMB where the Windows Failover Cluster feature was activated (does not need to be configured).

regards

Peter

[Matt_Fraser · Accepted solution]

Yes, that's right. 1 is the value I set. I just now realized that Jun said he set it to 0.

[Former Member · Accepted solution]

how to solve this problem?

[7amid_ibrahim · Accepted solution]

The change required is a simple registry change. 

1. Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.

1. In the search box, type regedit, and then tap or click regedit.

If you are prompted to enter an administrator password, type the password. If you are prompted to provide confirmation, provide confirmation.

1. Locate and then tap or click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkStation\Parameters

1. On the Edit menu, point to New, and then tap or click DWORD Value.

1. Type DisableCARetryOnInitialConnect.

1. Press and hold or right-click DisableCARetryOnInitialConnect, and then tap or click Modify.

1. In the Value data box, type 1, and then tap or click OK.

Exit Registry Editor.

[former_member182657]

Are you downloading & applying for correct OS platform.Please do verify once at your end.In addition share Event viewer logs as well.

Regards,

[Former Member]

I just followed the link and downloaded the hotfix,and the hotfix description says that it apt for windows 8 and server 2012 edition  .. can you specify how can i met the correct hotfix for the os platform?

regards,

Anoop

[Former Member]

Regards,

Anoop

[former_member182657]

Hi,

Could you share regional language of your system,If possible set it with English (United States).

or share the result from command intl.cpl.

After that could you try to install it again.

Regards,

[Former Member]

[former_member182657]

First maintain correct date & time for the system,additionally share the complete system information .Something fishy here

Thanks,

[Former Member]

Hi Anup,

Try to install the patch fix in compatible mode if you right click on the package and see the compatibility.

May be that might work.

regards,

Ram

[Former Member]

Hello Gaurav,

Sorry for misleading the issue.We couldn't actually apply the hotfix .We have downloaded the hotfix  from microsoft

While we try to install it ,it says cant be installed..And the windows update is up to date ,We have restarted the system once after the updation  was completed, also which was recommended by the system .

[former_member182657]

Could you share the error message where it's showing can't be installed ?

[TomCenens]

Just try out the test mentioned in SAP Note 1823833 - Accessing shares via SMB3.0 can result in long waiting times

If the test is fine, ignore the warning and proceed if possible

[Sriram2009]

Hi Anoop

During the installation you have to use the kernel 7.20 / 7.21 Ext (Without Ext Windows 2012 will not support). Kindly refer the SAP Note with General information point number 2

1732161 - SAP Systems on Windows Server 2012 (R2)

BR

SS

[Former Member]

For SAP systems based on SAP Netweaver 7.4x, only the 741 64 Bit kernel or newer are supported.

What does that mean ? Netweaver 7.4x will not support any other kernals?

here i'm using 721 64bit EXT kernal ..

Should that be the problem?

Do we need to download latest kernal for solman 7.1 ?

[Sriram2009]

Hi Anoop

1.  I mean that at the time of installation you have to use the kernel either 7.20  Ext or 7.21 Ext.

2. On your windows 2012 OS have you disable the firewall and UAC?

3. On Windows 2012 Check the time zone

BR

SS

[former_member182657]

For more on it just check the mentioned patch under Add/Remove Programs ---> View installed updates.If patch is there then proceed .

Good luck !!

[former_member182657]

Hi,

Have a look with SAP Note  1823833 - Accessing shares via SMB3.0 can result in long waiting times

So if mentioned Microsoft KB has already been successfully implemented without giving any type of errors or warnings then you could proceed your installations. (Depends after checking recent snap shot of the system ).

[Former Member]

Hai,

We apply the hotfix and restarted the system. But still shows that error.....

[former_member182657]

Could you share recent snap shot ?

[Sriram2009]

Hi Anoop

Before starting the SAP Solution Manager have you do the windows update from Microsoft site? Normally it download & update the all the secure patches from Microsoft site. and then start the SAP installation.

BR

SS

[former_member182657]

From the link which you shared

You must restart the computer after you apply this hotfix.

Hope this will help you.

Regards,

[former_member182657]

Have you applied the mentioned Microsoft KB 2820470 & restarted the system to retry ?

Thanks,

[Former Member]

hi Anup,

As suggested by Gaurav perform the KBA installtion and also do visit below page for more details on Microsoft 2012 R2 support for SAP.

As this requires a 7.21_EXT kernel for installation.

Do let us know if this helped you.

Regards,

Ram

[Former Member]

Hello Ram,

Current kernel version is Krnl_7.21_EXT_WIN__IA64__x64__SP08 .

Regards,

Anoop