Hi Bo,

It's only the scheduler? I think you need to check if the assigned user still exist. There was also a bug with assigning users but that was solved in 2.2.1.

Hope this helps,

Richard

Hi Richard,

Thanks for your fast input!

Yes, the CMSImport scheduler is the only one running. I have checked that the user doesn't exist in the members section before importing and I've checked that it still exists in the XML document I'm trying to import.

The running version of CMSImport is 2.1.1, so maybe an upgrade could fix it? I should simply copy over the new CMSImport dll file and then it's upgraded? :-)

The only thing I have "customized" with CMSImport is hooking up on the MemberImport.Imported which fires after the import has run, right?

The event code is used for setting members who are not found in the XML document to deactivated (bool) and the code looks like this:

public CMSImportEvents()
        {
            MemberImport.Imported += new MemberImport.ImportedEventHandler(MemberImport_Imported);
        }


        void MemberImport_Imported(ImportEventArgs e)
        {
            XmlDocument xmlDoc = new XmlDocument();
            xmlDoc.Load("urlToXml");
            XmlNodeList emailAdresses = xmlDoc.GetElementsByTagName("AccessUserEmail");

            List<string> xmlEmails = new List<string>();
            int i = 0;
            while (i < emailAdresses.Count)
            {
                xmlEmails.Add(emailAdresses[i].InnerText);
                i++;
            }

            var umbMembers = uQuery.GetMembersByType("Extranet");

            foreach (var member in umbMembers)
            {
                if (!xmlEmails.Contains(member.LoginName))
                {
                    member.getProperty("deaktiveret").Value = "1";
                    member.Save();
                    Log.Add(LogTypes.Custom, 1329, member.LoginName + " was not found in the XML document and has been deactivated");
                }            
            }

            umbraco.library.RefreshContent();            
        }

Thanks again.

All the best,

Bo

HI Bo,

With the user I mean the user you assigned to trigger the import, not the Member. An upgrade could fix it in that case yes. Just run the installer again and it should be fine. Think that is causing the issue otherwise you would have had the same error when you run the import directly

Hope this helps,

Richard

Hi again Richard,

I checked that the admin user is still there :-) Also, I've run the installer again which upgraded it to the current version. However, when I click on any of the scheduled imports I get an exception saying: "invalid column 'importAsUser'"

I tried to set up a scheduled task to run my custom import trigger, but it still gives me the null pointer error unless I run it manually :-/

Thanks again!

Bo

Hi Bo,

I think that the Admin user has a different Id than it normally has (not 0). That's why we found the bug teh other day. Run the script below to update the database please. Then open the Scheduled import in Umbraco select the user again and save it please.

 ALTER TABLE dbo.CMSImportScheduledTask ADD
     ImportAsUser int NULL

Thanks,

Richard

is working on a reply...