on 12-28-2006 2:16 PM
i'm trying to deploy par file
all my setting are right, but i get error that i see in sap-plugin.log file
Server returned HTTP response code: 401 for URL: http://sapepdev:50100
does anyone knows how to fix that problem?
is my "nwds-> preference-? workbench-> proxy " settings should be like the settings in the browser?
thanks
Roni
oss found out that spnego configuration cause that problem. we uninstalled spnego and now its working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The correct note number is 995785. At the time the note had not been released to customers. SAP attached the following to my oss message.
This note will be released when sp 11 is released. The relevant
section for you states:
- Problem with failed fallback to basic password authentication after
SPNego authentication failure caused by UME exception during the
resolution of the user name has been fixed.
I also asked if sap would provide a patch for previous support packs:
their response:
Development have indicated that due to the complex nature of this, that
they are unwilling to downgrade the patch to earlier versions.
The problem is when deploying applications from NWDS, NWDS user uid and password for authentication. The 401 error we are seeing in the logfile is because we are deploying applications to a WAS that is configured to use SPNEGO with a fall back scenario of basic authentication (uid and password) and their is a bug in handling the fall back. This problem I am seeing in our development environment. I have been able to deploy apps from NWDS to our test system. I thinks the reason it is working is the differences between the hardware configurations of our dev and test systems and what service principle names (SPN) that was used in the kerbrose keytab file.
Our dev environment consists of one app server and one db server. When configuring SPNEGO we used the hostname as the SPN in the kerbrose config.
Our test environment consists of two app servers which are VIP'ed (Virtual IP) and two db servers that clustered (MSCS and oracle Fail Safe). When configuring SPNEGO for this environment we used the VIP name as the SPN in the kerbrose config.
In NWDS I configured the portal connection to our test system to use the VIP. When using this configuration I get the deployment error. I then re-configure the portal connection to use one of the WAS hostnames for our test system. With this configuration I am able to deploy applications to the WAS.
I am currently working on creating a vip around our dev environment to see if this solves our problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here was SAP's response:
"From the attached traces, the problem seems to be the known issue of
Basic Authentication fallback when using Spnego. This bug is fixed
with SP11. See Note 95785 for more details on this patch."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill,
Thanks for the info. I checked note #95785 and it came up with a note related to the R/3 FI module. I figured maybe a digit was missing so I checked notes 957850-957859 and none of those seemed to be related to spnego at all. Do you remember what the text of the header of the note was? I looked for "spnego" at service.sap.com and the notes that came up didn't seem relevent to this problem but maybe I missed something.
Hi Roni,
I would suggest you to check your defaultTrace.trc file on the sever, to check for Exception after your deployment fails.
If you see there exception message: <b>com.sapportals.portal.prt.runtime.PortalRuntimeException: Access is denied: com.sap.portal.runtime.system.console.ArchiveUploader - user: Guest,</b>
Then it is for sure that your username/password is incorrect.
My tip is: Check that your password does not contain special char <b>%</b>, this is a bug in NWDS. NWDS has encoding problems with special char <b>%</b> in your password, so you password is corrupt even though you give right one in NWDS.
So check your password, I have seen problem only with <b>%</b>, but there could be some more chars that have this behaviour.
Greetings,
Praveen Gudapati
p.s. Pointa are always welcome for helpful answers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What happens when you use the URL http://sapepdev:50100/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.syst...?
(Without the closing ?)
You should see the PAR upload screen
Cheers
Hi Roni,
Are you trying to upload the par file from the NWDS?
If that is the case, you should configure the server under NWDS>>Window>>Preferences>>SAP J2EE engine.
Here, if you are using a remote host, fill in the details with IP address and port as 3900. Else fill in the details of the local host.
Once you configure you J2EE engine, you have to use SDM password for the deployment.
Also there is an alternate way for uploading the par file.
Log in to the portal with proper administrator/ any user login credentials, and go to Java Developer>>Tools>>Portal Archive Deployer and Remover.
Here you can browse for the par file upload and run it in Portal Component Starter and Viewer.
Regards,
Sujana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I do have a solution to this problem yet.... I have opened an OSS message with SAP on this problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Roni, I am having the same problem.... do you have spnego configured on the system you are trying to deploy to?
Have you resolved this issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
does anyone knows how to fix that problem in par file deployment ?
HTTP response code: 401
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Roni,
You may get this error when you have a problem with (userid, password) configured in NWDS. You may want to logon to the http://sapepdev:50100 using the same userId and password configured NWDS. Also try to deploy using another portal account with admin rights.
What does your sap-plugin.log say on your local system?
Cheers,
the error in sap-plugin.log is:
[02.01.07 / 11:05] #ERROR LEVEL# com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1 > No Information
java.io.IOException: Server returned HTTP response code: 401 for URL: http://sapepdev:50100/irj/servlet/prt/portal/prteventname/upload/prtroot/com.sap.portal.runtime.syst...
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:800)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.readResponse(DeployEngine.java:363)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.uploadPar(DeployEngine.java:435)
at com.sap.portal.developmentTools.general.wizards.upload.DeployEngine.deploy(DeployEngine.java:221)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.processUpload(SAPMPWizard.java:416)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard$1.run(SAPMPWizard.java:350)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:302)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:252)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:758)
at com.sap.portal.developmentTools.ideSpecific.eclipse.wizards.sapmakepar.SAPMPWizard.performFinish(SAPMPWizard.java:531)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
at org.eclipse.jface.window.Window.open(Window.java:563)
at org.eclipse.ui.actions.ExportResourcesAction.run(ExportResourcesAction.java:112)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:842)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Hi Roni,
I also faced the same problem, while deploying the par file.So please check your User-Id and Password.These credentials you are providing at the time of ur Initial Par file Deployment >Server Configure Settinngs...
Again you gave the password there w.r.t the user.
Hope this will rectify your problem.
Regards
Ganesh
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.