When I try to run any update query in Access 2007, I get the message
that action blocked because an available ....
What can I do about this?
Have a look at Update data by using a query and go to
Stop Disabled Mode from blocking a query
By default, Access disables all action
queries (update, append, delete, or
make table queries) unless your
database is in a trusted location or
the database is signed and trusted. If
you have not taken either of these
actions, you can still enable the
query for the current database session
by clicking Enable Content on the
Message Bar.
If you try to run an action query and
it seems like nothing occurs, check
the Access status bar for the
following message:
This action or event has been blocked by Disabled Mode.
Also Stop disabled mode from blocking a query
Related
I have created a View in BigQuery and want to set it to update. When trying to save a query in a Schedule Query, an error occurs: Scheduled Query Error
This error is about permissions. You need these permissions to create a query scheduler with BigQuery:
bigquery.transfers.update or (bigquery.jobs.create and
bigquery.transfers.get )
bigquery.jobs.create
bigquery.datasets.update
Another option is adding this role roles/bigquery.admin , including all the permissions you need to schedule or modify a query.
You can read more information about permissions.
When I run a query, unless I manually specify the data location to run the query, BQ defaults to the US multi-region and uses resources in the US.
But then, The BQ Data Transfer Service throws an error since I are now trying to export the data from a query that was executed in US to a table that sits in EU.
So, to fix that, before you schedule the query, I have to go under the query detailed settings, and change the Data Location to EU
Then save these settings, and finish scheduling the query.
Before that, make sure you have enable the Billing
enter image description here
And then maybe because of BigQuery Data Transfer Service (trusted through the pop-up windows……)
bother me a lot……
If the pop-up window does not appear, you should check the address bar to make sure the window is not blocked, if it's not the cause,you can try to change the location of data(related to where you store your data),and submit.
enter image description here
I had the same problem and it turned out to be the pop-up blocker on my Firefox browser. The pop-up blocker on Chrome also stopped the scheduled query working but Chrome was a bit more visible that pop-ups were blocked.
On Firefox, click on the circled icon in the address bar to see blocked pop-ups
Change the pop-up permission to 'Allow'.
I had exactly this generic error message 'Scheduled query error', and it was driving me mad. I checked all permissions and locations etc.
I turns out that the 'Time Travel Window' was set to less than 48 hours for the dataset I was trying to write into. Which apparently BigQuery doesn't like.
To fix this I executed this query
ALTER SCHEMA `PROJECTNAME.DATASETNAME`
SET OPTIONS(
max_time_travel_hours = 72);
We want to make the modules readonly. After clicking on the parent menus, all the submenus should also be readonly.
Tried fields_view_get() but there are too many forms to write the method for!
So is there any other way to do it. We are disabling the modules forever based on a particular date.
Please help.
The algorithm that you can follow to achieve this will depend on what kind of access do your users have to your server. If they do not have access to the Settings menu, then what you can do is have a cron job run every X minutes that validates their subscription for your modules.
If the cron job finds that the their subscription is invalid and you want to make some menus unclickable or some views read only you can run the following query against the database to find out what views does a particular module create:
select * from ir_model_data where module = 'your_module_name';
The ir_model_data model actually contains all the keys for data your module contains. All the menus, views, groups etc you created using XML files (or not) are there.
Once you get all the records in your cursor you can cr.fetchall() and then loop on the return value. Each record will have a model and an res_id. When you see that you have a menu or a view that interests you you can set its active field to false to completely hide the view or menu.
When you loop on your results and find a field (that is a record that has model='ir.model.fields', you can set the readonly field to True so that this field is readonly. You can do this for every field.
As you can understand this approach is not bullet proof. If your users have access to the settings (ie. admin rights) then you must not use Odoo's cron jobs and rather configure a cron job to be run from your Operating System to invoke an external Python script that will do the process described above.
Also, if you set the views/menus/fields readonly, they might be rendered as readonly on the web browser, but there is nothing stopping an end user for crafting a rpc request and sending inappropriate json data.
If the users have SSH access to your server there is not much you can do.
I have splunk alerts set up. however when an application server is restarted, many log entries are created which trigger these alerts. I would like to either ignore these log entries or ignore the alerts when an application server is restarted.
Short of being able to do that, is there a way to annotate the splunk timeline? that way I could annotate the timeline and when people get alerted they can open the report and see that a server reboot occurred. Other tools with timelines allow this sort of annotation.
The best way to implement 'safe work times' is by using a lookup file.
use the date_day date_hour type of fields to set the safe time, and then use the servername as the lookup field to get the data in, then use a where clause to filter out safe times.
lookup file
host safe_begin safe_end
myHost 1900 2200
Query:
.... | where date_hour!>=safe_begin AND date_hour!<=safe_end
after that, set your alert accordingly.
I'm writing a WLST script to deploy some WAR's and an EAR. However, intermittently, the script will time out because it can't seem to get an edit lock (this script is part of a chain of many other scripts). I was wondering, is there a way to override or stop any current locks on the server? This is only a temporary solution, but in the interest of time, it will do for now.
Thanks.
You could try setting a wait period and timeout:
startEdit([waitTimeInMillis], [timeoutInMillis], [exclusive]).
Are other scripts erroring out, leaving the session locked? You could try adding exception handling around those. Also, if you have 'Automatically acquire lock" enabled in the Admin Console and you use the admin console sometimes it can cause problems if you are running scripts at the same time, even though you are not making "lock-requiring" changes.
Also, are you using the same user for the chained scripts?
Within WLST, you can pass a number as a parameter to gain an exclusive lock. This allows the script to grab a different lock than the regular one that's used whenever an administrator locks from the console. It also prevents two instances of the same script from stepping on each other.
However, this creates complex change merge scenarios that are best avoided (by processes).
Oracle's documentation on configuration locks can be found here.
Alternatively, if you want the script to temporarily relieve any existing locks regardless of the pending changes, you may as well disable change management from the console, minimizing the inconvenience caused.
WLST also contains the cancelEdit command that you could run before you startEdit. Hope one of these options pan out!
To take the configuration change lock from another administrator:
If another administrator already has the configuration lock, the following message appears: Another user already owns the lock. You will need to either wait for the lock to be released, or take the lock.
Locate the Change Center in the upper left corner of the
Administration Console.
Click Take Lock & Edit.
Make your configuration changes.
In the Change Center, click Activate Changes. Not all changes take
effect immediately. Some require a restart (see Use the Change
Center).
As long as you're running WLST as an administrative user, you should be able to jump into an existing edit session with the edit() command - I've done a quick test with two admin users, one in the Admin Console, and one using WLST, and it appears to work fine - I can see the changes in the Admin Console session inside the WLST interpreter.
You could put a very simple exception handler around your calls to startEdit that will log the exception's stack trace, but do nothing else. And then rely on the edit call to pop you into the change session.
Relying on that is going to be tricky though if another script has started an edit session and is expecting to be able to commit that change session itself - you'll be getting exceptions and unreliable behaviour across multiple invocations.
As part of the holiday processing some of the jobs are disabled in sql server using script.
They are not disabled manually.
Now when we see the jobs there is a check mark for enable entity.
And when we right click on the job the instead of enable thing being highlighted disable entity is highlighted.
Now we are getting doubt whether jobs are disabled or not.
How to check it through a query is there any status bit which tells us state of the job.
Whether it is disabled or enabled.
Please suggest/advise.
SELECT name, enabled, *
FROM msdb.dbo.sysjobs
WHERE enabled = 0
The above query will bring all disabled jobs. What you are seeing is certainly strange to me too.
Right-click on the jobs folder and select Refresh to update the status icons and context menu.