Here's a beauty of a pile of poo I stepped in. I was trying to update my Jet Services server to the latest version of Jet Reports tools so I could access the Dashboard Builder.
In doing so I uncheck the boxes for Jet Server because, duh!, they were already installed.
WRONG MOVE!
That just uninstalled the Jet Server components. So bye bye Jet server.
Took a support case for me to realize how big a flip-up this was. I was trying to access Jet after this goof and, since the Jet Service windows service was no longer present I was focusing on trying to start the Jet Data Manager Server service.
As Jet Support so ably pointed out that service is only used for a "developer" scenario, which I believe is where multiple developers are using Jet at the same time. Not my cup of tea but, hey!, open a support case.
Meantime I'd try to start the Jet Data Manager Server and received the following:
"The service started and then stopped again. The reason for this can be that the user <x> has an incorrect repository connection."
Well, truth be told, the reason for this is I'm an idiot! I had no business trying to start that service. It should have been disabled and remained that way.
In reality what I needed to do was re-install the Jet Server components and reconfigure things. After doing that Jet was back up-and-running and I was back in business.
Please be careful and try not to follow my footsteps!
No comments:
Post a Comment