Error:
Microsoft OLE DB Provider for SQL Server error '80040e4d'
Login failed for user 'administrator'.
/ssconn.asp, line 12
Code:
oConn.Open "Provider=sqloledb;" & _
"Network Library=DBMSSOCN;" & _
"Data Source=198.107.136.50,1433;" & _
"Initial Catalog=GradeTrax;" & _
"User ID=administrator;" & _
"Password=password"
Your much wanted advice:
When running the project in debug mode or non-debug mode, I get the following error from MS Visual Studio:
TITLE: Package Validation Error
------------------------------
Package Validation Error
------------------------------
ADDITIONAL INFORMATION:
Error at Package [Connection manager "SYBASE_CONNECTION"]: The connection manager failed to defect from the transaction.
(Microsoft.DataTransformationServices.VsIntegration)
------------------------------
BUTTONS:
OK
------------------------------
Any ideas???
I'm getting "Access denied" error when I try to connect to SSIS from my desktop (Database Engine is fine). I'm a member of sysadmin within SQL, as well as an administrator on the server. I don't have any problem when I log on to the server directly via Remote Desktop and open SSIS.
I went into the surface area config tool, and I see that Database Engine and Analysis Services both expand and have a sub tabs to enable Services and Remote Connections, but Integration Services does not expand to a Remote Connections option, just Services. We're running MSDN Enterprise edition.
Does it matter if all the SQL services are using "Local System" for the logon ? I use an administrative logon on my SQL2000 boxes, and was fiddling with them on the 2005 box yesterday, but it seemed to cause more problems, so they are all Local System for now.
Am I missing something obvious ?
First of all i apologise if this is in the wrong area. My problem is as follows. I had set up a couple of aspx pages on our webserver which accessed a sql database on another server. These pages were set up using frontpage 2003 and everything worked fine. A week ago the pages stopped working giving the error "Server Error in '/' Application". As far as I know nothing has been changed on the servers. On top of this frontpage has started having connection problems. Frontpage will connect to the database but is unable to access the fields giving the following error.
Server error: Unable to retrieve schema information from the record source ' NAME' in a database using the connection string:
'DRIVER={SQL Server};SERVER=servername;DATABASE=live;UID=********;PWD=********'.
The following error message comes from the database driver software; it may appear in a different language depending on how the driver is configured.-------------------------------------------------------[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'NAME'.
Source: Microsoft OLE DB Provider for ODBC DriversNumber: -2147467259 (0x80004005)
I have been trying for the past few days to solve this one, but am reasonable new to SQL, so this may be an easy one.
Hope someone can help me
We recently install SQL Server 7 and we are testing things to get it up to speed so we can use it for our clients. We are having difficulty calling the database from a ASP page. Here is the error it gives in the browser:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''.
/asptest.asp, line 11
Now here is the ASP code:
<%
set conntemp=server.createobject("adodb.connection")
conntemp.open "DSN=Northwind;uid=dbuser;pwd=dbuser"
set rstemp=conntemp.execute("select * from customers")
howmanyfields=rstemp.fields.count -1
%>
I have created a System DSN name Northwind, and a user 'dbuser' on the PDC (running IIS as well). I have gone into SQL Server and added the user dbuser and specified to authenticate it from the PDC. What am I missing? What am I doing wrong?
Could someone please point it out to me.
TIA
-Jason
jason@flnet.com
I had an ODBC connection set up, and it has been working fine for the last week or so.
Suddenly, last night, I started getting this error and I'm at a loss for what to do.
Here is the error that I get:
Hi, I have an access 2003 database which connect to sql server via aDSN that goes through a VPN. The database works fine and everyone cancoonect from their normal computers but for anyone working on theirLaptops (IBM Think Pad T42's) they cannnot connect to the datasource.The DSN fails upon connection attempt with :Connection Failed:SQLState: '01000'SQL Server Error: 1326[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect()).Connection Failed:SQLState: '08001'SQL Server Error: 17[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not existor access is denied.This has been driving me insane as i cannot understand why it works forour desktop computers and not for our laptops. The version of MDAC isthe same on a computer that connects as it is on a laptop that doesn't.TCP/IP is enabled on the server and is using the default 1433 port.severs, desktops and laptops all patches and up to date with the latestSP's. DSN has been dropped and re-created. Domain user has been put inlocalAdmin group for laptop.I hope i'm mising something really obvious....can someone please pleaseput me out of my misery and tell me they have come accross this beforeand have a solution. Ive tried everything i can think of.CheersDan
View 3 Replies View RelatedHere is what I got:
Sql 2005 std on windows 2003 server r2
tcp port 1433 set for connections in Sql 2005
Port open on firewall from DMZ 1433 can connect from web farm telneting from all IP address on port 1433 to sql both by name and IP.
the connection works 99.9% of the time.
No errors in the sql logs showing anything Firewall logs show no blocks. Windows firewall service is disabled to move that out of the troubleshooting.
connection string:
<add key="CommonConnectionString" value="server=servernameinstancename,1433;database=DBname;uid=username;pwd=mypass;Connection Lifetime=30" />
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
I have a package that works fine locally but doesn't work when I deploy it to the server (and reset the connection strings to the local DB and AS instances that are running on the same server)It's not the usual permissions issue; I'm getting something about the SQL Browser not running (it is) and named instances. But my SSAS instance is the default unnamed instance?
The error message is "errors in the oledb provider. could not connect to the redirector. ensure the sql browser is running on the "." server" then another error with "error while retrieving name instance information".I've tried referencing the ssas server using its ip, ., hostname but the package craps out in a few sec
I've verified that the SSAS server is running and i can connect to it using ssms/tableau/excel etc.I've tried changing the service account of the sql browser to use local system.
Hi,
I'm trying to use an OLE DB connection manager from inside a custom log provider, but can't get the code to work - I get an exception "A first chance exception of type 'System.InvalidCastException' occurred in SSEALogProvider.dll" on the last line of the code below.
I know the connection is OLE DB from looking at .CreationName.
I've tried both with & without ToConnectionManager90(), but appearently not in the right way, both cases gives the same exception.
Any tips on what I'm missing? All the examples I've seen are either creating (instead of using) connection managers, or are file based connection managers. Any and all help much appreciated!
Thanks/Kristian
if (this.ConfigString.Length == 0 || connections.Contains(ConfigString) == false ||
connections[ConfigString].CreationName != "OLEDB")
{
infoEvents.FireError(0, "SSEALogProvider", "The ConnectionManager " + ConfigString + " specified in the ConfigString property cannot be found in the collection, or is of the wrong type (expected CreationName='OLEDB'.)", "", 0);
return Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Failure;
}
else
[...]
public override void OpenLog()
{
if (!connections.Contains(this.ConfigString))
throw new Exception("The ConnectionManager " + this.ConfigString + " does not exist in the Connections collection.");
ConnectionManager connectionManager = connections[ConfigString];
IDTSConnectionManager90 connectionManager90 = DtsConvert.ToConnectionManager90(connectionManager);
object connObj = connectionManager90.AcquireConnection(null);
//ConnectionManagerOleDb connectionManagerOleDb = (ConnectionManagerOleDb)(connectionManager.InnerObject);
//object connObj = connectionManagerOleDb.AcquireConnection(null);
if (connObj == null)
{
events.FireError(0, "SSEALogProvider", "Could not connect to the log database with connection string " + ConfigString + ".", "", 0);
return;
}
// Exception on next line: "A first chance exception of type 'System.InvalidCastException' occurred in SSEALogProvider.dll"
OleDbConnection oledbConnection = (OleDbConnection)connObj;
I have an application that talks to a SQL backend using an ODBC DSN connection. It works fine when running on a 32bit machine but fails in the 64bit environment. The DSN is setup properly on the 64bit box and the Test Connection returns sucess. However when my application tries to use the DSN to connect to the database I recieve the following error.
IM002 - Data source name not found and no default driver specified.
The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.
Any help would be appreciated.
I built a small package two years ago that uses Flat File Sources to copy in small text data files. Each source connection object has a UNC path to flat text files on another server. The source system changed, so I opened the package and updated the UNC path in one Connection Manager object, and clicked OK. The Flat File Source Editor that uses this source seemed to be able to see the new location when I clicked "Preview". Then I went back to the file source, and the connection had reverted back to the original one. it would not save the new UNC path.
I am using SQL Server 2012 SP2 with SSDT (run as admin). I closed the package in SSDT, edited the connection strings using XMLnotepad, and was then able to open, test, build and deploy the package.
It seems that the Source object will not let itself be changed. The other option is to delete it and recreate it, but I didn't want to remap the fields.
Why updating a connection object is not working?
Good day,
I am writing an application using VB.Net 2005 for the Windows CE 5.0 device and it is connecting to a SQL Server 2005 Mobile Edition Database.
The trouble I'm having is establishing a connection to a SQL Server Mobile database on the device.
Here is the code I am using:
Code Snippet
Public gConnectionString As String = "Data Source=Program FilesMobAppMobDB.sdf;Persist Security Info=False;"
Code Snippet
Imports System.Data.SqlServerCe
Public Class DBManager
Public Shared gSQLCEConnection As SqlCeConnection
Public Shared Function OpenDB() As Boolean
If gSQLCEConnection IsNot Nothing Then
Throw New InvalidOperationException("Connection already open.")
End If
gSQLCEConnection = New SqlCeConnection(gConnectionString)
Try
gSQLCEConnection.Open() 'Error occurs here
Return True
Catch ex As SqlCeException
MsgBox(ex.Message & vbCrLf & ex.HResult & vbCrLf & ex.NativeError & vbCrLf & ex.Source)
Return False
End Try
End Function
In the immediate window I recieve the following messages:
A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
A first chance exception of type 'System.UnauthorizedAccessException' occurred in mscorlib.dll
A first chance exception of type 'System.UnauthorizedAccessException' occurred in mscorlib.dll
A first chance exception of type 'System.UnauthorizedAccessException' occurred in mscorlib.dll
A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
A first chance exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.dll
A first chance exception of type 'System.UnauthorizedAccessException' occurred in mscorlib.dll
A first chance exception of type 'System.Data.SqlServerCe.SqlCeException' occurred in System.Data.SqlServerCe.dll
I believe that the first few lines are caused by the icons/pictures that I have included with my app, but the SqlCeException line occurs when the connection to the .SDF file is trying to be established.
Here is the exception output:
Message: "" (Blank)
HResult: -2147024882
NativeError: 0
Source: SQL Server 2005 Mobile Edition ADO.NET Data Provider
Programs under Remove Programs on the PDA are:
Microsoft .NET CF 2.0 ENU-String R...
Microsoft .NET Compact Framework...
Microsoft SQL Client
Microsoft SQL Mobile 2005
Microsoft SQL Mobile 2005 [EN]
Microsoft SQL Server 2005 Compact...
Microsoft SQL Server 2005 Compact...
Microsoft SQL Server 2005 Compact...
Microsoft SQLCE 2.0
Microsoft SQLCE 2.0 Dev
Any ideas on what could be stopping this connection from being established? It was working before but all of a sudden just stopped. I have warm booted, cold booted, and rebuilt with no luck and also checked that SQL Query Analyzer is not running on the PDA and that the connection string is valid.
The call to OpenDB occurs in the form_load of the startup object.
Thanks in advance,
Leon
Hi,
I have merge replication configured over VPN and the replication is failing to connect to the subscriber through Named pipes with the error Named Pipes Provider, error: 40 - Could not open a connection to SQL Server ......
Actually , I am having issues with Named pipes connection from publisher to subcriber. I have enabled the protocols and also enabled the remote connections using both tcp/ip and named pipes. I have created the client network alias using named pipes
Also, due to security reasons only few ports have been released on the subscriber. Please provide me some information on the following.
1) Does any port specifically be released for listening on named pipes? i am able to connect using tcpip with out any issues as 1433 has been released.
2) How to configure the replciation to use tcpip and not named pipes (guess by default it will use named pipes)?
I added a connection (ADO.NET) object by name testCon in the connection manager - I wanted to programmatically supply the connection string. So I used the "Expressions" property of the connection object and set the connectionstring to one DTS variable. The idea is to supply the connection string value to the variable - so that the connection object uses my connection string.
Then I added a "Backup Database Task" to my package with the name BkpTask. Now whenever I try to set the connection property of BkpTask to the testCon connection object, by typing testCon, it automatically gets cleared. I am not able to set the connection value.
Then after spending several hours I found that this is because I have customized the connection string in testCon. If I don't customize the connection string, I am able to enter the "testCon" value in the connection property of the BkpTask.
Is this an intrinsic issue?
I have a package that uses a for loop to iterate through an unknown amount of excel files and pull their data into a table. However, there will be cases when the file is corrupted or has some sort of problem so that either the transformation will fail or the excel data source will fail with an oledb connection error.
Could anyone suggest a clean way to trap these errors? Specifically, the "Cannot Aquire Connection from Connection Manager", which is the excel connection.
Thanks,
John T
i ran it from the command prompt. I used my nt account which belongs to the domain admin nt group. my account does have sql access as sa.
also on one of the servers all jobs are failing with the following message - Unable to Connect to Sql Server (local). The nt log records the error that the specific user sqlexec (this is the account on which sql executive runs) is not defined as a valid user of a trusted sql server connection. I am not able to change the security setting on this server using EM nor am i able to use the sql security manager. I get an access denied error. What is the workaround for this problem? Will stopping and restarting the sql service help?
------------
How did you run bcp? In dos prompt or as sql job? Which nt account did you run bcp under? Did you grant sql access for that nt account?
------------
aruna at 1/3/01 4:39:49 PM
Subject:
From:
Date: bcp failing (reply)
Ray Miao ()
1/3/01 4:15:33 PM
yes i did. it still gives me the same error - 18452 error not associated with a trusted connection
-----------------
Did you enable mixed login mode on the server?
------------
aruna at 1/3/01 2:55:59 PM
hello ray
It still does not work. I granted SA rights for the nt group via sql security manager. For one of the servers i get the following error message -
This sql server does not support Windows NT SQL Server Security stored procedures.
--------------
From:
Date: bcp over trusted connections failing (reply)
Ray Miao ()
1/3/01 12:51:50 PM
Use security manager to grant access for nt account.
------------
aruna at 1/3/01 11:59:49 AM
i am attempting to bcp using the -T (trusted connection) option in sql 6.5. the login security mode is set to integrated. the bcp is however failing with msg 18452 error not associated with a trusted connection. why is this happening? i do not want to hardcode the sa password in the bcp command.
thanks
I have an excutable on the c drive and I have created a job to run that excutable
In the Job
C:Folderjob.exe BA
The job was running until we had a power outage. Now I can get it to run with a scheduled job, the only way I can get it to run is typing it on the command line. I have tried droping and recreating this job but nothing works.
The error is: The stip did not generate any out put.
Do I need to troubleshoot the excutable which is a whole other beast.
Any help would be great.
Thanks
We have a sqljob keep failing if we set the ownership of the job other than 'sa'. Any idea why this fails?
View 6 Replies View RelatedHi,
View 6 Replies View RelatedI have a scheduled job on a SQL 2000 database which is failing. Here is the error message :
The job failed. Unable to determine if the owner (cacisnasir) of job Integrity Checks Job for DB Maintenance Plan 'IDS' has server access (reason: Could not obtain information about Windows NT group/user 'cacisnasir'. [SQLSTATE 42000] (Error 8198)).
I am the SA on the instance. I wonder why would I be getting this error message? I am able to logon to this instance and browse and change things. So clearly it recognizes me. But when I run the job it fails. Wonder why? my SQL Server version is 8.0.
Dear Reader,
Currently I am building an application for a theme park where I work as a trainee for school, one project for me is to rebuild all the hundreds of databases into a few sql driven application's. Now I got a problem whit the use of SCOPE_IDENTITY(). Because the data has to be correct before inserting it into the database I use the transact features of .NET and I create 1 SQL string wich I dump in that method. The problem is that I can't be able to use the value of SCOPE_IDENTITY() for some reason, maybe you guys see a mistake in the actual (dynamic) query:
Here is the query built up by my program to write the data (of a single form) into the database:
DECLARE @OID int;
INSERT INTO Medisch (med_za_ID, med_WeekNr, med_Enen, med_Bijzonderheden, med_AfwijkendGedrag, med_SexGedrag, med_GemAdemhaling, med_GemHoesten, med_Temperatuur, med_Conditie, med_BloedGeprikt, med_Cupje, med_BasisVis, med_Eetlust, med_GemGewicht)VALUES(3,1123,,'','','',,,,'','False','False',45,'',);
SELECT @OID = SCOPE_IDENTITY();
INSERT INTO Medisch_Medicijnen_Details (mmd_mmt_ID, mmd_med_ID, mmd_Hoeveelheid, mmd_Aantal) VALUES(@OID, 2,23, 23 );
Everything else works unless the SCOPE_IDENTITY() things.
I hope someone can help me out fixing this mistake.
Tnx in advanced,
Grz.
Stefan
Sql Guru's,
I have some DTS packages some times failing.one day sucess and next day it's failing. The following error showing.
DTSRun: Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_3 DTSRun OnError: DTSStep_DTSExecuteSQLTask_3, Error = -2147217900 (80040E14) Error string: OLE DB provider 'SQLOLEDB' reported an error. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147217900 (80040E14); Provider Error: 7399 (1CE7) Error string: OLE DB provider 'SQLOLEDB' reported an error. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error: -2147217900 (80040E14); Provider Error: 7312 (1C90) Error string: [OLE/DB provider returned message: Timeout expired] Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_3 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRu... Process Exit Code 1. The step failed.
Any body help me. This is very urgent
this is the message that i'm getting and i dont know what to do so that i can access my SQL databases thru cold fusion:
ODBC Error Code = 37000(Syntax error or access violation)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
i didnt have any problems with this database until i moved it over to another SQL server and tried the cold fusion front end to it. i dont know what to do now.
I have inherited the task of setting some standards for SQL Server setup and usage in my company. Use of SA with and without a password was rampant. As I get DTS jos and VB code changed to use another account I have been securing the SA account with a password that no one uses. I now get a multitude of failed logins for the SA account on multiple systems by people trying to logon as SA, not jobs. Is there any way to generate an error message that will pass the host PC or server, or network ID of the user trying to login with the SA account?
Thanks in advance.
Bill
When I create a DTS to import data from Visual FoxPro it will work if I run immeadiately, but when I schedule it to run at a specific time it will Fail.
Any ideas why??
Thanks for any input,
Tom
HELP!
I have a table with a field called remarks as text field. I have a trigger on it,
"Create Trigger trg_inbox_bess506a_mstr_on_del
On dbo.inbox_bess506a_mstr
For Delete
As
-- 040226, archive inbox to arc
set nocount on
insert into inbox_bess_mstr_arc (
pk_id,
batch_id,
py,
appropriation,
issueFrom,
issueTo,
submitBy,
submitDate,
validID,
validDate,
approveDate,
approveBy,
accountCode,
transType
--remark
)
select
pk_id,
batch_id,
py,
appropriation,
issueFrom,
issueTo,
submitBy,
submitDate,
validID,
validDate,
approveDate,
approveBy,
accountCode,
transType
--remark
from deleted
return
GO"
It fails with an error message:
"Server: Msg 21, Level 22, State 1, Procedure
trg_inbox_bess506a_mstr_on_del,
Line 8
WARNING - Fatal Error 7113 occurred at Dec 22 2004 11:25PM. Please
note the
error and time, and contact your System Administrator."
It's failing on a field with remarks greater than 1885 chars.
When I used a stored procedure to do the same, it worked. Why is the trigger failing now? Is there a limit on size for triggers and not procedures?
THANKS!!!!!!
The DTS package would execute and immediately fail. a reboot of this server fixed the problems, but does anyone know how to get more info out of DTS to state why it failed, we have branch on error and NT event log entries, but nothing specific to state why. The 1st task is to assign global variables, but I'm not even sure it got that far.
Obviously the problem is fixed now, but if it happens again, some ideas of how to get data out would be useful.
Hello I have two tables that have the same data in them but not all the data is in the new table. the old one has 397 more records then the new one and I need to insert that data in the new table but it keeps giving me a primary key violation rule.
SELECT dbo.Revised_MainTable.[IR Number], dbo.Report.[Incident Report No], dbo.Report.Date, dbo.Report.[I/RDocument], dbo.Report.TypeOfIncident
FROM dbo.Revised_MainTable RIGHT OUTER JOIN
dbo.Report ON dbo.Revised_MainTable.[IR Number] = dbo.Report.[Incident Report No]
WHERE (dbo.Revised_MainTable.[IR Number] IS NULL)
Can anyone help me please???
got it, thanks
View 5 Replies View RelatedI have a SP that basically copies data from one table to another.
Some of the data could be duplicates and so the SP detects any primary
key violations (error 2627) and if detected uses a random number for
the PK and tries the insert again.
This SP works fine when run manually from Management Studio but when
scheduled as a job step, it fails. From investigation, it seems that
the logic to handle PK violations is being processed but if there are
more than around 16 PK violations in the batch copy, the job step
fails at around the 17th violation insert and fails to process the
rest of the step.
When this happens, as well as seeing the 2627 error logged in the
message field of the job log history, it also records an error code
3621 in the SQL Message ID field of the log with Severity 14.
Does anyone know why this SP should fail as a job? I have checked
permissions and also tried setting the agent login and job owner to
the same account that successfully ran the SP in Mangement Studio but
this also failed.
At present the only way to get this job to run is to set the step
retry attempts to a number greater than the number of fails. Each
time the job is rerun, it will process a certain number before failing
and it only fails after processing a certain number of PK violations.
This work around is fine in a test environment of a few hundred
records but this job needs to process roughly 75,000 records and if all
these happened to be duplicates, it would require over 4500 retries
assuming its fails after every 16 records.
Thanks in advance.
Matt
I have a SP that basically copies data from one table to another.
Some of the data could be duplicates and so the SP detects any primary
key violations (error 2627) and if detected uses a random number for
the PK and tries the insert again.
This SP works fine when run manually from Management Studio but when
scheduled as a job step, it fails. From investigation, it seems that
the logic to handle PK violations is being processed but if there are
more than around 16 PK violations in the batch copy, the job step
fails at around the 17th violation insert and fails to process the
rest of the step.
When this happens, as well as seeing the 2627 error logged in the
message field of the job log history, it also records an error code
3621 in the SQL Message ID field of the log with Severity 14.
Does anyone know why this SP should fail as a job? I have checked
permissions and also tried setting the agent login and job owner to
the same account that successfully ran the SP in Mangement Studio but
this also failed.
At present the only way to get this job to run is to set the step
retry attempts to a number greater than the number of fails. Each
time the job is rerun, it will process a certain number before failing
and it only fails after processing a certain number of PK violations.
This work around is fine in a test environment of a few hundred
records but this job needs to process roughly 75,000 records and if all
these happened to be duplicates, it would require over 4500 retries
assuming its fails after every 16 records.
Thanks in advance.
Matt
Job is failing for one DB
I receive below errors
EVENT LOG:
sql server scheduled job 'db name'
(0x5EA2833965097647B1D375899CE3E179)-Status Failed-Invoked on 2007-12-09 00:01-Message: The Job Failed.The job was invoked by schedule1 (sunday 12 am) . The last step to run was step 2(db name)
Job History:
step 1:
Excuted as user NT AUTHORITYSYSTEM. The step succeeded
step 2:
Excuted as user: NT AUTHORITYSYSTEM . Invalid object name '#DiskSize'.[SQL STATE 42S02][Error 208]. The step failed.
step 3:
The job failed. The job was invoked by Schedule 1 (sun 12 am). The last step to run was step 2{db name}
I am new to SQL server, please help?
Thanks in advance