[no Bug] lost all TV Server settings and schedules (1 Viewer)

[vvulture]

Carried out upgrade instructions to the letter... lost all TV Server settings and schedules.... not happy. ( yes, i know i should've backup but even the best of us sometime forget ).

 

[mm1352000]

Carried out upgrade instructions to the letter... lost all TV Server settings and schedules.... not happy. ( yes, i know i should've backup but even the best of us sometime forget ).

Have you got install logs? Unless you somehow wiped the TV database that should not have happened.

 

[vvulture]

Logs attached... Just checked again and database is infact the old one, but all contents have been wiped.

Did not wipe anything.. just stopped TVService manually, checked services to make sure and carried out straight upgrade. Got successfull upgrade message.

 

[mm1352000]

@vvulture
There are two install log files in your log collection. First one at 1:21:01 pm, second at 1:21:50 pm.
In the first one we see:

[ DEBUG ] commandline parameters: /S /noClient /DeployMode --DeployMode /UpdateMode

[ INFO] InstallMode is: Dedicated TVServer or SingleSeat.
[ INFO] ==> Old TVServer/Client will be uninstalled now.

This is why you would have lost your schedules and channels.
For this to happen, you would have had to select a server-only install with advanced installation options.
Can you confirm that is what you did?

In the second log file we see:

commandline parameters: /S /noServer /DeployMode --DeployMode /UpdateMode

In the log file I see:

commandline parameters: /S /noServer /DeployMode --DeployMode /UpdateMode

[ INFO] TVServer component is already installed.
[ INFO] --> Means it is a SingleSeat installation.
[ INFO] --> Means TVServer was already updated.
[ INFO] ==> TVServer/Client won't be uninstalled.

So here it looks like you updated the client separately after reinstalling the server.
Can you confirm?

@Sebastiii
Looking at these log files, this is a bit strange:

commandline parameters: /S /noServer /DeployMode --DeployMode /UpdateMode

We can see it doesn't cause any problem...

SecPrepare: DeployMode = 1 | UpdateMode = 1

Is this normal?

 

[Sebastiii]

Looking at these log files, this is a bit strange:

commandline parameters: /S /noServer /DeployMode --DeployMode /UpdateMode

We can see it doesn't cause any problem...

SecPrepare: DeployMode = 1 | UpdateMode = 1

Is this normal?

I don't think it's normal, i remember fix something on this side about reinstall when SQL server is already installed (if i'm not wrong) need to debug that again it seems

Thanks

 

[mm1352000]

@vvulture
It would be really helpful if you could confirm.
If there is such a problem, we want to solve it before the final release... but we need your help.

 

[Sebastiii]

Looking at these log files, this is a bit strange:

commandline parameters: /S /noServer /DeployMode --DeployMode /UpdateMode

We can see it doesn't cause any problem...

SecPrepare: DeployMode = 1 | UpdateMode = 1

Is this normal?

I have look/find the commit about it :
SHA-1: 50282590d384742d135ab5494a85cf6bc931eaa1 10/12/2012 02:46:12

Effectively we have :
Process setup = Process.Start(_fileName, String.Format("/S /DeployMode --DeployMode {0} .....

So i don't remember why i keep '/DeployMode' i'm pretty sure it was needed (when i have do testing regression) but i can't say why now.
Better i need to test again and debug that to see if it's really needed

 

[mm1352000]

So i don't remember why i keep '/DeployMode' i'm pretty sure it was needed (when i have do testing regression) but i can't say why now.

Better i need to test again and debug that to see if it's really needed

Seems like something to do with the change from --abc to /abc.
It is not a serious problem, I was just curious.
As long as it works I think no need to investigate further right now.

 

[mm1352000]

No response => setting thread to no bug.
@vvulture
You can still follow up if you believe there is a genuine bug. Even a simple "oops, it was my mistake" would be appreciated too.

 

[vvulture]

So sorry for not replying guys... been very hectic at work.

During the install process, i made sure i selected the update option... 100% certain.
I did not select the sever only option...

Cheers