<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic MSSQL Start problem in BackOffice Products</title>
    <link>https://community.hpe.com/t5/backoffice-products/mssql-start-problem/m-p/4339162#M2773</link>
    <description>I have an accounting package that uses the MSSQLServer engine. The problem is my admin account data got corrupted and had to be restored makiing me a new user on the Server. This has forced MSSQLserver to fail to start saying login error. The service MSSQLServer won't start because the account GUI is different.&lt;BR /&gt;How can I go around this without losing data?</description>
    <pubDate>Fri, 16 Jan 2009 11:39:15 GMT</pubDate>
    <dc:creator>SQLFelix</dc:creator>
    <dc:date>2009-01-16T11:39:15Z</dc:date>
    <item>
      <title>MSSQL Start problem</title>
      <link>https://community.hpe.com/t5/backoffice-products/mssql-start-problem/m-p/4339162#M2773</link>
      <description>I have an accounting package that uses the MSSQLServer engine. The problem is my admin account data got corrupted and had to be restored makiing me a new user on the Server. This has forced MSSQLserver to fail to start saying login error. The service MSSQLServer won't start because the account GUI is different.&lt;BR /&gt;How can I go around this without losing data?</description>
      <pubDate>Fri, 16 Jan 2009 11:39:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/backoffice-products/mssql-start-problem/m-p/4339162#M2773</guid>
      <dc:creator>SQLFelix</dc:creator>
      <dc:date>2009-01-16T11:39:15Z</dc:date>
    </item>
  </channel>
</rss>

