NewInst.cmd not working!

[Former Member]

Dear all,

I having this situation whereby i installing a SAP 4.7 ext 2.0 on a NT base OS.

After installing the CI(central instance), i need to run this newinst.cmd so i can continue my installation of DATABASE instance. but when i run it, it prompt me that the " 'findstr' is not recognised as an internal or external command, operable program or batch file"

what could be possibly causing this?

I run this newinst.cmd a few times before and it work fine for me until i uninstalled the oracle software(not database instance) recently.

as for temporary solution, i rename the folder C:\Program Files\sapinst to sapinst.bak and run the sapinst.exe again to generate new sapinst folder.

Will there be any impact to the system if i do so?

Kindly help to solve my problem, thanks

regards,

Jerry

[JPReyes · Accepted solution]

Hi Jerry,

"findstr" is a windows command to find pieces of data on strings (or something like that) and seems to be missing from your os or maybe the path to this command is not set in the env variables.

Do a search for this file on your OS and add the path to the env variables so you can call it from any location. Otherwise you'll need a fresh OS installation.

Regards

Juan

[Former Member · Accepted solution]

"Do a search for this file on your OS and add the path to the env variables so you can call it from any location. Otherwise you'll need a fresh OS installation."

What file should i search from my OS?

[Former Member · Accepted solution]

My newinst.cmd still not working ....whenever i run it, the command prompt close itself.

could the problem relate to environment variable or registry entries?

Anyone please help?

[JPReyes · Accepted solution]

Search for file findstr.* should be located at C:\windows\system32 if its not there you now what the problem is.

Regards

Juan

[Former Member · Accepted solution]

There's findstr.exe in the system32 folder, so meaning the file still there, but the path in environment variable wrong?

[JPReyes · Accepted solution]

Hi Jerry,

That will be my next step... check that path exist for c:\windows\system32 in the enviromental variables

Regards

Juan

[Former Member · Accepted solution]

under what variable name? i checked under user variable and system variable, none of it have the path of <drive>:\windows\system32\findstr.exe

Kindly advise what variable to add? how do i know the variable will be call by the NewInst.cmd?

[JPReyes · Accepted solution]

just add <drive>:\windows\system32\ (without the filename, just the path) to system variables.

A variable tell the system that the commands under the path can be executed from the command prompt without calling the directory.

Regards

Juan

[Former Member · Accepted solution]

thanks! it work! i added <drive>:\windows\system32\ under the variable name "PATH" and it work.

Thanks so much! and now i understand more about the environment variable and how this system variable work.