NI Pal Service Manager memory error on pc startup

Hello,
I have two XP-pc's with NI-488.2 (ver. 2.30) and MAX (ver. 4.0.0.3010) installed.
Both pc's give on startup an nipalsm.exe memory error (see attachment).
When starting MAX, (if no error) no installed hardware is shown.
On both pc's also McAfee Virusscan 8.00 is running.
What does nipalsm.exe (internal) that can cause this error ?
With thanks,
       best regards,
             Geert
Message Edited by GeertVN on 11-03-2005 12:55 AM
Attachments:
nipalsm error on pc loading.jpg ‏25 KB
nipalsm.exe info.gif ‏34 KB

Hi,
I have some suggestions for you:
Try the latest driver, version 2.4:
http://digital.ni.com/softlib.nsf/websearch/1DDE5C​48F30C2C658625702000681295?opendocument&node=13206​0_US
---> Don't install the new driver over the other one. First remove the old one.
Are you testing the same GPIB card in both PCs? If yes, does the error occur without any cards plugged-in?
Try a Repair of MAX in Add/Remove programs
Make sure that you install first the driver without the card plugged-in.
Check if no firewall is blocking the nipalsm.exe. Maybe you can check if the error occurs when you have no McAfee software installed. (I don't think that the problem is caused by the MCAfee soft but I haven't tested it yet with the latest version)
Regards.
JV

Similar Messages

  • NIMCInit.dll NI-PAL Service Manager Error

    Hello all,
    I'm getting the attached NI-PAL Service Manager error every time I start my computer.  I've tried solution given in this post: http://forums.ni.com/ni/board/message?board.id=240&message.id=4362 thread with no luck.
    If I uninstall the NI-Motion drivers, or remove my PXI-7350 from the PXI chassis, the error goes away.  After I re-install the NI-Motion drivers and re-start the computer, the problem occurs as soon as the "Found New Hardware" wizard completes, and on every boot thereafter.
    Any pointers to what I should try next would be helpful.
    OS & Driver Versions:
    Windows XP SP2 Version 2002
    NI Measurement & Automation Explorer 4.4
    NI Motion Assistant 2.2
    NI-488.2 2.5
    NI-CAN 2.5.2
    NI-DAQmx 8.7
    NI-FGEN 2.5.1
    NI-Motion 7.6
    NI-VISA 4.2
    Hardware:
    PXI-1042 Chassis
    PXI-8187 Controller
    PXI-7350 (Slot 2)
    PXI-2566 (Slot 3)
    PXI-8464 (Slot 4)
    PXI-6254 (Slot 5)
    PXI-6602 (Slot 7)
    PXI-5402 (Slot 8)
    Attachments:
    NI-PAL Error2.png ‏19 KB

    Hi Mark, 
    Make sure that when you uninstall everything you also
    1.  Uninstall MAX
    2.  Delete the MAX data folder (this doesn't uninstall when you uninstall).
         On Windows XP and Windows 2000:
    Navigate to C:\Documents and Settings\All Users\Application Data\National Instruments\MAX\Data\
    The folder named Application Data is a hidden folder.  You can view hidden folders by selecing Tools » Folder Options..., click the View tab, and selecting Show hidden files and folders.
    Note: Remember that deleting the Data folder in its entirety
    will remove all configuration settings.  The next time MAX is launched,
    you will have to configure all of your hardware again.
    Thanks,

  • 'NI-PAL Service Manager has encountered a problem and needs to close. We are sorry for the inconvenience.'

    Hello,
    Any idea how to fix this problem that casuses this error?
    'NI-PAL Service Manager has encountered a problem and needs to close. We are sorry for the inconvenience.'
    I have been re-loading LabVIEW 8.0.1 Pro Dev Sytem, NI-DAQ (Traditional) and NI-DAQmx, all day.  This probelm seems to be related to the fact that I can, no longer, create executables or open my .lvproj files, yielding the other error:
    '' Problem sending commands to the program"
    Thank you
    Message Edited by FLT CTRL 6 on 06-02-2006 03:41 PM

    NI-PAL service Manager has encountered a problem and needs to close.… tell Microsoft...10Jan08
    Yesterday I started having this error message pop up when I first boot up my computer.  I haven’t even started LabVIEW. 
    Recent changes:
    6Jan08 Replaced motherboard and CPU.
    6Jan08 Formatted hard drive and reinstalled software(Windows XP Home Edition).  Computer working fine.
    8Jan08 Installed LabVIEW 8.0 Student Edition.  LV is working fine and the message does not appear.
    9Jan08 Download and install NiDAQ 8.6.1.  Reboot the system and the above error shows up.  LabVIEW works fine so far.
    Anybody have any ideas on what the problem is?  I have a screen shot of the actual message, but I can't load it on this page.
    Oliver
    [email protected]

  • NI-Motion, 7344, NI-PAL Service Manager Problem

    We have a 7344 motion card installed in a PC.  The error started
    to happen after we had a power failure.  When the PC starts up the
    following message is displayed: "NI-PAL Service Manager encountered a
    problem and needed to close"  The Error signature is: szAppName:
    nipalsm.exe, szAppVer: 2.1.0.49152, sz ModName: NIMCInit.dll,
    szModVer:7.2.1.3003 offset: 0001cfac. 
    More Details:
    We have two 7344 motion cards: 1 and 2 and two computers A and B. 
    Both motion cards were installed in PC A when we had the power
    failure.  We can install card 2 into either PC A or PC B and not
    encounter the error.  We install card 1 into PC A and we have the
    problem.  When card 1 is installed into PC B the problem does not
    occure.
    What should we do?
    Pat Pointer  ([email protected])

    Pat,
    this is really weird behavior. Most likely the issue is caused by a harddrive problem on PC A which might be resolved by following these steps.
    Run CHKDSK /F from the Windows recovery console
    Uninstall NI-Motion and remove the 7344 boards.
    Install NI-Motion 7.4 which is the latest NI-Motion version
    Install the 7344 boards in your PC.
    I hope that helps,
    Jochen Klier
    National Instruments Germany

  • Ni-Pal service Manager hat ein Problem festgestellt und muß beendet werden

    Die Meldung "Ni-Pal service Manager hat ein Problem festgestellt und muß beendet werden" wird jedesmal wenn ich den Computer starte angezeigt. Das nervt. Weiß jemand Abhilfe?

    Hallo!
    Der NI-PAL service manager wird am Anfang immer gestartet und ist dafür verantwortlich, dass die entsprechenden DLLs in den Speicher geladen werden. Wenn bei Ihnen jetzt ein Fehler auftritt dann sollten Sie herausfinden welche DLL den Fehler verursacht. Wenn der Fehler auftritt haben Sie die Möglichkeit diese Informationen aufzurufen. (For more information about this error, please click here), danach öffnet sich ein Fenster in dem Sie den Namen der DLL finden.
    Die DLL sollte dann deinstalliert und nachher nochmals installiert werden, wird die DLL nicht mehr benötigt kann Sie auch uninstalliert bleiben.
    Dieser Fehler wird meistens durch eine fehlerhafte Installation verursacht und kann durch die Reinstallation behoben werden. Nach der Installation Rechner neu starten damit der Speicher neu geladen wird.
    Viel Erfolg und ich hoffe ich liege richtig!
    LG, Günther Prossinger

  • NI-PAL Service Manager Error Message

    Hello Fellow LabVIEW users
    I am getting error message everytime I switch on my computer as shown in the attached image file.
    1) what is the NI-PAL? I could not find any help topics related to it.
    2) Why is this error message shown? Could it be because I changed the PCI port for my GPIB card?
    3) How do I overcome this issue? Is it a major problem?
    Thanks
    mhaque
    Attachments:
    error message.JPG ‏44 KB

    Mhaque,
                     May be the following link help for u..
             http://forums.ni.com/t5/LabVIEW/NI-PAL-service-man​ager-generate-an-error-at-the-startup-of-the/td-p/​...
    Siva
    Sivaraj M.S
    CLD

  • Data Services Management Console Error.

    Hi Experts,
    i have installed SAP Data Services 4.2 , at the time of installation "Data Services Management Console" are works fine , but now when i am tryiing to open it is giving error"web page is not available" , please guide me to troubleshoot the issue.
    Regards
    Ajit

    HI Arun Kumar
    Thanks for your reply.
    I checked the service Property and path to which it is executing it was correct and i didn't find any file call .conf in the Conf folder
    Can you please elaborate me where to check this, this is very much needed for my task.
    Thanks in advance
    Ajit

  • NI-PAL Service Manager problem at startup of PC

    I have been using the same version of LabVIEW (8.6) in the same computer with the same DAQ (PCI-6221) and the same OS (Windows XP Pro SP2) for a couple months but since a couple days ago, at startup I get a message saying that NI-PAL encountered an error and needs to close. When I click on "View more" it says that the problem is in szAppName: nimxs.exe szAppVer: 2.1.0.49152 szMonName: nipalut.dll szModVer: 1.5342.3.0 offset 00001204, and then, when I open an .exe built from a VI file, I get the error -2147220712, saying that such error occurred at DAQmx Create Channel (AI-Voltage-Basic) .vi: 4 and (AO-Voltage-Basic) .vi: 1(two different pop ups) and that there is no description of the error.
    To my knowledge no one have added/modified/deleted any component or module.
    Attachments:
    Error.jpg ‏218 KB
    20130918_110647CROP.jpg ‏287 KB

    Hi EIEN1, 
    This problem is due to a corruption in DAQmx. A DAQmx reinstall should solve the problem. If it persists you should try erasing Max Database: 
    http://digital.ni.com/public.nsf/allkb/2C7480E856987FFF862573AE005AB0D9
    I hope this information is useful, 
    Cheers!
    José Alberto G.
    National Instruments
    ELP Support Engineer
    www.ni.com/soporte

  • NI-PAL Service Manager has encountered a problem and needs to close

    Hello,
    I am getting this error after a few hours of running a Labview 7.1 program installed on an XP machine. A reboot and start up of the program seems to go as expected but after the error will pop up again after a few hours.The program appears to still run normally and you can interact with the interface.
    The following information was listed:
    szAppName:nimxs.exe szAppVersion: 2.1.1.49152 szModName: nismslu.dll
    szModVer: 1.4.0.49152 offset: 00003eb7
    What does this mean and will I have to reinstall Labview or could it be a WinXP problem?
    Thanks,
    Mike Cotharin

    Hi,
    Could you please tell me if you are using MAX (measurement and automation explorer)? This looks like a data base corruption.
    Regards,
    Miguel Fonseca
    Applications Engineer
    National Instruments

  • Memory Error Detected At Startup

    After a couple days of frustration, I think I figured out why my mac becomes hung up at the grey screen with the apple in the center everytime I attempt to boot. As a quick summary, I went to upgrade quicktime and after the install, I was prompted to restart and ever since then, I was not able to get the machine to boot up. I was out of my mind fearing the HD and all of my contents went to the grave.
    What I learned is that my memory, I think, has gone bad. I ran the hardware test and the message in the test results states that an error was detected at start up with the Memory. It says "2048 S0DIMM0/j25LOWER" as part of the error message...so I am geussing that meand the card in the the second slot crapped out on me. And after reading several threads, it seems pretty consistent with many other complaints who have this model and the same problem with the second memory slot.
    Anyways, I also heard my logic board now also be ruined as a result of corrupt memory? Eureka! I haven't gotten that far to know for sure, but I thought I would post this thread to see if what I described has happened to others and what they did to resolve.
    I have never opened up a powerbook before and changed / added memory, so I am walking into unknown territory. I was a PC user for many years prior to my powerbook and, unlike the mac, was pretty comfortable tinkering inside a PC. i am okay with jumping inside, but want to make sure I get some inside tips before an even potentially larger disaster!
    So, my questions are:
    1. Based off of the error message described above, is it the lower slot that is corrupt and do I simply remove the LOWER slot (they are two slots each with 256 mb)
    2. If I do that, will it run too too slowly with only 256MB on the first slot that it's not worth using?
    3. Should I just buy 1gig of memory and remove both 256 mb's from each slot?
    4. Will this incident corrupt my HD??
    5. What/where is the best memory card to buy at the most competitve price?
    Also, WHY WHY WHY did this happen?? My memory card on my PC lasted forever...what is going on here? This memory was included with the powerbook from the manufacturer.

    Hello!HERE is a good place to buy memory. It's unlikely that the MB is damaged and it is possible the ram chip has jarred loose. I'd probably try reseating it and if it still fails to work remove it as they do sometimes go bad. The link above may also have a video on changing the ram if you'll look under the tech tab on the site. 256 MB will be anemic on OSX so you'll likely want to replace the chip if it's indeed bad. Tom

  • Import Manager Out of Memory error

    I am running MDM 5.5.24.06 server on Windows XP Professional. The server has 4.0 GB RAM with 1.5 GB Virtual memory.
    I am trying to load 129 material master records from R/3 4.6 ( XML file size 8 MB), into MDM using Import Manager.
    When I click on import icon (Import Status tab selected), MDM Import Manager rightway returns 'Out of Memory' error.
    Tried to import the file again after rebooting the machine, restarting MDM Server, but still it returned the same error.
    Has anybody tried loading the R/3 material data into MDM? What's the experience? What was the load (# of records)?
    What was MDM IM performance? What's your hardware/software config?
    Appreciate your help.
    Thanks,
    Abhay

    Hi Abhay,
    My workstation has Windows 2000, Pentium 4 CPU 3.2 Ghz, 515,555 KB RAM.  The recommended specifications can be found on service market place of SAP, and we used those to procure our workstations.
    MDM server must be more pwerful than a workstation.  Try running the import manager from the server machine itself.  If it works there but not on your machine, it is memory of your workstation.
    Sometimes, I think this error comes when import map some issues- fields not mapped accurately or remote key mapped wrong etc.
    It is probably judicious to rpove the system memory as first step.
    Good luck!

  • Getting error when trying to create Exchange Connector in System Center Service Manager 2012

    Getting error when trying to create Exchange Connector in System Center Service Manager 2012
    The connection to the server was unsuccessful. Please check the server name and/or credentials entered.
    Additional Information: The server URL is not accessible or the user does not have permission to access it (message: The request failed. The remote server returned an error: (401) Unauthorized.
    Warm Regards, Pramod Kumar Singh Manager-IT

    Someone sorted out this issue by installing API 1.2 and copying the dll files to the service manager server ,service folder and replacing it with API 2.0 dll files.
    Also, your question is related to SCSM, please post at SCSM forum if you have further question.
    Juke Chou
    TechNet Community Support

  • Cannot connect to the Service Manager portal WCF service - Error when opening SM Portal

    Greetings,
    I have tried everything I can think of to resolve this issue and I have tried all suggestions I have found on Technet.
    Basically, I had the SM Portal working on a test VM.  I am ready to use it in production but it is not working.  I deleted my test VM and built a new one.  On it, I have SharePoint 2010 Foundation and the SM Portal installed.  I have
    a valid self-signed cert.  the FQDN is correct (hqsrva24.dds.local) in both SharePoint and also in IIS.  I also made sure under Application Settings on the SM Portal IIS site points to the FQDN of the SCSMWebContentServer.
    So what happens when I go to the SM Portal (https://hqsrva24.dds.local:444/SMPortal) is it prompts me for a logon, which i put in and the site comes up.  But at that point the Silverlight portion is not loaded and I immediately get prompted for a logon.
     I have tried several different logons, all of which have full access to the site in Sharepoint.  Eventually I get the error in red at the bottom of the screen "Cannot connect to the Service Manager portal WCF service"
    If I try to access the Web Content Server service on its own (https://hqsrva24.dds.local/Servicehost/services/DataAccessService.svc), I get a prompt to logon and none of my logons work.  i eventually get
    an unauthorized error. However; If I log into the server which SM Portal is on and go to https://localhost/Servicehost/services/DataAccessService.svc, I get no prompt to login and I get a "Metapublishing for this service is currently disabled."
    I'm out of ideas at this point, barring completely starting over (not just the SM portal but all of the Service Manager Suite).

    Man I've had this problem so many times and its almost always a different solution. Are you sure that either the Domain Users group or NT Authority\Authenticated Users have permissions to the site and service. remember the the two prompts are authenticating
    different things: the Sharepoint site and the application site (silverlight). Make sure users have permission in both SCSM and in Sharepoint. 
    - Slow is smooth and smooth is fast.

  • Service Manager 2012 R2 - Workflow Error - Event ID 4513

    Hi,
    We started to suffer a Workflow error in Service Manager 2012 R2 2 weeks ago. We noticed through the failure of some SLOs not being applied on Work Items. The error is the follow:
    Log Name:      Operations Manager
    Source:        HealthService
    Date:          13/03/2014 12:10:00
    Event ID:      4513
    Task Category: Health Service
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      XXX-XXX-XXX
    Description:
    The callback method DeliverDataToModule failed with exception "'­', hexadecimal value 0x1F, is an invalid character." in the module Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.
    Workflow: WorkItem_SetFirstAssingedTo_RelationhsipAdd_Rule
    Instance: Destino do Fluxo de Trabalho (interno)
    Instance ID: {383E578B-E1C9-2802-0047-815853405778}
    Management Group: CTRPROD
    Full Exception Text:
     System.ArgumentException: '­', hexadecimal value 0x1F, is an invalid character.
       at System.Xml.XmlEncodedRawTextWriter.InvalidXmlChar(Int32 ch, Char* pDst, Boolean entitize)
       at System.Xml.XmlEncodedRawTextWriter.WriteElementTextBlock(Char* pSrc, Char* pSrcEnd)
       at System.Xml.XmlEncodedRawTextWriter.WriteString(String text)
       at System.Xml.XmlWellFormedWriter.WriteValue(String value)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeAndVerifyType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, Boolean verifyKnownType, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithXsiType(XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle objectTypeHandle, Type objectType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle, Type
    declaredType)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at WriteArrayOfanyTypeToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , CollectionDataContract )
       at System.Runtime.Serialization.CollectionDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at WriteResultToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
       at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
       at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.DataContractSerializer.WriteObject(XmlWriter writer, Object graph)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.DataItemSubscription.GenerateItemXml(XmlWriter writer)
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.GenerateItemXmlInternal()
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.GetItemXml()
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.QueryItem(XPathExpression xpathQuery)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenReplaceWindowsWorkflowTaskParameterValue.TokenResolver(String tokenValue)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenResolver.RegexMatchEvaluator(Match m)
       at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat)
       at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenResolver.Resolve(String str)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenReplaceWindowsWorkflowTaskParameterValue.GenerateWindowsWorkflowTaskParameterValue(String elementTemplate)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskParameterValue.Resolve(TokenReplaceWindowsWorkflowTaskParameterValue resolver)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskArrayParameter.Resolve(TokenReplaceWindowsWorkflowTaskParameterValue resolver)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTask.Resolve(DataItemBase[] dataItems)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.ProcessDataItems(DataItemBase[] dataItems)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.OnNewDataItems(DataItemBase[] dataItems, Boolean isLogicalSet, DataItemAcknowledgementCallback acknowledgedCallback, Object acknowledgedState, DataItemProcessingCompleteCallback
    completionCallback, Object completionState)
       at Microsoft.EnterpriseManagement.HealthService.Internal.InputPortCallbacks.InputStreamBatchedAcknowledgedCallbackHandler`1.InputPortCallbackImplementation(DataItemBase[] dataItems, Boolean isBatchLogicalSet, DataItemAcknowledgementCallback
    acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
       at Microsoft.EnterpriseManagement.HealthService.Internal.ModuleContainer`1.Microsoft.EnterpriseManagement.HealthService.Internal.IModuleContainer.DeliverDataToModule(UInt32 inputPortNumber, DataItemBase[] dataItems, Boolean isBatchLogicalSet,
    DataItemAcknowledgementCallback acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
       at Microsoft.EnterpriseManagement.HealthService.Internal.ManagedHostHelper.Microsoft.EnterpriseManagement.HealthService.Internal.IManagedHostHelper.DeliverBatchedDataToModule(UInt32 inputPortNumber, Object moduleInputReference, DataItemBase[]
    dataItems, UInt32 dataItemCount, Boolean isBatchLogicalSet, Object completionReference)
    Event Xml:
    <Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='HealthService'/><EventID Qualifiers='49152'>4513</EventID><Level>2</Level><Task>1</Task><Keywords>0x80000000000000</Keywords><TimeCreated
    SystemTime='2014-03-13T15:10:00.000000000Z'/><EventRecordID>4953905</EventRecordID><Channel>Operations Manager</Channel><Computer>CTR-SCSM-MS01.sp.local</Computer><Security/></System><EventData><Data>CTRPROD</Data><Data>WorkItem_SetFirstAssingedTo_RelationhsipAdd_Rule</Data><Data>Destino
    do Fluxo de Trabalho (interno)</Data><Data>{383E578B-E1C9-2802-0047-815853405778}</Data><Data>DeliverDataToModule</Data><Data>'­', hexadecimal value 0x1F, is an invalid character.</Data><Data>Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction</Data><Data>System.ArgumentException:
    '­', hexadecimal value 0x1F, is an invalid character.
       at System.Xml.XmlEncodedRawTextWriter.InvalidXmlChar(Int32 ch, Char* pDst, Boolean entitize)
       at System.Xml.XmlEncodedRawTextWriter.WriteElementTextBlock(Char* pSrc, Char* pSrcEnd)
       at System.Xml.XmlEncodedRawTextWriter.WriteString(String text)
       at System.Xml.XmlWellFormedWriter.WriteValue(String value)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeAndVerifyType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, Boolean verifyKnownType, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithXsiType(XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle objectTypeHandle, Type objectType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle, Type
    declaredType)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at WriteArrayOfanyTypeToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , CollectionDataContract )
       at System.Runtime.Serialization.CollectionDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
       at WriteResultToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
       at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
       at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
       at System.Runtime.Serialization.DataContractSerializer.WriteObject(XmlWriter writer, Object graph)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.DataItemSubscription.GenerateItemXml(XmlWriter writer)
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.GenerateItemXmlInternal()
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.GetItemXml()
       at Microsoft.EnterpriseManagement.HealthService.DataItemBase.QueryItem(XPathExpression xpathQuery)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenReplaceWindowsWorkflowTaskParameterValue.TokenResolver(String tokenValue)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenResolver.RegexMatchEvaluator(Match m)
       at System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat)
       at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenResolver.Resolve(String str)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.TokenReplaceWindowsWorkflowTaskParameterValue.GenerateWindowsWorkflowTaskParameterValue(String elementTemplate)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskParameterValue.Resolve(TokenReplaceWindowsWorkflowTaskParameterValue resolver)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTaskArrayParameter.Resolve(TokenReplaceWindowsWorkflowTaskParameterValue resolver)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowTask.Resolve(DataItemBase[] dataItems)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.ProcessDataItems(DataItemBase[] dataItems)
       at Microsoft.EnterpriseManagement.SystemCenter.Subscription.WindowsWorkflowWriteAction.OnNewDataItems(DataItemBase[] dataItems, Boolean isLogicalSet, DataItemAcknowledgementCallback acknowledgedCallback, Object acknowledgedState, DataItemProcessingCompleteCallback
    completionCallback, Object completionState)
       at Microsoft.EnterpriseManagement.HealthService.Internal.InputPortCallbacks.InputStreamBatchedAcknowledgedCallbackHandler`1.InputPortCallbackImplementation(DataItemBase[] dataItems, Boolean isBatchLogicalSet, DataItemAcknowledgementCallback
    acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
       at Microsoft.EnterpriseManagement.HealthService.Internal.ModuleContainer`1.Microsoft.EnterpriseManagement.HealthService.Internal.IModuleContainer.DeliverDataToModule(UInt32 inputPortNumber, DataItemBase[] dataItems, Boolean isBatchLogicalSet,
    DataItemAcknowledgementCallback acknowledgementCallback, DataItemProcessingCompleteCallback completionCallback)
       at Microsoft.EnterpriseManagement.HealthService.Internal.ManagedHostHelper.Microsoft.EnterpriseManagement.HealthService.Internal.IManagedHostHelper.DeliverBatchedDataToModule(UInt32 inputPortNumber, Object moduleInputReference, DataItemBase[]
    dataItems, UInt32 dataItemCount, Boolean isBatchLogicalSet, Object completionReference)</Data></EventData></Event>
    Has anybody faced the same problem?
    Thanks
    Thiago

    Hi Thomas,
    Thanks for your response. I understood your comments but, the system was running fine for about 3 months. No changes have been applied during this time and suddenly this error pops out.
    I opened a case with MS Support, but they applied a WA which does not resolve our problem, because the error appears after a few days later after the WA procedure.
    The WA is just a watermark reset using this SQL query:
    DECLARE @MaxTransactionId Int, @RuleID uniqueidentifier
    SET @RuleID = '' -- <-- SET THIS TO YOUR RULE ID!!!
    SET @MaxTransactionId = (SELECT MAX(EntityTransactionLogId) FROM EntityTransactionLog) 
    UPDATE CmdbInstanceSubscriptionState
    SET State = @MaxTransactionId
    WHERE RuleId = @RuleID
    The problem with this WA is that all Work Items affected by the problem - workflows not being applied - do not get the information we need to identify all the SLA's. The system just "forget" them and moves on.
    Cheers,
    Thiago

  • System Center Service Manager 2012 SP1 upgrade install error

    I am trying to upgrade my SCSM 2012 front end app server to SP1 and am getting these failures in the log when it fails with the error "Service Manager is not in a valid state"
    09:07:58:Could not find WCS portal web site in IIS metabase!
    09:08:02:***ERROR*** Microsoft System Center 2012 - Service Manager: Microsoft System Center 2012 - Service Manager is not in a valid state. 
    09:08:02:Application Ended
    09:08:02:-222
    Can someone tell me how to get this rectified? The WCS portal is installed and running and has been for months. The DW is upgraded but I cannot get the SharePoint self service portal or the App server to upgrade due to this error.

    Hello
    One question you have the website installed on the same
    server on which you have the Server Management
    Server, so if you can
    not make your upgrade to
    SP1, this changed because
    a prerequisite of System Center Service
    Manager 2012 SP1 in which you can not have
    the server Mangement and
    website on the same server they have to be
    separate.

Maybe you are looking for