unable to create RFC iviews - connection test of the system failed

[Former Member]

hello,

I always try to configure my system to run an RFC iView...

The connection of myt system is failed for 1 of the 4 tests.

i don't know why.

I have filled this fields :

- application host

- ITS host name

- ITS path

- ITS protocol

- Logical system name (not sure it's correct)

- Sap client

- Sap system ID

- SAP system number

- Server port (not sure it's correct)

- System type

- Web as host name

- Web as path

- Web as protocol

and i have this error :

SAP Web AS Connection

Test Details:

The test consists of the following steps:

1. Check the validity of the system ID in the system object

2. Check if the system can be retrieved

3. Check if a SAP system is defined in the system object

4. Validate the following parameters: WAS protocol; WAS host name

5. Check HTTP/S connectivity to the defined back-end application

Results

1. The system ID is valid

2. Retrieval of the system was successful

3. The system object represents an SAP system

4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)

5. HTTP/S connection successful

ITS Connection

Test Details:

The test consists of the following steps:

1. Check the validity of the system ID in the system object

2. Check if the system can be retrieved

3. Check if the system object has a valid system alias

4. Check if a SAP system is defined in the system object

5. Validate the following parameters: ITS protocol; ITS host name

6. Check the validity of any user mapping in the system object

7. Check HTTP/S connectivity to the defined back-end application

Results

1. The system ID is valid

2. Retrieval of the system was successful

3. Retrieval of the default alias was successful

4. The system object represents an SAP system

5. The following parameters are valid: ITS Protocol (http) ITS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)

6. HTTP/S connection successful

Test Connection with Connector

Test Details:

The test consists of the following steps:

1. Retrieve the default alias of the system

2. Check the connection to the backend application using the connector defined in this system object

Results

Retrieval of default alias successful

Connection failed. Make sure user mapping is set correctly and all connection properties are correct.

Test Connection through the DQE

Test Details:

The test consists of the following steps:

1. Checks the existence of a backend admin user ID/password in the system properties.

2. Checks the existence of a default alias for the system.

3. Checks the DQE connection.

Results

1. DQE admin user ID or password is missing in the system properties. Make sure those properties exist for this system object.

2. Default alias of the system exists.

3. DQE connection successful. If you continue to experience problems, verify the DQE admin user ID and password properties for this system object.

can you help me to end this configuration?

thanks a lot.

(reward points for helful answers...)

Adrien

[Former Member · Accepted solution]

Hi Adrien,

Have you setup an Alias for the system? Setup the alias and configure the user mapping for the system. You should do fine then.

Hth,

Sameer

P.S - the default server port is 3200, ask your Basis guys in case 3200 doesnt work.

[Former Member · Accepted solution]

hello Sameer

Is it possible to create an RFC iView with a "SAP system with load balancing" ?

My user mapping don't find this system (i have created my system with load balancing).

What are the kinds of system should we create for running correctly an RFC iViews.

in fact, i don't really know what is the user mapping. I think it's used to connect ourself in another system (like SAP?) but i'm not sure... I'm in a wrong way?

Thanks.

[Former Member · Accepted solution]

Hi Adrien,

Yes it is possible to create an RFC view based on an SAP system with load balancing.

You are right about user mapping. User mapping is done so that your current system (where the user mapping is defined) sends the login information (your username and password in this case) automatically to the remote system (R/3 for example).

Thus, whenever you would call your RFC iView from that particular R/3 system, it is checked if you have provided the necessary access rights for logging on and using that system.

To set up user mapping on your system, you will first need to set up an alias. This alias name for your system is used by NetWeaver to identify the backend remote system.

To set up the alias, do the following - first open the system you created to edit it's properties. Above the properties on the right, you see a "Display" drop down box. There select "System Alias". Give in any name you wish as the system alias and select add.

Now click the personalize button (or go to User Administration and select that user). You should see the system for User Mapping (under the name you gave above).

Add in the user name and password for the user in the backend R/3, and try the connection tests again.

I think that should set you up proper

Bye!

Sameer

[Former Member · Accepted solution]

great, very helpful !!!

i work on this and i come back if another error come...

Thanks a lot !

Message was edited by:

Adrien Loire

[Former Member · Accepted solution]

Aha! Sorry but forgot a small point there

You need to open your system properties again. In the Property Category drop down box, select "User Management".

Here you should see four fields. For the logon method property, select UIDPW. As the name suggests, this indicates to the system that it is a User ID and Password logon method.

For the last property (the fourth one), select "admin,user" as the User mapping type. In case you want only the Administrator to do the user mapping, select just "admin" or in the case of user, select "user".

Selecting "admin,user" allows the admin to change the property in case the user does something wrong.

After changing that, save it and you should be able to carry out the user mapping as usual.

Bye!

Sameer

[Former Member · Accepted solution]

héhé, i find this just after my post... Sorry for this 🐵

I have make a big progress in the comprehesion of my problems, but my system and my connection test are always down.

Now, i Really think it's my Server Port and my Logical System Name

How find this???

(i have an error in the creation of the RFC iView and my test connection is alway ths same, with an error on the connector.)

[Former Member · Accepted solution]

Hi Adrien,

Did you try with the server port 3200? Any logical name should be all right (I generally use the same logical name as the one I give in during the creation). Only make sure that the logical name has no special characters (underscores are all right though).

In case the server port 3200 (the 00 is for the instance number of your R/3) does not work, could you please list the values you gave for the properties here? Also try setting up another test system with a dedicated server (with the same properties you have currently) and then test it's connection too.

Bye,

Sameer

P.S - At the same time, also call up your Basis people and ask them for the exact server port (tell them you dont want the Message Port number which should be 3600 by default).

Here is another test you can carry out - if you have the entry for the R/3 you are trying to use as a backend in your SAPGui logon, check the system number for that system and add that to the port number. For example, if the system number is 01, then your port will be 3201.

[Former Member · Accepted solution]

Hi Sameer.

Thanks again for your answer.

port 3200 doesn't work and it's the same for 3248 (my ssn is 48...). maybe the problem come from another thing?

i've made an error before... My system always was a dedicated server and not with load balancing. Sorry.

i list all the values i gave for the properties...

- Application host : wsapv49.dhcp.xxx.xx.xxxx

- ITS Host name : wsapv49.dhcp.xxx.xx.xxxx:8045

- ITS Path : /sap/bc/gui/sap/its/webgui

- ITS protocol : Http

- Logical system name : RBDCLNT800 (on an advice on a sdn forum user)

- Sap Client : 800

- SID : RBD

- Sap system number : 45

- Serveur port : 3200

- Web as host name : wsapv49.dhcp.xxx.xx.xxxx:8045

- Web as path : /sap/bc/gui/sap/its/webgui

- Web as protocol : Http

test connection always down

[Former Member · Accepted solution]

Hallo Adrien,

Your SAP system number is 45, so your server port should be 3245 not 3248. Try with that, I am also assuming that you have now created a new system based on the dedicated R/3 template instead of the load balancing?

Salut ,

Sameer

[Former Member · Accepted solution]

rhaaa I am so thoughtless

I repeat 🐵

i would obviously say 45 in my previous post...

I never made a system with load balancing. I've only made the dedicated one (it's a mistake)...

I'm sorry for all, i'm beginner with SAP (i'm starting with the portail), i'm not very good in english, and i say anything when i try to explain my problems !!

thanks for your patience

and "salut" ,

Adrien

[Former Member · Accepted solution]

Hello Adrien,

Don't worry about being a beginner, I remember my days too as a beginner with the NetWeaver system :). As far as your english goes, its quite fine. Much better than my french actually, in case I don't understand you, I will ask for a clarification (which I doubt considering your english ).

Try the following settings. They are the basic ones you need in any case to set up a connection. Just check them again and try the connection. You can find the following parameters easily if you set the Property Category to "Connector". I have a strange feeling about the server name you gave in so try with the IP address of your R/3 system. I do not think that it is the same system as your DHCP server. You should be able find the IP address of your system in your SAPLogon pad.

Application Host - IP address of your R/3 system (NOT sapv49.dhcp.ptx.fr.sopra).

Logical System Name - RBDCLNT800

Remote Host Type - 3

SAP Client - 800

SAP ID (SID) - RBD

SAP System Number - 45

Server Port - 3245

System Type - SAP_R3

Also ping the IP address of your R/3 system first to make sure you can reach it. Does the System now show up for a user mapping? You will have to do the user mapping completely too for a successful test of the connector.

Bye,

Sameer

[Former Member · Accepted solution]

guten Tag (thanks google),

ok -

i have found the ip adress and i have remplaced it for the application host.

all the others fields are like yours.

in my user mapping, i think i have made everything.

I choose my user, i put him with the system alias. I put too the r/3 system user and pw.

==> Always an error in the test connector :'( -- Even if the 3 others are always running well --

it would be too bad to stop here, i'm so near to my goal with the RFC iViews (I'm fighting with them since 2 weeks)

[Former Member · Accepted solution]

Guten Tag to you too Adrien (Google helped you correctly )!

Man getting your system running has just now become my life's number one goal. We will fight to the end

Ok, so you have the IP address of your SAP R/3 server and the rest of the fields are set too. Let's go over this step by step.

The properties are now set (although the server port could be problematic. Ask your SAP Basis/Administrator again for the correct port, tell him what port no. you are using).

I will now describe how to set the user mapping step by step even though I think you have done it correctly.

1) Log on to the Portal as the Administrator. Go to the tab User Administration.

2) Under Identity Management, search for "Administrator" (not any other user, let's test with Administrator only). Click on the row in the search results when the search is over.

3) Below, you should be see the "User mapping" tab as the last one. Here, in the drop down box for System, your RBD system should be visible. Select it and click modify.

4) Enter <u>your username and password for the R/3 system</u> - the same username and password you use to logon from the SAPGui for the R/3.

5) Click "Save" and you should see (X) after the system name to signify the mapping has been done.

Go back to System Administration -> System Configuration and in the Display drop down box, select "Permissions". Search for the "Everyone" group and add it. After you add it, select the Administrator drop down box to "Full Control" and most important - tick the box for "End User".

Save and test the system's connector again.

In case it fails again, go to the link http://<yourNetWeaverServer>:<ServerPort>/nwa.

Login as Administrator, and go to Analysis (top menu bar) then Debug on the second level menu.

Beside the drop down box "Show", select predefined view and in <Select View> select Default Trace. This will show you the logs of what went wrong when you tested your system. Check for the time and the error beside it.

In case the test does not work, could you please copy the error entries in the log files here?

Regards,

Sameer

[Former Member · Accepted solution]

doesn't work, doesn't work... :o(

I found this in "analysis" -> "Debug"

-

---

error 3 mai 2007 16:49:32:168 Failed to get connection for system final

/System/Server com.sap.portal.ivs.connectorService sap.com/irj admin ITEM-31892 Server 0 0_33638

-

---

error 3 mai 2007 16:49:32:168 (R3/BW) Failed to get connection. Please contact your admin.

/System/Server com.sap.portal.connectors.R3 sap.com/irj admin ITEM-31892 Server 0 0_33638

-

---

i found too a -BIG- file in the directories, "last block" of the file

-

---

#1.5#000D56D8CEA2005D0000001500000FC400042F9201A5E5D2#1178204046283#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.

The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.

Exception id: [000D56D8CEA2005D0000001300000FC400042F9201A5E071]#

#1.5#000D56D8CEA2005D0000001600000FC400042F9201A76132#1178204046383#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.

at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:209)

at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:193)

at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:952)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

#

#1.5#000D56D8CEA2005D0000001800000FC400042F9201A765B7#1178204046383#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)].

The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.

Exception id: [000D56D8CEA2005D0000001600000FC400042F9201A76132]#

-

---

and with another test connector

-

---

#

#1.5#000D56D8CEA200600000001800000FC400042F921D02D625#1178204505301#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.

The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.

Exception id: [000D56D8CEA200600000001600000FC400042F921D02D1AE]#

#1.5#000D56D8CEA200560000001600000FC400042F921D39B77B#1178204508896#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tc_wddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> enter#

#1.5#000D56D8CEA200560000001700000FC400042F921D3AE547#1178204508977#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tc_wddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###connectToSystem()->Selected Systemnull#

#1.5#000D56D8CEA200560000001800000FC400042F921D3BE964#1178204509037#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#sap.com/tc_wddispwda#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###getElement(String, Filter, int):NamedLocatedElement!ConfigManagerReader.SEARCH_FOR!CTC#

#1.5#000D56D8CEA200560000001900000FC400042F921D414CF2#1178204509397#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tc_wddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> leave success#

#1.5#000D56D8CEA200560000001A00000FC400042F921E69A639#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tc_wddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> enter#

#1.5#000D56D8CEA200560000001B00000FC400042F921E69A953#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tc_wddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> success#

#1.5#000D56D8CEA2006E0000010500000FC400042F9231C81C6F#1178204853786#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #

#1.5#000D56D8CEA204E70000000100000FC400042F9231C90EA8#1178204853846#com.sap.engine.services.dqe#sap.com/irj#com.sap.engine.services.dqe#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#Thread[Log_Worker_6,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server/DQE#Plain###mai 03, 2007 17:07:33.786 [SAP_HOST|4039|SAPEngine_Application_Thread[impl:3]_9] <CONNECTOR.ERROR> Error trying to establish connection to the EIS : final Connection Failed: Nested Exception. Failed to get connection. Please contact your admin. #

#1.5#000D56D8CEA200690000001E00000FC400042F92335B4C9E#1178204880215#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #

#1.5#000D56D8CEA200690000002000000FC400042F92335B4FE3#1178204880215#com.sap.portal.ivs.connectorService#sap.com/irj#com.sap.portal.ivs.connectorService#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Java###Failed to get connection for system #1#final#

-

---

i happy to carry my life's number one goal with another guy

(thanks, again and again)

Adrien

Message was edited by:

Adrien Loire

[Former Member · Accepted solution]

Hi Adrien,

Sorry for replying this late but I was completely flooded with work.

Your logs did not help me much but here are some more ideas - I see that you are logging on as admin. I don't know if it's the same as the Administrator as far as roles, groups and permissions go, but I would suggest logging on as Administrator when testing just to be sure. Another thing, your system is named ITEM-31892. Remove the "-" from the name. Maybe there is something wrong when you have "-" although I doubt it. Another thing, make sure that in the "Connector" property category of your system, you have set the value SAP_R3 for the property System Type. The remote host type should also be 3.

Also do this - go to \WINDOWS\system32\drivers\etc (on your system where NetWeaver is installed). There you will find a file called Services. Open it in a test editor and add the following anywhere in the file on a new line-

sapmsRBD 3645/tcp

The 36<SystemNumber> is the message server port of your R/3 system, and the sapms<SID> identifies which system it is.

Test again. In case it also does not work, try registering your system in the SLD. Go to http://<ServerName>:<ServerPort>/sld. Login as Administrator and click on Technical systems. Select WEB AS ABAP and here are the steps that will help you in registering the system -

1) Select Web AS ABAP

2) For the Installation Number, Database Host, log in to your R/3 system and click on System -> Status in the top menu bar. The Database host name is found under Database Data.

3) Message Server Port = 36<SystemNumber>, Instance Number = System Number

4) Leave the Application Servers part and go to the next step.

5) Client (at least one client needed, no need to give the logical client name).

6) For the Installed Products select SAP ERP 2004 or ECC 5.0 depending on what is installed and on the right hand side select "All".

7) Make sure to add the sapmsT03 3600/tcp entry in the services file as described above.

😎 Restart your NetWeaver system.

Try testing again. In case the setup still doesn't work, can you send me ALL your parameter values (except for the IP address of course) that you gave in for the connector again? (Exactly as you have set the values)

Bye!

Sameer

[Former Member · Accepted solution]

hurrah !!!!!!!!

all my testes are OK !

i've changed application Host, Server port and the file "Services" so i don't know where was the problem, but i think it's the file.

3 weeks for my system... next step now

[Former Member · Accepted solution]

Woohoo!

I'll have a beer this weekend for this glorious end to your problem!

Sameer