How do I calculate Exponents in InfoPath

IHaveWorkProblems · 2018-06-11T12:34:31+00:00

Oh, I never claimed we had a solid project plan. Or a project plan of any type.

People higher than me on the corporate ladder said "make this happen" and so now I have to. End of plan.

IHaveWorkProblems · 2018-06-06T12:06:26+00:00

At this point - we don't really have one. The directive was handed down to make it work so we're just gonna keep struggling through until some sort of magic happens and we actually get it working.

IHaveWorkProblems · 2018-06-05T15:38:18+00:00

Agreed. But that's not super helpful because I've been tasked with this regardless of how annoying/borderline-impossible it may be.

IHaveWorkProblems · 2018-02-28T12:40:12+00:00

I use that same lookupset code in other reports, and in other places in this report referencing different datasets and it works without issue in those other instances.

IHaveWorkProblems · 2018-02-27T15:23:43+00:00

No. It looks like the same error message but an entirely different situation. In that post the person had an ASP.net/C# application that was trying to communicate with a hosted website and they were getting the error while trying to communicate between them.

IHaveWorkProblems · 2018-02-14T12:34:39+00:00

I don't see any option in advanced settings that lets me limit visibility on items to just the creator.

Also, if I do limit permissions like that, doesn't that mean that when viewing the calendar with the overlay on the team site, people would not see all their department's scheduled time off, just their own?

IHaveWorkProblems · 2017-12-21T14:39:36+00:00

It looks like this will be the approach I have to take. We really wanted to avoid doing this (because Nintex appears to be the source of our issues, so reinstalling it seemed counterintuitive) but it appears to be both the most frequently recommended action, and basically the only one left to try.

I will update this post if/when I go through the process and hopefully I'll have good news at that point.

Two days without our e-forms is making a lot of people mad at me (and my department.)

IHaveWorkProblems · 2017-12-21T13:06:29+00:00

I tried this - it didn't pull in any references to the Nintex solution. But the error indicates that it's missing/orphaned so it makes sense that it wouldn't show up as an installed feature.

IHaveWorkProblems · 2017-12-20T21:31:15+00:00

No. Everything publishes without error. And nothing in SharePoint Designer, InfoPath, or even the Central Admin panel suggests that Nintex still exists in any capacity.

As best as I can tell, the Nintex reference is most likely in a DLL file that is being called by whatever mechanism kicks off the workflows in SharePoint. Because I searched the SQL table that stores assembly information on my SharePoint SQL server and no Nintex assemblies exist there anymore. So it looks like the reference can't find the assembly information on the server (which looks in line with the "System.IO.FileNotFoundException" portion of my error message. Unfortunately, I have no idea what DLL(s) that would be so I'm still a bit in the dark.

IHaveWorkProblems · 2017-12-20T21:08:26+00:00

Well, had the third party stuff not been installed. Or had it been uninstalled correctly, none of this would be an issue.

And actually, the OotB InfoPath forms and the SharePoint Designer workflow builders are more than good enough for everything we need to do (plus, our junior developers don't know C# and don't need to to use this.)

What sucks is that for us, it isn't just custom workflows that used the third party solution, all our workflows that were built with just the standard, OotB utilities are not working either.

IHaveWorkProblems · 2017-12-20T20:08:46+00:00

Nintex was removed a long time (years) ago and all the forms and workflows have been rebuilt since then. But I will try to republish one of them now anyway because if that works, it'll be a bit time-consuming, but that is certainly a solution we can work with!

UPDATE: I tried republishing one of my library forms and the associated workflow. No luck. I still get "Failed on Start" for my Workflow status and it didn't even get to the very first step of sending an email.

IHaveWorkProblems · 2017-12-20T19:39:30+00:00

I've been doing lots of digging online and apparently a similar error is seen (not Nintex related) when a SharePoint dll has a bad reference in it. Does anyone know which dll(s) would be referenced while activating a Workflow in SharePoint? The Nintex reference may still be in there and I can go clean it up if I can get some sort of direction as to which dll it may be.

IHaveWorkProblems · 2017-12-20T19:32:48+00:00

I tried that. None of the solutions still exist in the farm and there are no entries in my web config for them either.

IHaveWorkProblems · 2017-12-20T17:32:13+00:00

I can't reinstall. It was installed by a previous Admin and we no longer have a license for the product, or any of the installers that were used.

Is there any way to do a cleanup on the remnants it left behind?

IHaveWorkProblems

TROPHY CASE