11:53:26 AM view_server(4576): Error: view_server.exe(4576): Error: Unable to construct version. 11:53:26 AM view_server(4576): Error: view_server.exe(4576): Error: Unable to construct cleartext for object "0x3456" in VOB "ambw3r1a:E:\cc_s7p\vobs\infra\S7P_INFRA.vbs": error detected by ClearCase subsystem
In the view server log the following entries can be found: Unable to check out "M:\atw11af9_view\f_rlmc\dummy\cm_tool.txt". Correct the condition, then uncheckout and re-checkout the element.Īttempts to read or checkout file elements in a VOB fail with certain views.ĭuring a checkout operation the following error is reported:Įrror checking out 'M\atw11af9_view\f_rimc\dummy\cm_tool.txt'.Ĭhecked out version, but could not copy data to "M:\atw11af9_view\f_rimc\dummy\cm_tool.txt" in view: unknown error in VOB.Ĭorrect the condition, then uncheckout and re-checkout the element. Many thanks to collegue Ananda Subramanian, with whom I worked together on this problem in my dev-box.Checked out version, but could not copy data to "M:\vob\dir\file.doc" in view: permission denied. This is not a solution for the cause, but might help some getting on track again. I did try a full compile, restart services, undo changes and syncs, with no luck. If there is no user session, it uses some other credentials/logic to startup and caches the XML file so later access is not needed. My deduction is that the Dynamics IIS(express)/SSRS services uses the logged in credentials if available to access this path and failes. you can access the file directly using the full path. I did have read-access to the file, but not to a folder in that path (C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services was access denied). In 8.1 dev this is a non-admin-useraccount. What I saw, was that the user in the error was my RDP account. What I saw when the "Something went wrong" report presented itself, you would want to check the eventlog (Application and services logs \ Microsoft \ Dynamics \ AX-SSRSReportViewer). In my case, reports were available again.
Then logon to the environment and do your thing. After a restart, do _not_ create an RDP session, but go to the URL on your own computer and open a single (standard) report. A rather simpel thing you may want to try, is restart the DEV-environment. Maybe somebody is searching like me on this error, so I would like to contribute what I found out. I had the same problem yesterday and today.
0 kommentar(er)
