Showing posts with label databases. Show all posts
Showing posts with label databases. Show all posts

Tuesday, March 27, 2012

Error 18210 Backup up SQL Server 2005 Database to network drive

I have 2 different servers that run nightly backup jobs to a network drive using the UNC format. I am noticing the larger databases encountering the following errors on a regular basis

Error: 18210, Severity: 16, State: 1.

'\\fnfssql3\SQLBackups\MNSQL05\<database>.BAK'. Operating system error 64(The specified network name is no longer available.).

BACKUP failed to complete the command BACKUP DATABASE <database>. Check the backup application log for detailed messages.

There are 5 databases on this server all backed up by the same job and 3 of them wortk fine and 2 of them fail so it is not a permissions problem. Have there been any problems with backing up to a network drive in 2005?

Well, backing up to networks drives is not officially *supported*, thats why the browser only display the local drives.

The reason for that and the logical explanation why you shouldn′t do that is, because the network is less reliable than local drives. If you want to make sure the database is backuped to network, you will have to either make sure the windows where the backups are streamed to the network don′t interfer with each other or you use a local backup to a drive and copy the files later over. Thats the most reliable option beside using a NAS / SAN.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Network hic-up can do this. One can see such error without sql involved.

Try trapping the error and retry the operation. Also, try backing up locally as suggested by Jens.

|||

Backing up database to a UNC path is fully supported. You must be thinking of running the database from a network drive.

http://support.microsoft.com/kb/304261

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlbackuprest.mspx

|||

Oj,

the reason why I put *supported* in stars is, that it is sure supported, but not reliable in terms of just having a network share associated on a UNC share. (I thought he explanation should made that clearer, sorry for the poor explanation :-) ) The reliablity descrease due to your mentioned outages on the network. Having big backup files for the transfer over the network is there not recommended undless you have a SAN or a NAS which ensures more reliablity for the transfer. I often used the UNC path backup too on customer sites but either tried to shape the task to copy the files to different time windows or used a local backup and copied the files over with a mechanism (like xcopy / robocopy) to restart in the case of a connection loss.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Wednesday, March 21, 2012

Error 14294 in replication

Hi
I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
This server has several published databases that they replicate data to
another server.
All the replications is of transactional type.
When creating to publish another database it leaves me the following error:
Error 14294
Supply either @.job_id or @.job_name to indentify the job.
That I can make to correct the problem?
Thank you
are you or have you deployed the other publications using a script?
If you, you must use unique publication names and ensure that you don't
specify a snapshot agent name, log reader agent name, or distribution agent
name.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario" <Mario@.discussions.microsoft.com> wrote in message
news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> Hi
> I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
> This server has several published databases that they replicate data to
> another server.
> All the replications is of transactional type.
> When creating to publish another database it leaves me the following
error:
> Error 14294
> Supply either @.job_id or @.job_name to indentify the job.
> That I can make to correct the problem?
> Thank you
|||Hi Hilary
I don′t use a script, my publications was created by wizard.
"Hilary Cotter" wrote:

> are you or have you deployed the other publications using a script?
> If you, you must use unique publication names and ensure that you don't
> specify a snapshot agent name, log reader agent name, or distribution agent
> name.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario" <Mario@.discussions.microsoft.com> wrote in message
> news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> error:
>
>
|||Can you do a Select @.@.SERVERNAME on your publisher and see what server name
it returns? Did you rename this server recently.
There are some reports that this error can be cleared by disabling
replication on your publisher and then recreating it.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario" <Mario@.discussions.microsoft.com> wrote in message
news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> Hi
> I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
> This server has several published databases that they replicate data to
> another server.
> All the replications is of transactional type.
> When creating to publish another database it leaves me the following
error:
> Error 14294
> Supply either @.job_id or @.job_name to indentify the job.
> That I can make to correct the problem?
> Thank you

Monday, March 19, 2012

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I can
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom JuergensHi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have the
same problem? Or maybe deleting the existing maintenance plan and creating it
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:
> We have a maintainance plan for full/diff/log backups of selected databases
> running at regular intervals through SQLAgent. The backups are working; I can
> restore the databases. But starting a few weeks ago we've been getting error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Server
> "ERRORLOG" text file also contains no error messages in connection with the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||Thanks to you both for the pointers and good ideas. I'll try your suggestions
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have the
> same problem? Or maybe deleting the existing maintenance plan and creating it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried running
> the package manually from SSIS (like using the Execute Package Utility) and
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
> > We have a maintainance plan for full/diff/log backups of selected databases
> > running at regular intervals through SQLAgent. The backups are working; I can
> > restore the databases. But starting a few weeks ago we've been getting error
> > messages in the system event log.
> >
> > First, there's an entry confirming the successful completion of the backups
> > with ID 18265 (source MSSQL$...)
> > Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> > followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> > Error ..." (source SQLAgent$...)
> >
> > As I said, the backups themselves seem to be successful, and the SQL Server
> > "ERRORLOG" text file also contains no error messages in connection with the
> > plans.
> >
> > This is still worrying us a bit, because we fear there might be a good
> > reason for these error messages, and obviously we want to be quite certain
> > that our backups are working properly and will be available if and when we
> > need them.
> >
> > Does anyone have any insight/advice on Error 12291?
> >
> > Thanks
> > Tom Juergens|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:
> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>

Friday, March 9, 2012

Error 1038: Cannot use empty object or coymn names.Use a single sp

hi,
in SQL server, when list down the databases, there is a database without any
name.
also, when i click on the properties option of any other databases, i get
the following error : "Error 1038: Cannot use empty object or coymn names.
Use a single space if necessary".
I am not able to delete the unnamed database.
can any body suggest what to do in this case.
thanks and Regards
Jagminder
just try this in the Query Analyser
sp_renamedb '', 'new_name'
drop database new_name
please let me know, if it worked.
best Regards,
Chandra
http://chanduas.blogspot.com/
http://groups.msn.com/SQLResource/
"Jagminder Chugh" wrote:

> hi,
> in SQL server, when list down the databases, there is a database without any
> name.
> also, when i click on the properties option of any other databases, i get
> the following error : "Error 1038: Cannot use empty object or coymn names.
> Use a single space if necessary".
> I am not able to delete the unnamed database.
> can any body suggest what to do in this case.
> thanks and Regards
> Jagminder
|||Hi,
Try issuing the below command:-
DROP DATABASE []
or
DROP DATABASE [ ]
Thanks
Hari
SQL Server MVP
"Jagminder Chugh" <JagminderChugh@.discussions.microsoft.com> wrote in
message news:AB972FBE-58DF-4473-8807-497DB9F7A45B@.microsoft.com...
> hi,
> in SQL server, when list down the databases, there is a database without
> any
> name.
> also, when i click on the properties option of any other databases, i get
> the following error : "Error 1038: Cannot use empty object or coymn names.
> Use a single space if necessary".
> I am not able to delete the unnamed database.
> can any body suggest what to do in this case.
> thanks and Regards
> Jagminder

Error 1038: Cannot use empty object or coymn names.Use a single sp

hi,
in SQL server, when list down the databases, there is a database without any
name.
also, when i click on the properties option of any other databases, i get
the following error : "Error 1038: Cannot use empty object or coymn names.
Use a single space if necessary".
I am not able to delete the unnamed database.
can any body suggest what to do in this case.
thanks and Regards
Jagminderjust try this in the Query Analyser
sp_renamedb '', 'new_name'
drop database new_name
please let me know, if it worked.
--
best Regards,
Chandra
http://chanduas.blogspot.com/
http://groups.msn.com/SQLResource/
---
"Jagminder Chugh" wrote:
> hi,
> in SQL server, when list down the databases, there is a database without any
> name.
> also, when i click on the properties option of any other databases, i get
> the following error : "Error 1038: Cannot use empty object or coymn names.
> Use a single space if necessary".
> I am not able to delete the unnamed database.
> can any body suggest what to do in this case.
> thanks and Regards
> Jagminder|||Hi,
Try issuing the below command:-
DROP DATABASE []
or
DROP DATABASE [ ]
Thanks
Hari
SQL Server MVP
"Jagminder Chugh" <JagminderChugh@.discussions.microsoft.com> wrote in
message news:AB972FBE-58DF-4473-8807-497DB9F7A45B@.microsoft.com...
> hi,
> in SQL server, when list down the databases, there is a database without
> any
> name.
> also, when i click on the properties option of any other databases, i get
> the following error : "Error 1038: Cannot use empty object or coymn names.
> Use a single space if necessary".
> I am not able to delete the unnamed database.
> can any body suggest what to do in this case.
> thanks and Regards
> Jagminder|||hi
thanks for your reply
i tried it but did not work...its giving the same error.
can you suggest some other alternative
Jagminder
"Chandra" wrote:
> just try this in the Query Analyser
> sp_renamedb '', 'new_name'
> drop database new_name
> please let me know, if it worked.
> --
> best Regards,
> Chandra
> http://chanduas.blogspot.com/
> http://groups.msn.com/SQLResource/
> ---
>
> "Jagminder Chugh" wrote:
> > hi,
> >
> > in SQL server, when list down the databases, there is a database without any
> > name.
> > also, when i click on the properties option of any other databases, i get
> > the following error : "Error 1038: Cannot use empty object or coymn names.
> > Use a single space if necessary".
> >
> > I am not able to delete the unnamed database.
> >
> > can any body suggest what to do in this case.
> >
> > thanks and Regards
> >
> > Jagminder|||hi
i tried
dropdatabase [ ] and it worked.
thanks for the reply
regards
Jagminder Chugh
IT Consultant
"Chandra" wrote:
> just try this in the Query Analyser
> sp_renamedb '', 'new_name'
> drop database new_name
> please let me know, if it worked.
> --
> best Regards,
> Chandra
> http://chanduas.blogspot.com/
> http://groups.msn.com/SQLResource/
> ---
>
> "Jagminder Chugh" wrote:
> > hi,
> >
> > in SQL server, when list down the databases, there is a database without any
> > name.
> > also, when i click on the properties option of any other databases, i get
> > the following error : "Error 1038: Cannot use empty object or coymn names.
> > Use a single space if necessary".
> >
> > I am not able to delete the unnamed database.
> >
> > can any body suggest what to do in this case.
> >
> > thanks and Regards
> >
> > Jagminder

Error 1038: Cannot use empty object or coymn names.Use a single sp

hi,
in SQL server, when list down the databases, there is a database without any
name.
also, when i click on the properties option of any other databases, i get
the following error : "Error 1038: Cannot use empty object or coymn names.
Use a single space if necessary".
I am not able to delete the unnamed database.
can any body suggest what to do in this case.
thanks and Regards
Jagminderjust try this in the Query Analyser
sp_renamedb '', 'new_name'
drop database new_name
please let me know, if it worked.
best Regards,
Chandra
http://chanduas.blogspot.com/
http://groups.msn.com/SQLResource/
---
"Jagminder Chugh" wrote:

> hi,
> in SQL server, when list down the databases, there is a database without a
ny
> name.
> also, when i click on the properties option of any other databases, i get
> the following error : "Error 1038: Cannot use empty object or coymn names.
> Use a single space if necessary".
> I am not able to delete the unnamed database.
> can any body suggest what to do in this case.
> thanks and Regards
> Jagminder|||Hi,
Try issuing the below command:-
DROP DATABASE []
or
DROP DATABASE [ ]
Thanks
Hari
SQL Server MVP
"Jagminder Chugh" <JagminderChugh@.discussions.microsoft.com> wrote in
message news:AB972FBE-58DF-4473-8807-497DB9F7A45B@.microsoft.com...
> hi,
> in SQL server, when list down the databases, there is a database without
> any
> name.
> also, when i click on the properties option of any other databases, i get
> the following error : "Error 1038: Cannot use empty object or coymn names.
> Use a single space if necessary".
> I am not able to delete the unnamed database.
> can any body suggest what to do in this case.
> thanks and Regards
> Jagminder

Sunday, February 19, 2012

ERROR - SQL Server 7, Reporting Services, and SQL 2000 Functions

I sincerely hope this is not the case...
Is it safe to assume that SQL Server Reporting Services cannot "talk" to SQL
Server 7 databases?
One of our developers is trying to run a simple test query against our SQL
Server 7 database; however, he is getting errors : "'DATABASEPROPERTYEX' is
not a recognized function name.". This is native to SQL 2000, though - so we
know why the error is occuring.
The question is why not use DATABASEPROPERTY for backwards compatibility?
How can we work around this limitation? We have tried modifying the provider
properties with no success; it appears this function call occurs behind the
scenes.
Thank you for your insight.
--
Elliot M. Rodriguez, MCSD
My .Net blog, with tips here and there:
http://derivedclass.europe.webmatrixhosting.netSQL7 did not support collations like SQL2000 does and the DATABASEPROPERTY
function does not have a Collation property. Having said that, this could
have been handled better :-)
You need to go to the "Data Options" tab of the "Dataset" dialog in
report designer for any datasets originating from SQL7
On the Data Options tab you will see that all settings contain "Auto".
Replace the Auto-settings with the following settings:
Collation = Latin1_General
Case sensitivity = false
Kanatype sensitivity = false
Width sensitivity = false
Accent sensitivity = true
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Elliot M. Rodriguez" <someemail> wrote in message
news:%23LY0TvJ9DHA.2756@.TK2MSFTNGP10.phx.gbl...
> I sincerely hope this is not the case...
> Is it safe to assume that SQL Server Reporting Services cannot "talk" to
SQL
> Server 7 databases?
> One of our developers is trying to run a simple test query against our SQL
> Server 7 database; however, he is getting errors : "'DATABASEPROPERTYEX'
is
> not a recognized function name.". This is native to SQL 2000, though - so
we
> know why the error is occuring.
> The question is why not use DATABASEPROPERTY for backwards compatibility?
> How can we work around this limitation? We have tried modifying the
provider
> properties with no success; it appears this function call occurs behind
the
> scenes.
> Thank you for your insight.
> --
> Elliot M. Rodriguez, MCSD
> My .Net blog, with tips here and there:
> http://derivedclass.europe.webmatrixhosting.net
>|||Jasper:
MANY thanks - works as described. I hope a KB comes of this; this is going
on my blog (with credit to you, of course :D)
--
Elliot M. Rodriguez, MCSD
My .Net blog, with tips here and there:
http://derivedclass.europe.webmatrixhosting.net
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:etPHbvL9DHA.2028@.TK2MSFTNGP10.phx.gbl...
> SQL7 did not support collations like SQL2000 does and the DATABASEPROPERTY
> function does not have a Collation property. Having said that, this could
> have been handled better :-)
> You need to go to the "Data Options" tab of the "Dataset" dialog in
> report designer for any datasets originating from SQL7
> On the Data Options tab you will see that all settings contain "Auto".
> Replace the Auto-settings with the following settings:
> Collation = Latin1_General
> Case sensitivity = false
> Kanatype sensitivity = false
> Width sensitivity = false
> Accent sensitivity = true
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Elliot M. Rodriguez" <someemail> wrote in message
> news:%23LY0TvJ9DHA.2756@.TK2MSFTNGP10.phx.gbl...
> > I sincerely hope this is not the case...
> >
> > Is it safe to assume that SQL Server Reporting Services cannot "talk" to
> SQL
> > Server 7 databases?
> >
> > One of our developers is trying to run a simple test query against our
SQL
> > Server 7 database; however, he is getting errors : "'DATABASEPROPERTYEX'
> is
> > not a recognized function name.". This is native to SQL 2000, though -
so
> we
> > know why the error is occuring.
> >
> > The question is why not use DATABASEPROPERTY for backwards
compatibility?
> > How can we work around this limitation? We have tried modifying the
> provider
> > properties with no success; it appears this function call occurs behind
> the
> > scenes.
> >
> > Thank you for your insight.
> >
> > --
> > Elliot M. Rodriguez, MCSD
> >
> > My .Net blog, with tips here and there:
> > http://derivedclass.europe.webmatrixhosting.net
> >
> >
>

Friday, February 17, 2012

error

Hi

The company I currently work for backups its SQL databases by

dumping them into a shared folder on nearby sysem. Once in a blue moon

the following error appears on the screen of the SQL server:

Windows - Delayed Write Failed

Windows was unable to save all the data for the file

\Device\LanmanRedirector\10.100.20.7\backup\logs\DB backup 4 hour cycle to remotesrv

storage4_200608150615.txt. The data has been lost. This error may be caused by

a failure of your computer hardware or network connection. Please try to save

this file elsewhere.

There are other processes that talk to other shares (on the same drive

on the same remote system) and none of them gives me the above

error. What more both systems are on the same LAN and IP subnet that is

very lightly used. The network cables are all high grade CAT6

cable (machine cripmed). I'm not a windows/SQL

Administrator (Unix is my background), so if I'm asking the wrong

questions in the wrong forum please kindly redirect me to the right

forum.

Why does this error popup?

TIA

Paolo

One place you might try is to take a look at the Array Controller Read/Write Cache ratio on the target server. If the controller is set to 100% Read, this type of error could happen. You could also take a look at the array controller on the server initiating the backups. The controller should never be set to 100% Read, although even though it may be, it doesn't allow no Write caching. However, if there is too much data being written to the array and there isn't enough Write cache, you could experience the type of failures you are seeing. Also make sure there are no failed disks in the array. You may also want to make sure that all of the storage drivers are up to date as well.