Uploaded image for project: 'MediaPortal 1'
  1. MediaPortal 1
  2. MP1-3012

gentle.config connect string not updated accordingly by configuration.exe.

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 1.3.0
    • 1.1.0 RC 3
    • TvPlugin
    • None
    • Operating System: Windows 7
      Platform: Intel

    Description

      I borrowed a MP singleseat install for troubleshooting purposes.
      This PC is called PC1.

      At home configured the servername in MP config to point to my home server called "server".

      I then stopped tvservice on PC1.

      Once I was done with the PC1, I returned the PC to the user.

      I configured servername back to "PC1" again.

      When running MP, it would stop at "loading plugings".
      Disabling tvplugin made it load properly.

      The culprit seems to be that gentle.config isn't properly updated with the correct connect string.


      It was:
      <DefaultProvider name="SQLServer" connectionString="Password=****;Persist Security Info=True;User ID=sa;Initial Catalog=tvlibrary;Data Source=server\SQLEXPRESS;Connection Timeout=300;" />

      It should have been:

      <DefaultProvider name="SQLServer" connectionString="Password=****;Persist Security Info=True;User ID=sa;Initial Catalog=tvlibrary;Data Source=PC1\SQLEXPRESS;Connection Timeout=300;" />

      Pay attention to the source key ... Source=server VS Source=PC1

      I had to manually edit this key, nothing did it for me automatically.

      On a sidenote, if servername in mp config is empty, the current local PC name would be saved to mp.xml when running MP.

      configuration.exe and tvplugin.dll should update gentle.config file.

      I seem to remember arion_p did some changes to gentle.net allowing it to see these changes without having to restart the app.

      Attachments

        Activity

          People

            HomeY HomeY
            gibman Elo Rasmussen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: