Error encountered while setting a ClearCase dynamic view.
root#clearcase:~ # ct setview cc_dyn_view
ct: Error: Operation "view_ws_is_ws_view" failed: view storage directory or control files unavailable --
additional information may be present in the view server host's view log.
root#kviewsrvr:~ #
View log shows:-
2013-11-20T11:40:21+05:30 view_server(16910): Error: Operation fcntl(F_SETLK), .pid: Input/output error
2013-11-20T11:40:21+05:30 view_server(16910): Warning: Temporary server starting for unusable view at '/net/clearcase/viewstore/root/cc_dyn_view.vws'
Anyone please help to resolve this issue.
It depends on the ClearCase version, and on the view and vob server (Unix, Solaris, windows).
This thread reports a similar error, sugesting a Linux system limitation:
The size of the file table will need to be increased.
Increase the 'nflocks' kernel parameter from 200 to 400.
If it is not that, you need to check:
the server ClearCase logs (not just the view logs),
any permission issue in accessing /net/clearcase/viewstore/root/cc_dyn_view.vws.
Related
We have a Snowflake database that connects to a Shared View from PlayFab (for game events etc.) Stored procedures run daily via scheduled tasks to copy the latest data from the view into our own 'local' Snowflake table. It's been working fine, but today we're getting the following error trying to read from the PlayFab View:
Error: 100183: SQL compilation error: Failure during expansion of view 'PLAYFAB_ARCHIVE_SHARED': SQL compilation error: Object 'REPORT_PRIMARY.PUBLIC.ACCOUNT_MAPPER' does not exist or not authorized.
I can't find any mention of the error number or REPORT_PRIMARY.PUBLIC.ACCOUNT_MAPPER in the documentation. I believe error 100183 relates to a problem in a stored procedure, but I don't think it's my procedure, since I get the same error running a simple query from the PLAYFAB_ARCHIVE_SHARED view manually. I've checked the data from the PlayFab side, and it exists there. I'm not really sure whether the problem is Snowflake or PlayFab, but because of the error code, I suspect Snowflake.
I'm trying to get a direct support answer, but that doesn't seem to be happening for some reason. Anybody experienced this before?
PlayFab had mistakenly removed access to the view. Snowflake support confirmed that they could not find the view REPORT_PRIMARY.PUBLIC.ACCOUNT_MAPPER. After contacting PlayFab support, they re-enabled the shared view and Snowflake access is now working again.
In past I have faced similar error on view, Its because of the access could you run grant access on the stored procedure to your role.
When running the following SQL against a SQL Server 2005 Express database:
CREATE FULLTEXT CATALOG My_FTCatalog AS DEFAULT
the following error occurs:
Execution of a full-text operation failed. 'The revocation process could not continue - the certificate(s) could not be checked.'
The error is occurring on a computer that does not have access to the internet, so the certificate information may be 'stale', but its not clear how the above SQL statement triggers the certificate error, and what certificate is at fault.
The SQL is being run with administrative privileges on the computer and in the database.
Thanks in advance.
This is a partial answer/guess to my question, but I hope if someone else comes to this question, they are able to benefit from the answer.
The workaround is to configure Full Text to not verify signatures. This is accomplished by executing the following SQL Command:
EXEC sp_fulltext_service 'verify_signature', 0;
GO
Based on the above setting of not verifying signatures, I found the following page:
https://msdn.microsoft.com/en-us/library/ms142595%28v=sql.90%29.aspx
This pages indicates that the filters used by the Full Text search need to be signed, which would explain why an error involving certificates could be generated when creating a Full Text database.
This pages provides a map of the components that make up the Full Text search architecture, provides some insight into the executable or *.dll files that may need to signed:
https://technet.microsoft.com/en-us/library/ms142541%28v=sql.90%29.aspx
The error in the question references the "revocation process". On the computer that is producing the error, another application displayed an error in it's certificate properties window that said:
Windows cannot determine the validity of this certificate because it cannot locate a valid certificate revocation list from one or more of the certification authorities in the certification path.
The computer producing the error does not have access to the internet, which prevents the OS/certificate management software from being able to validate the revocation lists.
So the 'guess' about what is happening is that when the Full Text database is created, one step in the database creation process is to validate the signatures of the filters used by the Full Text search. Part of the validation of the signatures includes validating the revocation list, but this cannot be completed because the computer is not on the internet, which results in the production of the error.
I hope this helps someone.
This may or may not help future users, but I was able to fix the
'The revocation process could not continue - the certificate(s) could
not be checked.'
issue by making a change to the STATE registry file. However, the installers I was was trying to run would get this error when trying to install Windows Updates with an offline installer.
Open REGEDIT.exe and change STATE from 1000 to 23c00 in:
HKEY_CURRENT_USER\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERION\WINTRUST\TRUSTPROVIDERS\SOFTWAREPUBLISHING\STATE
You are looking for the WinTrust folder which may or may not be in currentversion.
If this helped you, mark it up!
We are working on a task to resurrect a ClearCase server.
During the restoration process, we are stuck with following error as shown in server log.
vobrpc_server.exe(<pid>): Error: See albd or vob error logs on host <host name>
Here is the background.
We were given 2 servers [Registry & view server]
Registry server was in island and view server was in under a domain, which is now currently unavailable.
We created a new group called "ClearCase" and put both these servers under same LAN and created new users under ClearCase group.
While the license & albd service started successfully, it is still unable to create / restore views.
We were able to see VOB information via ClearCase explorer, but while trying to create a new view & while accessing the folder, we are getting error like "Encountered an improper argument". Google around this error, we ended up in seeing above error in ClearCase server logs.
The actual errors are:
view server log error:
view_server.exe(pid): Warning: Unable to open vob
'<host_name>:E:\ClearCase_Storage_e\vobs\AdmitOneIKE.vbs':
unknown error in VOB.
view_server.exe(7876):
Error: Unexpected error in VOB
"<host_name>:E:\ClearCase_Storage_e\vobs\AdmitOneIKE.vbs"
op vob_ob_get_vob_owner_sid:error detected by ClearCase subsystem
See vobrpc_server_log on host <host_name>...
vobrpc_server.exe(1188):
Error: Problem starting vob_server for vob
<host_name>:E:\ClearCase_Storage_e\vobs\esg.vbs. server
Albd(5364):
Error: Server vob_server.exe (pid=7224) on
"E:\ClearCase_Storage_e\vobs\AdmitOneIKE.vbs"
died on startup; marking it as "down".
vob_server.exe(pid):
Error: No group "clearcase" found.
vob_server.exe(7224):
Error: Unknown style protections.
cccredmgr(6388):
Error: Trouble contacting registry on host "<host_name>":
timed out trying to communicate with ClearCase remote
There seems to be an issue with the owner or the groups associated with the Vob.
I would recommend trying using fix_prot for fixing the vob.
And/or cleartool protectvob to change/reset ownership and group membership.
On Windows 7 x64, SQL Server 2014(x64) Management Tools installation fails with the following error;
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Management Services
Component error code: 1406
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140719_170948\sql_ssms_Cpu64_1.log
Error description: Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel.
I monitored installation with Process Monitor and find that it is trying to write(RegSetValue) HKLM\SOFTWARE\Wow6432Node\(Default) value which results in "Access Denied".
So, when i try to change that key's default value within regedit, it is not allowed too;
Cannot edit : Error writing the value's new contents..
For Wow6432Node key, i grant permissions to following users/groups; Everyone, Current Admin Account, Administrators, System but that did not help to change that default value even with regedit.
I could only think about registry corruption or some windows bug or may be some other program intervention, so, i disabled antivirus app. What might it be and how could i solve it?
After trying several things, finally, i applied the following and it worked. Restart may be required after applying it.
regdacl HKLM\SOFTWARE\Wow6432node /gga:F /ggu:F /ggs:F
Download regdacl here
http://www.heysoft.de/en/software/regtools.php?lang=EN
Can you creat a view in CCRC if stream is locked ?
It seems others can create a view but this one guy is getting an error when trying to create the view:
problems performing ClearCase operation
Problems were encountered while retrieving view synchronization information and data
ClearCase CM server: Error: unable to begin update session: unknown error in view server.
ClearCase CM Server: Error: Additional information may be available in the view log on host "hostname".
ClearCase CM Server: Error: operation "view_ws_begin_load_session" failed: unknown error in view server
Any ideas on how to fix or trouble shoot this?
(CCRC is on Windows XP SP3 laptops)
No the stream isn't locked.
Looking at the views log on the server can tell you more, but typically, you can have error due to access rights (like the primary group incorrectly or not set in the CCRC GUI).
Or there is some kind of server error (the CCRC being the view server for all the web views: the view_server process for that particular view could have an issue)
So check the CCRC server logs for views (see getlog):
cleartool getlog -host CCRC_servername -since yesterday view