SOTI Pulse Logo

When trying to add a package to mobicontrol get an internal server error

J
Jon
YRC Worldwide

I spoke with support and they suggested we change the max text replication size on the sql server due to an error (that existed before this issues started) on the mobi server. When we try to add any package no matter the size we get an internal server error and the package is not added. We've restarted the servers and I've looked at the DS, MS, and DSE logs and don't see any entries at the times I'm uploading the packages. We've tried recreating the packages with different version numbers after this change and still not able to add a package.

I also tried cleaning out c:\windows\temp and got a different error message when trying to add the package.  I restored the temp folder and went back to the internal server error. It looks like the package is completely copying to the temp folder but it's not being added into the web server by mobicontrol. 

Ideas of where to look next? This was all working before we upgraded the second and third servers to the same version as the primary. Our primary was 13.4.4266 and the secondary and tertiary were 13.3. 

Edited 7 years ago
SOTI MobiControl
ANSWERS
JM
Johnathon Marshall
7 years ago

Hey there Jon,

Our server is cloud hosted so it may be different but I had this happen in the past and it was because, for whatever reason, two of the exact same package was uploaded. Once that happened I couldn't make any changes regarding packages, I had to open a ticket and the end solution was to have my database rebuilt to right before I uploaded the package and try again uploading again afterwords.

They still are not sure why the package uploaded twice at the exact same time and it has happened a few times since.

Hope this helps or points you in the right direction to a resolution.

Regards,

Johnathon

RC
Raymond Chan
7 years ago (edited 7 years ago)

Did you say you have an HA system with three deployment servers, and you had one at 13.4.4266 and the other two  at v13.3  running "concurrently" for some time?  Were you instructed by anyone to migrate/run your system that way?   How long did that hybrid HA system last?  Did you change policies/add new packages in that hybrid HA system?

J
Jon
7 years ago

Unfortunately it ran that way for about 3 months before I started working here. The person who updated the servers did not know that you had to do all three manually. Several packages were added while it was in the mixed state unfortunately. It wasn't until a windows update broke SHA-1 on the primary that I realized the servers were out of sync. 

RC
Raymond Chan
7 years ago

I am not sure if v13.4.4266 include something that breaks what you want to do, or whether the way you migrate your HA system cause the problem. In general, ALL running servers on a live HA system should run the same "version PLUS build number" at ALL time. This is what I have been told since day one I started working on v10/v11 HA systems. Your database data may already have included corrupted data that cause other problem(s) that you are not aware of.

As it has been in this hybrid state for 13 months,  it's basically impractical to consider falling back and restoring to a clean database before the upgrade at that time.   I believe your only option is to contact Soti support/professional-service team to analyse your  log files and database, and see if they can clean up any problem(s) found. 

Similar Discussions