<?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 SDE User password expires - causing MXD links to break and me a headache in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/sde-user-password-expires-causing-mxd-links-to/m-p/747227#M42037</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have a small issue. Our SDE service password expired the other day and I had to go in to our SQL database and update it to something new.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Well, since updating the account's password, all of the MXDs related to that project no longer load the layers properly - the layers' connections are all broken.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once i changed the password - and confirmed it worked via ArcCatalog - I opened an MXD to do some work, and low and behold the layers are still broken. I try to repair but I get a message saying that the account has been locked out. I am assuming that the layers in the MXD are trying to connect via SDE with the expired password, thus causing a lockout on the account.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Instead of changing the password for every MXD that causes an account lockout, is there a better way to go about fixing these MXDs without changing the SDE password multiple times?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Andrew&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 May 2011 12:22:14 GMT</pubDate>
    <dc:creator>AndrewBrown1</dc:creator>
    <dc:date>2011-05-10T12:22:14Z</dc:date>
    <item>
      <title>SDE User password expires - causing MXD links to break and me a headache</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-user-password-expires-causing-mxd-links-to/m-p/747227#M42037</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have a small issue. Our SDE service password expired the other day and I had to go in to our SQL database and update it to something new.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Well, since updating the account's password, all of the MXDs related to that project no longer load the layers properly - the layers' connections are all broken.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once i changed the password - and confirmed it worked via ArcCatalog - I opened an MXD to do some work, and low and behold the layers are still broken. I try to repair but I get a message saying that the account has been locked out. I am assuming that the layers in the MXD are trying to connect via SDE with the expired password, thus causing a lockout on the account.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Instead of changing the password for every MXD that causes an account lockout, is there a better way to go about fixing these MXDs without changing the SDE password multiple times?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Andrew&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2011 12:22:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-user-password-expires-causing-mxd-links-to/m-p/747227#M42037</guid>
      <dc:creator>AndrewBrown1</dc:creator>
      <dc:date>2011-05-10T12:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: SDE User password expires - causing MXD links to break and me a headache</title>
      <link>https://community.esri.com/t5/data-management-questions/sde-user-password-expires-causing-mxd-links-to/m-p/747228#M42038</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The SDE user password really shouldn't be present in *any* map documents. As an administrative&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;management account, the SDE user should not own spatial data, and the password for it should be &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;closely held (to limit the possibility of instance corruption).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Best practice calls for data ownership accounts to manage spatial data, and browse accounts&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;for read-only access to data that doesn't need editing (and read-mostly access to data which&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;may [granted through roles]). You'll still have an impact from browse user password expiration,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;but if it really is read-only, there won't be as pressing a reason to enable time-based expiration. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Some sites require users to log in as themselves for browse accounts; you can support this by &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;not storing the browse user password in map documents (uncheck the "save password" tic-box),&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;which allows users to override the username and password at initial connect. OS authentication&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;can also help in this regard.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;A forums search (lower box in upper-right corner) on "mxd password change" brought up several&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;posts that lead to resources for changing broken map documents, but you may need to review &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;current geodatabase implementation before you can make best use of them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- V&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2011 13:17:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sde-user-password-expires-causing-mxd-links-to/m-p/747228#M42038</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2011-05-10T13:17:15Z</dc:date>
    </item>
  </channel>
</rss>

