Can you telnet to port 3389 from the WI server? When you changed the port did you stop the XML service, unregister it with *ctxxmlss /u*. and re-register it with ctxsmlss /r3389 ? After this verify it through the CMC. On 1/26/06, Lich, Brian M <blich@xxxxxxxxx> wrote: > > Sorry. I should have clarified. > > > > The IMA service is starting correctly. When I installed the rollup > hotfix, I started see the below mentioned errors in the event log. One > problem was that the patch changed the XML publishing port back to share > with IIS. I changed it back to the port that I'm using (TCP 3389) but the > problem still persisted. > > > > When a user tried to log into Citrix, they were given the error message of > "Resource Unavailable" and that error (the error below) was logged in the > WI's application event log. > > > > Thanks… > > Brian > > > ------------------------------ > > *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Jeff Pitsch > *Sent:* Thursday, January 26, 2006 2:01 PM > *To:* thin@xxxxxxxxxxxxx > *Subject:* [THIN] Re: IMA error > > > > Maybe I'm not understanding the problem, is the IMA service starting > correctly or not? Or is this an error that you are getting from WI? > > > > Jeff > > > > On 1/26/06, *Lich, Brian M* <blich@xxxxxxxxx> wrote: > > The message was pretty consistent: > > > > An error of type "IMA" with an Error ID of "0x80000001" was reported by > the XML Service at address " http://server:3988";. [Log ID: 5d3e3396] > > > > These event logs collected on the WI server and repeatedly showed an error > for each of the other farm servers (in the WI event log). > > > > Thanks in advance… > > Brian > > > ------------------------------ > > *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On > Behalf Of *thinlist@xxxxxxxxx > *Sent:* Thursday, January 26, 2006 12:50 PM > > > *To:* thin@xxxxxxxxxxxxx > *Subject:* [THIN] Re: IMA error > > > > Where are all the messages in the event log? Is this message coming from > the WI server? > > On 1/26/06, *Lich, Brian M* < blich@xxxxxxxxx> wrote: > > I am running a SQL 2000 datastore and the database server is accessible. > I have 7 servers in my farm and 5 out of the 7 were having problems. I just > un-installed the rollup package and everything is working fine again. > > > > Are there any best practices to follow when applying a Citrix hotfix? Is > there something that should be done to the datastore ( e.g. compacting or > such) besides backing it up before applying a hotfix? > > > > Thanks in advance… > > Brian > > > ------------------------------ > > *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Jeff Pitsch > *Sent:* Thursday, January 26, 2006 10:48 AM > *To:* thin@xxxxxxxxxxxxx > *Subject:* [THIN] Re: IMA error > > > > What datastore is it? If you run through the DSN config can you connect? > How many servers do you have and are any of those experiencing the issue? > Is the datastore server up and running? > > > > Jeff > > > > On 1/26/06, *Lich, Brian M* < blich@xxxxxxxxx> wrote: > > Hi Jeff, > > > > I just recreated the LHC and am still seeing the event logs. Do I check > the connectivity to the datastore through dsmaint? > > > > Thanks… > > Brian > > > ------------------------------ > > *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Jeff Pitsch > *Sent:* Thursday, January 26, 2006 10:23 AM > *To:* thin@xxxxxxxxxxxxx > *Subject:* [THIN] Re: IMA error > > > > You've recreated the LHC? You've check connectivity to the datastore? > > > > Jeff > > > > On 1/26/06, *Lich, Brian M* < blich@xxxxxxxxx> wrote: > > Hello: > > > > This morning my Citrix farm started giving the following error message: > > > > An error of type "IMA" with an Error ID of "0x80000001" was reported by > the XML Service at address " http://server:3988";. [Log ID: 5d3e3396] > > > > I am running PS 4.0 with Server 2003 w/SP1 and the new hotfix roll-up > pack. I have tried to unregister the XML server and re-register but the > problem persists. The XML Service port is TCP 3988. > > > > Is there anything else that I can try? > > > > Thanks in advance… > > Brian Lich > > > > > > > > > > > > > >