How can I undo a mistaken click on the False Error link on a database errors report?
On page


<http://www.sdms.si:92/wikitree/ShowErrors.htm>


Select all three checkboxes **Show temporarily hidden errors, Show ignored errors** and**Hide active errors** and enter your wikitree ID or the one you mistakenly selected. You will see all false errors and temporarily hidden ones with undo links. Click undo link and that is it.
hi sheeeng.  thank you for reporting this to us.  we looked into that file and verified that there is a false detection indeed.  we have fixed this already and the fix should go out soon on the next database releases.

 

thank you again for you report! 

 

 

f-secure labs Find and push the "reset button" A few things to try.


1. Use [Variable Tables](http://odetocode.com/Articles/365.aspx) instead -> maybe the import wizard prefers that?
2. Name your return fields.


Try using the following stored proc (untested .. just thinking out loud...)



```
CREATE PROCEDURE dbo.Foo
AS

    SET NOCOUNT ON

    DECLARE @ResultTable TABLE (SomeId INTEGER)

    INSERT INTO @ResultTable
    SELECT DISTINCT Id AS Identity -- Or u can rename this field to anything...
    FROM SomeExistingTableWhichHasAnIdentityField

GO

```

Try that and see if the wizard refreshes, now.


-- 


 Attempt #2 :)


Ok .. when the EF designer/wizard/whatever fails to figure out EXACTLY what my stored proc is suppose to be returning, I usually do the following :-


1. Make sure the stored procedure doesn't exist at all in the EF designer/context, etc. (You have a clean starting point)
2. Open up your stored procedure and `/* /*` comment out *EVERYTHING* after the procedure definition.


eg..



```
ALTER PROCEDURE dbo.Foo
(
    Bar1 INT,
    Bar2 TINYINT,
    ... // whatever u have as your optional input arguments //
)
AS
    SET NOCOUNT ON

    /* 
    .... every thing in here is commented out 
    */
GO

```

Now ...
 3. Add a forced fake return in the stored proc, which (more or less) just *defines* the output structure/fields.


eg..



```
ALTER PROCEDURE dbo.Foo
(
    Bar1 INT,
    Bar2 TINYINT,
    ... // whatever u have as your optional input arguments //
)
AS
    SET NOCOUNT ON

    SELECT 1 AS Id, 1 AS UserId, 1 AS SomeOtherId, 
        CAST('AAA' AS NVARCHAR(350)) AS Name,
        -- etc etc etc..
    /* 
    .... every thing in here is commented out 
    */
GO

```

[and then](http://www.youtube.com/watch?v=K7luMp6lb9M) ...


4. Add this stored proc to your EF designer/wizard/etc... Now the correct fields should be 'determined' by the designer. AWESOME. Yes .. the values are all hardcoded .. but that's ok (so far).
5. Once your happy that EF is now updated right, go back to your stored proc, and remove all hardcoded SELECT (which we did in the above step). Now we remove the comments which we commented out the entire real code. So you should have your original stored proc, back.


... and now EF is updated and doesn't know we've changed the plumbing of your stored proc.


win :)


does this work for ya? Have you tried restarting your browser? > You might have missed a bracket somewhere... Only such a mistake causes so many insignificant errors.
> 
> 


And to find it, [format your code](http://www.gidnetwork.com/b-38.html) properly. It's your first debugging tool. A trigger is not what you want.


What you need is a scheduled job.


Take a look at the official documentation on the subject:


[Scheduling Jobs with Oracle Scheduler](http://docs.oracle.com/cd/B28359_01/server.111/b28310/scheduse.htm#i1033533)


Feel free to ask more questions if you find any trouble when creating your scheduled job. The best way to  

do it is to rename the file then force a replication from a known good server.


If it is not too  

corrupted you can do an updall -r and it will rebuild the indexes.


Try running  

nfixup.exe against it. If that doesn’t work, try ncompact -c against it.


Note: ncompact  

exists in all workstation installs. nfixup is not part of the client — you can  

copy it off a server that runs at a similar NBotes version.


Make sure to use  

the -c option with compact (ncompact -c whatever\your\file.nsf)


In case it didn’t assist you, then you may use professional recovery software <http://www.nsf.openfiletool.com/> NSF Open File Tool The clue is `Access denied for user 'homestead'@'localhost'`


Do you have a user called `homestead`? Have you attempted to grant them access to the database?


If you're unsure of the answers to either of those questions, I think you should re-read the documentation. Errors and warnings usually appear in `....\logs\php_error.log` or `....\logs\apache_error.log` depending on your php.ini settings.


Also useful errors are often directed to the browser, but as they are not valid html they are not displayed.


So `"tail -f`" your log files and when you get a blank screen use IEs "view" -> "source" menu options to view the raw output. Here is a link to assist you.


<https://technet.microsoft.com/en-us/library/ms178078(v=sql.105).aspx>


If you had done a web search with the question you entered here, you would have found multiple sites that give you the instructions