{"id":4226,"date":"2013-05-21T12:44:10","date_gmt":"2013-05-21T16:44:10","guid":{"rendered":"https:\/\/pitss.org\/us\/2013\/05\/21\/pitss-con-error-cannot-write-pll\/"},"modified":"2017-05-15T14:00:42","modified_gmt":"2017-05-15T18:00:42","slug":"pitss-con-error-cannot-write-pll","status":"publish","type":"post","link":"https:\/\/pitss.org\/us\/2013\/05\/21\/pitss-con-error-cannot-write-pll\/","title":{"rendered":"PITSS.CON Error \u2013 \u2018Cannot Write PLL\u2019 When Updating Libraries to File System"},"content":{"rendered":"<p>You are making updates to libraries (PLLs) inside the PITSS.CON database repository. When you go to update the library in Module Handling to save the changes back to the file system, the library inside the C:\\pitsscon\\users\\pitss#\\olb directory should be updated where the original copy of the library is moved to the C:\\pitsscon\\users\\pitss#\\old directory. However, there is a known issue where the following error may appear instead when trying to update a PLL back to the file system:<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2013\/05\/image3.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" src=\"https:\/\/pitss.org\/files\/2013\/05\/image_thumb3.png\" alt=\"image\" width=\"582\" height=\"399\" border=\"0\" \/><\/a><\/p>\n<p>At the bottom of the Module Handling window, you may see the error \u201cUpdating of modules completed with errors.\u201d<\/p>\n<p>NOTE: In PITSS.CON 12.1.3, you may see instead a glitch where the update says it completes, but the library is not actually updated:<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2013\/05\/image4.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" src=\"https:\/\/pitss.org\/files\/2013\/05\/image_thumb4.png\" alt=\"image\" width=\"586\" height=\"390\" border=\"0\" \/><\/a><\/p>\n<p>In this case, the \u201cFmb Old Path\u201d in the INIT_PARAMETER table for the PITSS.CON user is set incorrectly. It should be set to the user\u2019s old directory. The screenshot below shows it set incorrectly:<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2013\/05\/image5.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" src=\"https:\/\/pitss.org\/files\/2013\/05\/image_thumb5.png\" alt=\"image\" width=\"595\" height=\"393\" border=\"0\" \/><\/a><\/p>\n<p>To change the path, double-click in the text box next to Path Name. A dialog window will appear. Make sure you are in your PITSS.CON user folder. Next, select the \u201cold\u201d directory and click \u201cOpen\u201d.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2013\/05\/SNAGHTMLd0d57b.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" src=\"https:\/\/pitss.org\/files\/2013\/05\/SNAGHTMLd0d57b_thumb.png\" alt=\"SNAGHTMLd0d57b\" width=\"425\" height=\"274\" border=\"0\" \/><\/a><\/p>\n<p>The path name will now be the correct directory. Click on another path location to save the changes.<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2013\/05\/image6.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" src=\"https:\/\/pitss.org\/files\/2013\/05\/image_thumb6.png\" alt=\"image\" width=\"602\" height=\"395\" border=\"0\" \/><\/a><\/p>\n<p>Return to Module Handling. You should be able to successfully update the libraries back to the file system:<\/p>\n<p><a class=\"thickbox\" href=\"https:\/\/pitss.org\/files\/2013\/05\/image7.png\"><img loading=\"lazy\" decoding=\"async\" style=\"padding-left: 0px;padding-right: 0px;padding-top: 0px;border: 0px\" src=\"https:\/\/pitss.org\/files\/2013\/05\/image_thumb7.png\" alt=\"image\" width=\"608\" height=\"402\" border=\"0\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>You are making updates to libraries (PLLs) inside the PITSS.CON database repository. When you go to update the library in Module Handling to save the changes back to the file system, the library inside the C:\\pitsscon\\users\\pitss#\\olb directory should be updated where the original copy of the library is moved to the C:\\pitsscon\\users\\pitss#\\old directory. However, there [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[6,14],"tags":[25,12,7],"class_list":["post-4226","post","type-post","status-publish","format-standard","hentry","category-pitss-con","category-resolve-issues","tag-customer-support-request","tag-error","tag-pitss-con"],"_links":{"self":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/4226","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/comments?post=4226"}],"version-history":[{"count":3,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/4226\/revisions"}],"predecessor-version":[{"id":8501,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/4226\/revisions\/8501"}],"wp:attachment":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/media?parent=4226"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/categories?post=4226"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/tags?post=4226"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}