<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-36900394</id><updated>2011-04-21T21:54:37.338-04:00</updated><title type='text'>Remedy ARS</title><subtitle type='html'>This blog is for discussions regarding the BMC/Remedy Action Request Server product.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://remedy-ars.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://remedy-ars.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Steve</name><uri>http://www.blogger.com/profile/11659696729706771552</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://photos1.blogger.com/img/187/3099/640/WPAPM.2.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>7</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-36900394.post-2889977207543886705</id><published>2008-11-03T09:20:00.002-05:00</published><updated>2008-11-03T09:29:26.521-05:00</updated><title type='text'>Bizarre things</title><content type='html'>Haven't posted in a while.  Been too busy trying to fix things that shouldn't be broken in the first place.&lt;br /&gt;&lt;br /&gt;The project I am on recently upgraded to Remedy Version 7.1 patch 4.  We had previously done a lot of testing on our staging server with no issues.  Soon after we upgraded the Production server, all manner of hell broke loose.  &lt;br /&gt;&lt;br /&gt;First, BMC changed the way Remedy handles the ARDBC LDAP plugin's date formats.  In 6.03, dates coming from an Active Directory were handled correctly. For instance, if I used a Vendor table pointing to an AD class through the LDAP to search for records that had been recently modified, I could run a query like:&lt;br /&gt;&lt;br /&gt;     modifyTimestamp &gt;= "2008/10/31 7:00:00 AM"&lt;br /&gt;&lt;br /&gt;This, of course, would return all records modified since 7AM on the 31st.  6.03 converted that date into 20081031070000.0Z.  Version 7.1 converted it to 20081031070000Z.  Note the subtle difference.  This would cause a No Matching Requests popup.&lt;br /&gt;&lt;br /&gt;What I discovered is that I had to set a new field on the LDAP Configuration form called &lt;span style="font-weight:bold;"&gt;LDAP Date-Time Format&lt;/span&gt; to &lt;span style="font-style:italic;"&gt;AD Generalized Time&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;Our testing showed no problem since, as per usual, our staging environment can't link to the AD.  So, we couldn't really test the LDAP.  Fun, eh?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/36900394-2889977207543886705?l=remedy-ars.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://remedy-ars.blogspot.com/feeds/2889977207543886705/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=36900394&amp;postID=2889977207543886705' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/2889977207543886705'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/2889977207543886705'/><link rel='alternate' type='text/html' href='http://remedy-ars.blogspot.com/2008/11/bizarre-things.html' title='Bizarre things'/><author><name>Steve</name><uri>http://www.blogger.com/profile/11659696729706771552</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://photos1.blogger.com/img/187/3099/640/WPAPM.2.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-36900394.post-116307666914447798</id><published>2006-11-09T07:31:00.000-05:00</published><updated>2006-11-15T15:06:53.413-05:00</updated><title type='text'>Mid Tier bug with IE</title><content type='html'>Interesting bug I discovered in Remedy's Mid Tier application which only occurs with IE (6.0.2800).&lt;br /&gt;&lt;br /&gt;I have a field on a control panel into which I can type the last several numbers of a &lt;b&gt;&lt;i&gt;Request ID&lt;/i&gt;&lt;/b&gt;.&lt;br /&gt;&lt;p&gt;&lt;a href="http://photos1.blogger.com/blogger/1108/385/1600/IEMidtierBug_1.1.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center;" alt="" src="http://photos1.blogger.com/blogger/1108/385/320/IEMidtierBug_1.1.jpg" border="0" /&gt;&lt;/a&gt;Clicking ENTER while the field has the focus cause Active Links to trigger on &lt;i&gt;return&lt;/i&gt;. The code pads the numbers with the prefix of the &lt;b&gt;&lt;i&gt;Request ID&lt;/i&gt;&lt;/b&gt; and using the EXTERNAL keyword creates a qualification statement for a table field. &lt;/p&gt;&lt;p&gt;&lt;a href="http://photos1.blogger.com/blogger/1108/385/1600/IEMidtierBug_2.0.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center;" alt="" src="http://photos1.blogger.com/blogger/1108/385/320/IEMidtierBug_2.0.jpg" border="0" /&gt;&lt;/a&gt; Then it refreshes the table field and the record is displayed. If I change the last number of the &lt;b&gt;&lt;i&gt;Request ID&lt;/i&gt;&lt;/b&gt; and again hit ENTER, the new record is displayed in the table field (on the USER TOOL at least).&lt;br /&gt;&lt;a href="http://photos1.blogger.com/blogger/1108/385/1600/IEMidtierBug_3.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center;" alt="" src="http://photos1.blogger.com/blogger/1108/385/320/IEMidtierBug_3.jpg" border="0" /&gt;&lt;/a&gt; However, in IE, if I hit ENTER that second time nothing happens. If I manually remove the prefix and hit ENTER it works.&lt;br /&gt;&lt;br /&gt;I tried playing around with code, and created a final active link that has no qualification statement that simply triggers if I click ENTER while the field has the focus. A message is displayed:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://photos1.blogger.com/blogger/1108/385/1600/IEMidtierBug_6.0.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center;" alt="" src="http://photos1.blogger.com/blogger/1108/385/320/IEMidtierBug_6.0.jpg" border="0" /&gt;&lt;/a&gt; &lt;/p&gt;&lt;p&gt;Now, as I mentioned, If I change the last number to an 8 again, and hit ENTER, I don't get that message. Which means that the MID TIER is not interpreting a keystroke (ENTER key) when using IE.  However, this works fine if I use Firefox (NOTE: I haven't tested IE 7.0 yet).&lt;/p&gt;&lt;p&gt;This is what I discovered. The field is 15 characters long.  If there were 15 characters in the field, IE/Mid Tier would not interpret the ENTER keystroke.  When I increased the field's data length to 16 characters , the ENTER keystroke was interpreted correctly!&lt;/p&gt;&lt;p&gt;To test this simply create a display-only form with one field (15 characters). Create an Active Link which triggers on &lt;em&gt;return&lt;/em&gt; and displays a Message. Then open the form via IE and type in less than 15 characters. Click ENTER and view the message. Now fill the field with 15 characters. Hit ENTER again. Doesn't work!&lt;/p&gt;******************************************************************************&lt;br /&gt;&lt;span style="font-weight: bold; color: rgb(255, 0, 0);"&gt;UPDATE:  Apparently, this was a known bug fixed in patch 19.  Why this bug wasn't listed in the Knowledge base I don't know.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/36900394-116307666914447798?l=remedy-ars.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://remedy-ars.blogspot.com/feeds/116307666914447798/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=36900394&amp;postID=116307666914447798' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116307666914447798'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116307666914447798'/><link rel='alternate' type='text/html' href='http://remedy-ars.blogspot.com/2006/11/mid-tier-bug-with-ie.html' title='Mid Tier bug with IE'/><author><name>Steve</name><uri>http://www.blogger.com/profile/11659696729706771552</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://photos1.blogger.com/img/187/3099/640/WPAPM.2.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-36900394.post-116247598054939390</id><published>2006-11-02T08:56:00.000-05:00</published><updated>2006-11-15T14:42:08.696-05:00</updated><title type='text'>Active Link Caching</title><content type='html'>Had an interesting problem with a lag on the load of a Control Panel.  Noticed in the client-side database log that the Active Links for a form being referenced in a table field were being cached to the workstation.  We thought this odd, since we weren't actually LOADING the form, just refreshing a table field that pointed to the form.&lt;br /&gt;&lt;br /&gt;The official response from Remedy was that the Active Links are cached in order that a table double-click to open a record will do so smoothly and quickly (since the ALs have already been cached).  What if I don't want that to happen (i.e. I would rather have the lag happen WHEN and IF they cause that form to open, NOT when they simply look at a record in a frikkin' table!).&lt;br /&gt;&lt;br /&gt;How stupid is that?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/36900394-116247598054939390?l=remedy-ars.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://remedy-ars.blogspot.com/feeds/116247598054939390/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=36900394&amp;postID=116247598054939390' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116247598054939390'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116247598054939390'/><link rel='alternate' type='text/html' href='http://remedy-ars.blogspot.com/2006/11/active-link-caching.html' title='Active Link Caching'/><author><name>Steve</name><uri>http://www.blogger.com/profile/11659696729706771552</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://photos1.blogger.com/img/187/3099/640/WPAPM.2.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-36900394.post-116247534887659555</id><published>2006-11-02T08:41:00.000-05:00</published><updated>2006-11-15T14:42:08.535-05:00</updated><title type='text'>Web Services</title><content type='html'>We have another odd bug with the Remedy ARS Web Services functionality.  If we create a simple web service to create a record in a form (table), and consume it using &lt;a href="http://www.crosschecknet.com"&gt;SOAPSonar&lt;/a&gt;, we get a warning that there is an:&lt;br /&gt;&lt;blockquote&gt;This is an unexpected token.  The expected token is "SEMICOLON".  Line 57, position 88&lt;/blockquote&gt;&lt;br /&gt;Followed by:&lt;br /&gt;&lt;blockquote&gt;Object reference not set to an instance of an object.&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Odd since Remedy tech support recommended SOAPSonar as a web service testing tool.&lt;br /&gt;&lt;br /&gt;However, the Web Service is consumed and works correctly.  We can create a record and get the Request ID returned.&lt;br /&gt;&lt;br /&gt;If we use VB.Net to build an application which consumes the Web Service, we can also successfully create a record in ARS.  Unfortunately, we usually don't get a return value.  There is no error, just nothing.&lt;br /&gt;&lt;br /&gt;Since we cannot contact Remedy's Tech Support directly, we have to go through a third party support centre.  They have asked for Logs which have shown nothing (we already knew that) and have claimed they cannot reproduce the problem.  We thought that was odd, and asked them for a def file and VB code which they used to attempt to replicate the issue.  Their answer:  "They don't have the space to keep all the stuff around, so they deleted it".  Snort.&lt;br /&gt;&lt;br /&gt;So, we have no idea if Remedy has even been contacted regarding this issue, or whether someone is just blowing smoke up our asses.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/36900394-116247534887659555?l=remedy-ars.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://remedy-ars.blogspot.com/feeds/116247534887659555/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=36900394&amp;postID=116247534887659555' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116247534887659555'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116247534887659555'/><link rel='alternate' type='text/html' href='http://remedy-ars.blogspot.com/2006/11/web-services.html' title='Web Services'/><author><name>Steve</name><uri>http://www.blogger.com/profile/11659696729706771552</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://photos1.blogger.com/img/187/3099/640/WPAPM.2.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-36900394.post-116238518837283276</id><published>2006-11-01T07:41:00.000-05:00</published><updated>2006-11-15T14:42:08.420-05:00</updated><title type='text'>Active Link Guide permissions</title><content type='html'>I am using version 6.03 Patch 18 of the ARS, and patch 16 of the Admin Tool.  I believe any version of the Admin tool prior to and including patch 16 has this bug.&lt;br /&gt;&lt;br /&gt;Ensure you have your default permissions set, specifically for Active Link guides for this issue.  Create a new Active Link guide, name it, and select the form.  DO NOT click on the Permissions tab.  Add any number of Active Links to the guide, and save it and close it.  &lt;br /&gt;&lt;br /&gt;Now reopen the guide and look at the Permissions tab...no permissions.  Fun, eh?  Apparently, this has been fixed with Patch 17 (forthcoming) of the Admin tool.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/36900394-116238518837283276?l=remedy-ars.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://remedy-ars.blogspot.com/feeds/116238518837283276/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=36900394&amp;postID=116238518837283276' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116238518837283276'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116238518837283276'/><link rel='alternate' type='text/html' href='http://remedy-ars.blogspot.com/2006/11/active-link-guide-permissions.html' title='Active Link Guide permissions'/><author><name>Steve</name><uri>http://www.blogger.com/profile/11659696729706771552</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://photos1.blogger.com/img/187/3099/640/WPAPM.2.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-36900394.post-116231777953082073</id><published>2006-10-31T12:56:00.000-05:00</published><updated>2006-11-15T14:42:08.280-05:00</updated><title type='text'>The new BMC/Remedy support site</title><content type='html'>Well...if you have had any dealings with Remedy in the past, you will know that their support site was never the best in terms of layout or navigation. Unfortunately, it just got worse.&lt;br /&gt;&lt;br /&gt;The first thing facing you when you first encounter the new support site is the following:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://photos1.blogger.com/blogger/1108/385/1600/RemedySupport_1.1.jpg"&gt;&lt;img style="DISPLAY: block; MARGIN: 0px auto 10px; CURSOR: hand; TEXT-ALIGN: center" alt="" src="http://photos1.blogger.com/blogger/1108/385/320/RemedySupport_1.1.jpg" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Clicking on Login gives you a normal looking Login screen, however, you no longer type in your User ID. Now it asks for your email address.&lt;br /&gt;&lt;br /&gt;Once logged in, you are presented with this:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://photos1.blogger.com/blogger/1108/385/1600/RemedySupport_3.jpg"&gt;&lt;img style="DISPLAY: block; MARGIN: 0px auto 10px; CURSOR: hand; TEXT-ALIGN: center" alt="" src="http://photos1.blogger.com/blogger/1108/385/320/RemedySupport_3.jpg" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Choosing the Knowledge Base link under the heading &lt;b&gt;Remedy and Marimba Heritage Customers&lt;/b&gt; opens the Advanced Search Knowledge Database page:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://photos1.blogger.com/blogger/1108/385/1600/RemedySupport_6.jpg"&gt;&lt;img style="DISPLAY: block; MARGIN: 0px auto 10px; CURSOR: hand; TEXT-ALIGN: center" alt="" src="http://photos1.blogger.com/blogger/1108/385/320/RemedySupport_6.jpg" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This is where it gets problematic. If all you want to do is search for, say, an issue with Active Link Guide permissions, you would think you just type in some keywords and off you go. Nope. Note the line in bold and italics that reads:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;b&gt;&lt;i&gt;If no Product is selected, then the current Product List will be applied in the Search&lt;/b&gt;&lt;/i&gt;&lt;/blockquote&gt;&lt;br /&gt;So, what is meant by &lt;b&gt;&lt;i&gt;"...the current Product List..."&lt;/b&gt;&lt;/i&gt;?  Here's the FIRST PAGE!:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://photos1.blogger.com/blogger/1108/385/1600/RemedySupport_7.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://photos1.blogger.com/blogger/1108/385/320/RemedySupport_7.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Look at it!  I mean, the list is hideous!  The returned results aren't bad, but not as clean looking as they once were:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://photos1.blogger.com/blogger/1108/385/1600/RemedySupport_8.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://photos1.blogger.com/blogger/1108/385/320/RemedySupport_8.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Note the absence of a version number?  This is annoying.  As well, when you search, you cannot choose the version number.  In the section in the Search page there is a field to the right of the &lt;b&gt;Product&lt;/b&gt; field in which you can select &lt;i&gt;All Products&lt;/i&gt; or &lt;i&gt;My Products List&lt;/i&gt;.  Trust me, that option doesn't help.&lt;br /&gt;&lt;br /&gt;I don't know what rationale BMC has for this, except for cost savings.  Since it offers nothing to clients.  Explore the site and you will see how terrible it is.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/36900394-116231777953082073?l=remedy-ars.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://remedy-ars.blogspot.com/feeds/116231777953082073/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=36900394&amp;postID=116231777953082073' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116231777953082073'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116231777953082073'/><link rel='alternate' type='text/html' href='http://remedy-ars.blogspot.com/2006/10/new-bmcremedy-support-site.html' title='The new BMC/Remedy support site'/><author><name>Steve</name><uri>http://www.blogger.com/profile/11659696729706771552</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://photos1.blogger.com/img/187/3099/640/WPAPM.2.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-36900394.post-116231209472509265</id><published>2006-10-31T11:27:00.000-05:00</published><updated>2006-11-15T14:42:08.172-05:00</updated><title type='text'>Introduction</title><content type='html'>I know there are a few sites out there dedicated to Remedy ARS (google has an ARS List group).  But I felt there was room for a more informal, non-forum style site that would  present problems, solutions, and examples.&lt;br /&gt;&lt;br /&gt;My intent for this site is to provide ARS users/developers with a location in which they can get updates on current developments with the environment and certain tips and tricks as shared by myself and others.&lt;br /&gt;&lt;br /&gt;Enjoy.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/36900394-116231209472509265?l=remedy-ars.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://remedy-ars.blogspot.com/feeds/116231209472509265/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=36900394&amp;postID=116231209472509265' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116231209472509265'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/36900394/posts/default/116231209472509265'/><link rel='alternate' type='text/html' href='http://remedy-ars.blogspot.com/2006/10/introduction.html' title='Introduction'/><author><name>Steve</name><uri>http://www.blogger.com/profile/11659696729706771552</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://photos1.blogger.com/img/187/3099/640/WPAPM.2.jpg'/></author><thr:total>0</thr:total></entry></feed>
