I was trying to track down an issue of why a workflow will kick off one workflow, but not a different one. So, I loaded up my K2 Server Console so that I could see what was happening, and I was getting this error repeatedly, as long as I would let it go.
Warning 7000 Object reference not set to an instance of an object.
We have a load balanced server set, and the second server works fine, just the first is doing this. As for the rest of the server console, it all seemed load correctly.
Info 7020 Running Microsoft .NET Framework v2.0.50727
Info 7021 Running K2.net Server 2003 SP4 (v3.6262.1.0)
Info 4403 K2.net Server started under [user account]
Info 7022 Starting K2.net Server Performance Monitoring
Debug 7100 SQL Initialized [server]
Debug 7101 Socket Initialized
Debug 7102 Worker initialized
Debug 7103 Evaluating License Key
Info 7104 K2.net Licensed for 1 CPU(s)
Debug 7106 ThreadPool initialized
Debug 7107 User Manager ADUM.K2UserManager initialized
Warning 7000 Object reference not set to an instance of an object.
Warning 7000 Object reference not set to an instance of an object.
Warning 7000 Object reference not set to an instance of an object.
Warning 7000 Object reference not set to an instance of an object.
Warning 7000 Object reference not set to an instance of an object.
Warning 7000 Object reference not set to an instance of an object.
Warning 7000 Object reference not set to an instance of an object.
Info 7120 K2.net Server was successfully started
Warning 7000 Object reference not set to an instance of an object. (this is where it starts to repeat infintiely)
Has anyone run into this before? Any help is much appreciated.
-Doug
