Viewing 15 posts - 1 through 15 (of 69 total)
Maybe you have an application which uses the sa password. Create a trace with profiler to trap this kind of events (Security Audit - Audit Login Failed)
Hope this helps.
November 29, 2004 at 1:17 pm
Have you checked all the available processors in the processors configuration item?
July 6, 2004 at 2:38 pm
My machine is the only one running AS Manager on the network
June 29, 2004 at 1:51 pm
I´m using the same 'elegant' method, but i think that our friends from Microsoft should be developed some utility, exe, command or whatever that let us do that in a...
June 29, 2004 at 7:43 am
You could try to find which is the sp that stores the instruction, and then take a look to the permissions. Script all the sps through EM, and find the...
June 9, 2004 at 1:36 pm
I can do it running a batch with this string:
isql -S server -U sa -P password -d userdatabase -Q "exec SP" -o salida.txt
Late answer, but who knows...maybe still could help...
June 7, 2004 at 2:42 pm
thanks a lot, Steve. I will try it
May 13, 2004 at 11:20 am
May 12, 2004 at 12:43 pm
May 11, 2004 at 1:09 pm
i can´t imagine how can i do that on 6.5 version...
May 10, 2004 at 1:26 pm
-See if from the sql server box you can tnsping the box.
-then see if you can connect native via sqlplus.
-Then validate a simple connection via the msdaora...
January 22, 2004 at 10:16 am
MSDAORA. Also using Oracle provider for OLEDB.
Runnig the commands, the information is the same:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDAORA' reported an error. The provider...
January 22, 2004 at 6:33 am
I get this error when i try to see the Oracle tables shareds (through EM, for example). Of course, if i run a distributed query i get the same error...
January 22, 2004 at 5:52 am
January 22, 2004 at 5:34 am
Frank, thanks for your help. I take a look on the link (you was dealing with the same issue, right?), and realize that the most simple solution, i mean check...
November 27, 2003 at 7:49 am