I am trying to move a database from one machine to another by taking a
backup from one and restoring it on another. Both machines are W2k sp3 with
SQL2k sp3. As far as I can tell they are both straightforward, standard
installations (OS and DB), except;
The target machine has been partitioned into three (system, apps, and data),
and the disk is mirrored.
I can take the backup and restore it to a number of machines, but on the
machine that I need to restore the database to I get;
Microsoft SQL-DMO(ODBC SQL State: 42000)
There is insufficient free space on disk volume e:\ to create the database.
The database requires 16519462912 additional free bytes, while only
6329229312 bytes are available.
RESTORE DATABASE is terminating abnormally.
The database backup file is only 146M, the data file is 143M and the log
file is 15M.
The data partition (e:) has 8G free space, although the system/boot
partition (c:) has about 2G
Does anyone have any ideas how this could be happening?
--
regards,
Paul DurdinHi.
The data partition (e:) need + - 16 GB. free,you only have
+ - 6 GB.
>--Original Message--
>I am trying to move a database from one machine to
another by taking a
>backup from one and restoring it on another. Both
machines are W2k sp3 with
>SQL2k sp3. As far as I can tell they are both
straightforward, standard
>installations (OS and DB), except;
>The target machine has been partitioned into three
(system, apps, and data),
>and the disk is mirrored.
>I can take the backup and restore it to a number of
machines, but on the
>machine that I need to restore the database to I get;
>Microsoft SQL-DMO(ODBC SQL State: 42000)
>There is insufficient free space on disk volume e:\ to
create the database.
>The database requires 16519462912 additional free bytes,
while only
>6329229312 bytes are available.
>RESTORE DATABASE is terminating abnormally.
>The database backup file is only 146M, the data file is
143M and the log
>file is 15M.
>The data partition (e:) has 8G free space, although the
system/boot
>partition (c:) has about 2G
>Does anyone have any ideas how this could be happening?
>--
>regards,
>Paul Durdin
>
>.
>|||That's indeed what the error message says - but surely you telling me that a
140M database needs 16G to restore it!
--
regards,
"Jorge Lavado" <jorge.Lavado@.cgey.com_NO_SPAM> wrote in message
news:0aab01c3aa9b$1255c6d0$a101280a@.phx.gbl...
> Hi.
> The data partition (e:) need + - 16 GB. free,you only have
> + - 6 GB.
> >--Original Message--
> >I am trying to move a database from one machine to
> another by taking a
> >backup from one and restoring it on another. Both
> machines are W2k sp3 with
> >SQL2k sp3. As far as I can tell they are both
> straightforward, standard
> >installations (OS and DB), except;
> >The target machine has been partitioned into three
> (system, apps, and data),
> >and the disk is mirrored.
> >
> >I can take the backup and restore it to a number of
> machines, but on the
> >machine that I need to restore the database to I get;
> >
> >Microsoft SQL-DMO(ODBC SQL State: 42000)
> >There is insufficient free space on disk volume e:\ to
> create the database.
> >The database requires 16519462912 additional free bytes,
> while only
> >6329229312 bytes are available.
> >RESTORE DATABASE is terminating abnormally.
> >
> >The database backup file is only 146M, the data file is
> 143M and the log
> >file is 15M.
> >The data partition (e:) has 8G free space, although the
> system/boot
> >partition (c:) has about 2G
> >
> >Does anyone have any ideas how this could be happening?
> >--
> >regards,
> >
> >Paul Durdin
> >
> >
> >.
> >|||When you restore a database, you need the same amount of space for the mdf,
ndf and ldf as the size those files had when you did the backup. If the
files were smaller when you did the backup and the restore claims you need
more space, you have hit a bug in SQL Server (I haven't heard of such a bug,
though). A couple of things:
Make sure that you restore the correct backup. One backup file can have more
than one backup. Check using RESTORE HEADERONLY.
Check the size needed according to the backup. Use RESTORE FILELISTONLY.
Make sure you specify the correct FILE = if the backup file has more then
one backup.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
news:%23Vrx9mqqDHA.2644@.TK2MSFTNGP09.phx.gbl...
> That's indeed what the error message says - but surely you telling me that
a
> 140M database needs 16G to restore it!
> --
> regards,
>
> "Jorge Lavado" <jorge.Lavado@.cgey.com_NO_SPAM> wrote in message
> news:0aab01c3aa9b$1255c6d0$a101280a@.phx.gbl...
> > Hi.
> > The data partition (e:) need + - 16 GB. free,you only have
> > + - 6 GB.
> >
> > >--Original Message--
> > >I am trying to move a database from one machine to
> > another by taking a
> > >backup from one and restoring it on another. Both
> > machines are W2k sp3 with
> > >SQL2k sp3. As far as I can tell they are both
> > straightforward, standard
> > >installations (OS and DB), except;
> > >The target machine has been partitioned into three
> > (system, apps, and data),
> > >and the disk is mirrored.
> > >
> > >I can take the backup and restore it to a number of
> > machines, but on the
> > >machine that I need to restore the database to I get;
> > >
> > >Microsoft SQL-DMO(ODBC SQL State: 42000)
> > >There is insufficient free space on disk volume e:\ to
> > create the database.
> > >The database requires 16519462912 additional free bytes,
> > while only
> > >6329229312 bytes are available.
> > >RESTORE DATABASE is terminating abnormally.
> > >
> > >The database backup file is only 146M, the data file is
> > 143M and the log
> > >file is 15M.
> > >The data partition (e:) has 8G free space, although the
> > system/boot
> > >partition (c:) has about 2G
> > >
> > >Does anyone have any ideas how this could be happening?
> > >--
> > >regards,
> > >
> > >Paul Durdin
> > >
> > >
> > >.
> > >
>|||Thanks for the suggestions.
I've checked the backup file using RESTORE FILELISTONLY FROM
FILE='backupfilename'
This reports the log file as 16377380864 (where have I seem this figure
before?) So I guess that explains why SQLSvr says it cant restore the
database.
I checked the log file size in EM to be 14,643M, but the physical log file
is actually 14,993,664k.
Being a newbie to SQL DBA stuff I am puzzled. How come the physical size is
different from the size recorded in EM?
I did a bit of reading, and I am starting to get a bit of an understanding,
so I did a...
DBCC SHRINKDATABASE (databasename)
followed by
BACKUP LOG databasename WITH TRUNCATE_ONLY
Then did another backup and examined the backup as above. I get much the
same figures as before.
How can I shrink the log file (having already dome the above).
--
regards,
Paul Durdin
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:e1HtntqqDHA.2588@.tk2msftngp13.phx.gbl...
> When you restore a database, you need the same amount of space for the
mdf,
> ndf and ldf as the size those files had when you did the backup. If the
> files were smaller when you did the backup and the restore claims you need
> more space, you have hit a bug in SQL Server (I haven't heard of such a
bug,
> though). A couple of things:
> Make sure that you restore the correct backup. One backup file can have
more
> than one backup. Check using RESTORE HEADERONLY.
> Check the size needed according to the backup. Use RESTORE FILELISTONLY.
> Make sure you specify the correct FILE = if the backup file has more then
> one backup.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
> news:%23Vrx9mqqDHA.2644@.TK2MSFTNGP09.phx.gbl...
> > That's indeed what the error message says - but surely you telling me
that
> a
> > 140M database needs 16G to restore it!
> >
> > --
> > regards,
> >
> >
> > "Jorge Lavado" <jorge.Lavado@.cgey.com_NO_SPAM> wrote in message
> > news:0aab01c3aa9b$1255c6d0$a101280a@.phx.gbl...
> > > Hi.
> > > The data partition (e:) need + - 16 GB. free,you only have
> > > + - 6 GB.
> > >
> > > >--Original Message--
> > > >I am trying to move a database from one machine to
> > > another by taking a
> > > >backup from one and restoring it on another. Both
> > > machines are W2k sp3 with
> > > >SQL2k sp3. As far as I can tell they are both
> > > straightforward, standard
> > > >installations (OS and DB), except;
> > > >The target machine has been partitioned into three
> > > (system, apps, and data),
> > > >and the disk is mirrored.
> > > >
> > > >I can take the backup and restore it to a number of
> > > machines, but on the
> > > >machine that I need to restore the database to I get;
> > > >
> > > >Microsoft SQL-DMO(ODBC SQL State: 42000)
> > > >There is insufficient free space on disk volume e:\ to
> > > create the database.
> > > >The database requires 16519462912 additional free bytes,
> > > while only
> > > >6329229312 bytes are available.
> > > >RESTORE DATABASE is terminating abnormally.
> > > >
> > > >The database backup file is only 146M, the data file is
> > > 143M and the log
> > > >file is 15M.
> > > >The data partition (e:) has 8G free space, although the
> > > system/boot
> > > >partition (c:) has about 2G
> > > >
> > > >Does anyone have any ideas how this could be happening?
> > > >--
> > > >regards,
> > > >
> > > >Paul Durdin
> > > >
> > > >
> > > >.
> > > >
> >
> >
>|||Seems like EM reports the size incorrectly... Where in EM do you see that
space reported? In the taskpad or right-click the database, properties?
To shrink log, Check out below KB articles:
INF: How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/default.aspx?scid=kb;en-us;256650
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
Log File Grows too big
http://www.support.microsoft.com/?id=317375
Log file filling up
http://www.support.microsoft.com/?id=110139
Considerations for Autogrow and AutoShrink
http://www.support.microsoft.com/?id=315512
http://www.mssqlserver.com/faq/logs-shrinklog.asp
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
news:OBrU7YsqDHA.3844@.tk2msftngp13.phx.gbl...
> Thanks for the suggestions.
> I've checked the backup file using RESTORE FILELISTONLY FROM
> FILE='backupfilename'
> This reports the log file as 16377380864 (where have I seem this figure
> before?) So I guess that explains why SQLSvr says it cant restore the
> database.
> I checked the log file size in EM to be 14,643M, but the physical log file
> is actually 14,993,664k.
> Being a newbie to SQL DBA stuff I am puzzled. How come the physical size
is
> different from the size recorded in EM?
> I did a bit of reading, and I am starting to get a bit of an
understanding,
> so I did a...
> DBCC SHRINKDATABASE (databasename)
> followed by
> BACKUP LOG databasename WITH TRUNCATE_ONLY
> Then did another backup and examined the backup as above. I get much the
> same figures as before.
> How can I shrink the log file (having already dome the above).
> --
> regards,
> Paul Durdin
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:e1HtntqqDHA.2588@.tk2msftngp13.phx.gbl...
> > When you restore a database, you need the same amount of space for the
> mdf,
> > ndf and ldf as the size those files had when you did the backup. If the
> > files were smaller when you did the backup and the restore claims you
need
> > more space, you have hit a bug in SQL Server (I haven't heard of such a
> bug,
> > though). A couple of things:
> >
> > Make sure that you restore the correct backup. One backup file can have
> more
> > than one backup. Check using RESTORE HEADERONLY.
> > Check the size needed according to the backup. Use RESTORE FILELISTONLY.
> > Make sure you specify the correct FILE = if the backup file has more
then
> > one backup.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at:
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> > "Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
> > news:%23Vrx9mqqDHA.2644@.TK2MSFTNGP09.phx.gbl...
> > > That's indeed what the error message says - but surely you telling me
> that
> > a
> > > 140M database needs 16G to restore it!
> > >
> > > --
> > > regards,
> > >
> > >
> > > "Jorge Lavado" <jorge.Lavado@.cgey.com_NO_SPAM> wrote in message
> > > news:0aab01c3aa9b$1255c6d0$a101280a@.phx.gbl...
> > > > Hi.
> > > > The data partition (e:) need + - 16 GB. free,you only have
> > > > + - 6 GB.
> > > >
> > > > >--Original Message--
> > > > >I am trying to move a database from one machine to
> > > > another by taking a
> > > > >backup from one and restoring it on another. Both
> > > > machines are W2k sp3 with
> > > > >SQL2k sp3. As far as I can tell they are both
> > > > straightforward, standard
> > > > >installations (OS and DB), except;
> > > > >The target machine has been partitioned into three
> > > > (system, apps, and data),
> > > > >and the disk is mirrored.
> > > > >
> > > > >I can take the backup and restore it to a number of
> > > > machines, but on the
> > > > >machine that I need to restore the database to I get;
> > > > >
> > > > >Microsoft SQL-DMO(ODBC SQL State: 42000)
> > > > >There is insufficient free space on disk volume e:\ to
> > > > create the database.
> > > > >The database requires 16519462912 additional free bytes,
> > > > while only
> > > > >6329229312 bytes are available.
> > > > >RESTORE DATABASE is terminating abnormally.
> > > > >
> > > > >The database backup file is only 146M, the data file is
> > > > 143M and the log
> > > > >file is 15M.
> > > > >The data partition (e:) has 8G free space, although the
> > > > system/boot
> > > > >partition (c:) has about 2G
> > > > >
> > > > >Does anyone have any ideas how this could be happening?
> > > > >--
> > > > >regards,
> > > > >
> > > > >Paul Durdin
> > > > >
> > > > >
> > > > >.
> > > > >
> > >
> > >
> >
> >
>|||Sorted!!
Article 272318 says it all. Now have the log file shrunk and the backup
reflects a smaller size. I'll have to try restoring the backup on the target
machine on Monday, but this looks like it will have fixed the problem.
Thanks for your help,
--
regards,
Paul Durdin
"Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
news:OBrU7YsqDHA.3844@.tk2msftngp13.phx.gbl...
> Thanks for the suggestions.
> I've checked the backup file using RESTORE FILELISTONLY FROM
> FILE='backupfilename'
> This reports the log file as 16377380864 (where have I seem this figure
> before?) So I guess that explains why SQLSvr says it cant restore the
> database.
> I checked the log file size in EM to be 14,643M, but the physical log file
> is actually 14,993,664k.
> Being a newbie to SQL DBA stuff I am puzzled. How come the physical size
is
> different from the size recorded in EM?
> I did a bit of reading, and I am starting to get a bit of an
understanding,
> so I did a...
> DBCC SHRINKDATABASE (databasename)
> followed by
> BACKUP LOG databasename WITH TRUNCATE_ONLY
> Then did another backup and examined the backup as above. I get much the
> same figures as before.
> How can I shrink the log file (having already dome the above).
> --
> regards,
> Paul Durdin
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:e1HtntqqDHA.2588@.tk2msftngp13.phx.gbl...
> > When you restore a database, you need the same amount of space for the
> mdf,
> > ndf and ldf as the size those files had when you did the backup. If the
> > files were smaller when you did the backup and the restore claims you
need
> > more space, you have hit a bug in SQL Server (I haven't heard of such a
> bug,
> > though). A couple of things:
> >
> > Make sure that you restore the correct backup. One backup file can have
> more
> > than one backup. Check using RESTORE HEADERONLY.
> > Check the size needed according to the backup. Use RESTORE FILELISTONLY.
> > Make sure you specify the correct FILE = if the backup file has more
then
> > one backup.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at:
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> > "Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
> > news:%23Vrx9mqqDHA.2644@.TK2MSFTNGP09.phx.gbl...
> > > That's indeed what the error message says - but surely you telling me
> that
> > a
> > > 140M database needs 16G to restore it!
> > >
> > > --
> > > regards,
> > >
> > >
> > > "Jorge Lavado" <jorge.Lavado@.cgey.com_NO_SPAM> wrote in message
> > > news:0aab01c3aa9b$1255c6d0$a101280a@.phx.gbl...
> > > > Hi.
> > > > The data partition (e:) need + - 16 GB. free,you only have
> > > > + - 6 GB.
> > > >
> > > > >--Original Message--
> > > > >I am trying to move a database from one machine to
> > > > another by taking a
> > > > >backup from one and restoring it on another. Both
> > > > machines are W2k sp3 with
> > > > >SQL2k sp3. As far as I can tell they are both
> > > > straightforward, standard
> > > > >installations (OS and DB), except;
> > > > >The target machine has been partitioned into three
> > > > (system, apps, and data),
> > > > >and the disk is mirrored.
> > > > >
> > > > >I can take the backup and restore it to a number of
> > > > machines, but on the
> > > > >machine that I need to restore the database to I get;
> > > > >
> > > > >Microsoft SQL-DMO(ODBC SQL State: 42000)
> > > > >There is insufficient free space on disk volume e:\ to
> > > > create the database.
> > > > >The database requires 16519462912 additional free bytes,
> > > > while only
> > > > >6329229312 bytes are available.
> > > > >RESTORE DATABASE is terminating abnormally.
> > > > >
> > > > >The database backup file is only 146M, the data file is
> > > > 143M and the log
> > > > >file is 15M.
> > > > >The data partition (e:) has 8G free space, although the
> > > > system/boot
> > > > >partition (c:) has about 2G
> > > > >
> > > > >Does anyone have any ideas how this could be happening?
> > > > >--
> > > > >regards,
> > > > >
> > > > >Paul Durdin
> > > > >
> > > > >
> > > > >.
> > > > >
> > >
> > >
> >
> >
>|||I was looking in the database properties under Transaction Log->Space
allocated.
Doh! I think it was me - I took 15,xxx to be 15M but now the figure is 11(M)
so EM was reporting 15G (correctly).
It was me! It was me! I shall have to go on a re-education course / take up
a new career, or maybe pack up for the day and get ready to watch the rugby
over the weekend (its very weird watching rugby in the morning - it should
be an evening thing with plenty of beer).
--
regards,
Paul Durdin
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:eoivagsqDHA.2776@.tk2msftngp13.phx.gbl...
> Seems like EM reports the size incorrectly... Where in EM do you see that
> space reported? In the taskpad or right-click the database, properties?
> To shrink log, Check out below KB articles:
> INF: How to Shrink the SQL Server 7.0 Transaction Log
> http://support.microsoft.com/default.aspx?scid=kb;en-us;256650
> INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
> http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
> Log File Grows too big
> http://www.support.microsoft.com/?id=317375
> Log file filling up
> http://www.support.microsoft.com/?id=110139
> Considerations for Autogrow and AutoShrink
> http://www.support.microsoft.com/?id=315512
> http://www.mssqlserver.com/faq/logs-shrinklog.asp
>
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
> news:OBrU7YsqDHA.3844@.tk2msftngp13.phx.gbl...
> > Thanks for the suggestions.
> >
> > I've checked the backup file using RESTORE FILELISTONLY FROM
> > FILE='backupfilename'
> >
> > This reports the log file as 16377380864 (where have I seem this figure
> > before?) So I guess that explains why SQLSvr says it cant restore the
> > database.
> >
> > I checked the log file size in EM to be 14,643M, but the physical log
file
> > is actually 14,993,664k.
> >
> > Being a newbie to SQL DBA stuff I am puzzled. How come the physical size
> is
> > different from the size recorded in EM?
> >
> > I did a bit of reading, and I am starting to get a bit of an
> understanding,
> > so I did a...
> >
> > DBCC SHRINKDATABASE (databasename)
> > followed by
> > BACKUP LOG databasename WITH TRUNCATE_ONLY
> >
> > Then did another backup and examined the backup as above. I get much the
> > same figures as before.
> >
> > How can I shrink the log file (having already dome the above).
> >
> > --
> > regards,
> >
> > Paul Durdin
> >
> > "Tibor Karaszi"
> <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> > wrote in message news:e1HtntqqDHA.2588@.tk2msftngp13.phx.gbl...
> > > When you restore a database, you need the same amount of space for the
> > mdf,
> > > ndf and ldf as the size those files had when you did the backup. If
the
> > > files were smaller when you did the backup and the restore claims you
> need
> > > more space, you have hit a bug in SQL Server (I haven't heard of such
a
> > bug,
> > > though). A couple of things:
> > >
> > > Make sure that you restore the correct backup. One backup file can
have
> > more
> > > than one backup. Check using RESTORE HEADERONLY.
> > > Check the size needed according to the backup. Use RESTORE
FILELISTONLY.
> > > Make sure you specify the correct FILE = if the backup file has more
> then
> > > one backup.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > Archive at:
> > >
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> > >
> > >
> > > "Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
> > > news:%23Vrx9mqqDHA.2644@.TK2MSFTNGP09.phx.gbl...
> > > > That's indeed what the error message says - but surely you telling
me
> > that
> > > a
> > > > 140M database needs 16G to restore it!
> > > >
> > > > --
> > > > regards,
> > > >
> > > >
> > > > "Jorge Lavado" <jorge.Lavado@.cgey.com_NO_SPAM> wrote in message
> > > > news:0aab01c3aa9b$1255c6d0$a101280a@.phx.gbl...
> > > > > Hi.
> > > > > The data partition (e:) need + - 16 GB. free,you only have
> > > > > + - 6 GB.
> > > > >
> > > > > >--Original Message--
> > > > > >I am trying to move a database from one machine to
> > > > > another by taking a
> > > > > >backup from one and restoring it on another. Both
> > > > > machines are W2k sp3 with
> > > > > >SQL2k sp3. As far as I can tell they are both
> > > > > straightforward, standard
> > > > > >installations (OS and DB), except;
> > > > > >The target machine has been partitioned into three
> > > > > (system, apps, and data),
> > > > > >and the disk is mirrored.
> > > > > >
> > > > > >I can take the backup and restore it to a number of
> > > > > machines, but on the
> > > > > >machine that I need to restore the database to I get;
> > > > > >
> > > > > >Microsoft SQL-DMO(ODBC SQL State: 42000)
> > > > > >There is insufficient free space on disk volume e:\ to
> > > > > create the database.
> > > > > >The database requires 16519462912 additional free bytes,
> > > > > while only
> > > > > >6329229312 bytes are available.
> > > > > >RESTORE DATABASE is terminating abnormally.
> > > > > >
> > > > > >The database backup file is only 146M, the data file is
> > > > > 143M and the log
> > > > > >file is 15M.
> > > > > >The data partition (e:) has 8G free space, although the
> > > > > system/boot
> > > > > >partition (c:) has about 2G
> > > > > >
> > > > > >Does anyone have any ideas how this could be happening?
> > > > > >--
> > > > > >regards,
> > > > > >
> > > > > >Paul Durdin
> > > > > >
> > > > > >
> > > > > >.
> > > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||> It was me! It was me! I shall have to go on a re-education course / take
up
> a new career, or maybe pack up for the day and get ready to watch the
rugby
> over the weekend (its very weird watching rugby in the morning - it should
> be an evening thing with plenty of beer).
LOL! :-) We all do this from time to time. One tip: IF contradictions, trust
the engine, as the tools might have bugs in them. This wasn't such a case,
but could have been .
Well, here, we have to go to a sportsbar to watch the rugby. In the
morning...
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
news:%2336PHpsqDHA.1960@.TK2MSFTNGP12.phx.gbl...
> I was looking in the database properties under Transaction Log->Space
> allocated.
> Doh! I think it was me - I took 15,xxx to be 15M but now the figure is
11(M)
> so EM was reporting 15G (correctly).
> It was me! It was me! I shall have to go on a re-education course / take
up
> a new career, or maybe pack up for the day and get ready to watch the
rugby
> over the weekend (its very weird watching rugby in the morning - it should
> be an evening thing with plenty of beer).
> --
> regards,
> Paul Durdin
>
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:eoivagsqDHA.2776@.tk2msftngp13.phx.gbl...
> > Seems like EM reports the size incorrectly... Where in EM do you see
that
> > space reported? In the taskpad or right-click the database, properties?
> >
> > To shrink log, Check out below KB articles:
> >
> > INF: How to Shrink the SQL Server 7.0 Transaction Log
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;256650
> >
> > INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC
SHRINKFILE
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
> >
> > Log File Grows too big
> > http://www.support.microsoft.com/?id=317375
> >
> > Log file filling up
> > http://www.support.microsoft.com/?id=110139
> >
> > Considerations for Autogrow and AutoShrink
> > http://www.support.microsoft.com/?id=315512
> >
> > http://www.mssqlserver.com/faq/logs-shrinklog.asp
> >
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at:
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> > "Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
> > news:OBrU7YsqDHA.3844@.tk2msftngp13.phx.gbl...
> > > Thanks for the suggestions.
> > >
> > > I've checked the backup file using RESTORE FILELISTONLY FROM
> > > FILE='backupfilename'
> > >
> > > This reports the log file as 16377380864 (where have I seem this
figure
> > > before?) So I guess that explains why SQLSvr says it cant restore the
> > > database.
> > >
> > > I checked the log file size in EM to be 14,643M, but the physical log
> file
> > > is actually 14,993,664k.
> > >
> > > Being a newbie to SQL DBA stuff I am puzzled. How come the physical
size
> > is
> > > different from the size recorded in EM?
> > >
> > > I did a bit of reading, and I am starting to get a bit of an
> > understanding,
> > > so I did a...
> > >
> > > DBCC SHRINKDATABASE (databasename)
> > > followed by
> > > BACKUP LOG databasename WITH TRUNCATE_ONLY
> > >
> > > Then did another backup and examined the backup as above. I get much
the
> > > same figures as before.
> > >
> > > How can I shrink the log file (having already dome the above).
> > >
> > > --
> > > regards,
> > >
> > > Paul Durdin
> > >
> > > "Tibor Karaszi"
> > <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> > > wrote in message news:e1HtntqqDHA.2588@.tk2msftngp13.phx.gbl...
> > > > When you restore a database, you need the same amount of space for
the
> > > mdf,
> > > > ndf and ldf as the size those files had when you did the backup. If
> the
> > > > files were smaller when you did the backup and the restore claims
you
> > need
> > > > more space, you have hit a bug in SQL Server (I haven't heard of
such
> a
> > > bug,
> > > > though). A couple of things:
> > > >
> > > > Make sure that you restore the correct backup. One backup file can
> have
> > > more
> > > > than one backup. Check using RESTORE HEADERONLY.
> > > > Check the size needed according to the backup. Use RESTORE
> FILELISTONLY.
> > > > Make sure you specify the correct FILE = if the backup file has
more
> > then
> > > > one backup.
> > > >
> > > > --
> > > > Tibor Karaszi, SQL Server MVP
> > > > Archive at:
> > > >
> > >
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> > > >
> > > >
> > > > "Paul Durdin" <pdurdin@.nospam_hotmail.com> wrote in message
> > > > news:%23Vrx9mqqDHA.2644@.TK2MSFTNGP09.phx.gbl...
> > > > > That's indeed what the error message says - but surely you telling
> me
> > > that
> > > > a
> > > > > 140M database needs 16G to restore it!
> > > > >
> > > > > --
> > > > > regards,
> > > > >
> > > > >
> > > > > "Jorge Lavado" <jorge.Lavado@.cgey.com_NO_SPAM> wrote in message
> > > > > news:0aab01c3aa9b$1255c6d0$a101280a@.phx.gbl...
> > > > > > Hi.
> > > > > > The data partition (e:) need + - 16 GB. free,you only have
> > > > > > + - 6 GB.
> > > > > >
> > > > > > >--Original Message--
> > > > > > >I am trying to move a database from one machine to
> > > > > > another by taking a
> > > > > > >backup from one and restoring it on another. Both
> > > > > > machines are W2k sp3 with
> > > > > > >SQL2k sp3. As far as I can tell they are both
> > > > > > straightforward, standard
> > > > > > >installations (OS and DB), except;
> > > > > > >The target machine has been partitioned into three
> > > > > > (system, apps, and data),
> > > > > > >and the disk is mirrored.
> > > > > > >
> > > > > > >I can take the backup and restore it to a number of
> > > > > > machines, but on the
> > > > > > >machine that I need to restore the database to I get;
> > > > > > >
> > > > > > >Microsoft SQL-DMO(ODBC SQL State: 42000)
> > > > > > >There is insufficient free space on disk volume e:\ to
> > > > > > create the database.
> > > > > > >The database requires 16519462912 additional free bytes,
> > > > > > while only
> > > > > > >6329229312 bytes are available.
> > > > > > >RESTORE DATABASE is terminating abnormally.
> > > > > > >
> > > > > > >The database backup file is only 146M, the data file is
> > > > > > 143M and the log
> > > > > > >file is 15M.
> > > > > > >The data partition (e:) has 8G free space, although the
> > > > > > system/boot
> > > > > > >partition (c:) has about 2G
> > > > > > >
> > > > > > >Does anyone have any ideas how this could be happening?
> > > > > > >--
> > > > > > >regards,
> > > > > > >
> > > > > > >Paul Durdin
> > > > > > >
> > > > > > >
> > > > > > >.
> > > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts
Thursday, March 29, 2012
Error Reporting: Installation on SQL 2005 on x64
I installed SQL 2005 on x64 machine and notice that my Y: drive (data drive) has these additional directories (shown below). I know those files are components of “Microsoft Application Error Reporting”. They are shared among multiple applications, hence them being in “common files”. After disabling the error reporting using Microsoft SQL Server 2005->Configuration Tools->Error and Usage Reporting, can I get rid of those directories or specify which directory that it should go to? Has anyone seen this before? Thanks.
The following had been installed to the drive that we did not specify in the installation of SQL 2005. Is there any way to redirect these file back the window directory?
Volume in drive Y is New Volume
Volume Serial Number is 882B-9F43
NULL
Directory of y:\program files\common files\microsoft shared\dw
NULL
06/01/2006 11:26 AM <DIR> .
06/01/2006 11:26 AM <DIR> ..
06/01/2006 11:26 AM <DIR> 1028
06/01/2006 11:26 AM <DIR> 1031
06/01/2006 11:26 AM <DIR> 1033
06/01/2006 11:26 AM <DIR> 1036
06/01/2006 11:26 AM <DIR> 1040
06/01/2006 11:26 AM <DIR> 1041
06/01/2006 11:26 AM <DIR> 1042
06/01/2006 11:26 AM <DIR> 2052
06/01/2006 11:26 AM <DIR> 3082
04/25/2005 01:44 PM 1,030,336 DW20.EXE
04/25/2005 01:44 PM 496,328 DWDCW20.DLL
04/25/2005 01:44 PM 489,672 DWTRIG20.EXE
3 File(s) 2,016,336 bytes
11 Dir(s) 85,983,068,160 bytes free
NULL
Monday, March 26, 2012
Error opening Management Studio (Express)
Hello all,
I'm having an error opening the SSMS Express on a machine. This is a new install on this machine, so i've never had this running. However, i've install SSMSE many times and this is the first error that I've come across. I have the minimum requirements on the machine (Framework, XML, Windows Installer)
The error is:
Header: "Microsoft .Net Framework"
"Unhandled exception has occured in a component in your application. If you click Continue, the application will igonore this error and attempt to continue.
Attempted to read or write protected memory. This is often an indication that the other memory is corrupt"
(Details at end of post)
Now what this machine is running is:
OS: SBS 2003 SP1
Memory: 1.5 GB (over 1 GB is free)
Hard Disk: 7 GB of free space
Windows Updates are done up to just before SP2
SQL Server Express (SP2) is installed on this machine.
SSMSE Version: 3042
What I've done trying to resolve this issue:
1) reboot the machine
2) apply remaining windows updates (save for W2K3 SP2)
3) Re-install of SSMSE
4) Re-download of SSMSE install package and an uninstall & reinstall
5) Repair of .Net Framework 2.0
6) Repair of SQL Native Client
I'm not sure what to attempt next, if anyone can give me any insite at all, that would be great. All I did was install the requirements, install SQL Server Express SP2, then install SSMSE. This has worked in the past for me.
Any and all help greatly appreciated!!
Thanks,
Ryan
Note: here is the stack track that the application generates:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.GdipGetLogFontW(HandleRef font, HandleRef graphics, Object lf)
at System.Drawing.Font.ToLogFont(Object logFont, Graphics graphics)
at System.Drawing.Font.ToLogFont(Object logFont)
at System.Drawing.Font.ToHfont()
at System.Windows.Forms.Control.FontHandleWrapper..ctor(Font font)
at System.Windows.Forms.Control.get_FontHandle()
at System.Windows.Forms.Control.SetWindowFont()
at System.Windows.Forms.Control.OnHandleCreated(EventArgs e)
at System.Windows.Forms.TreeView.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
Microsoft.SqlServer.Express.AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.AppIDPackage.DLL
-
Microsoft.SqlServer.Express.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.VSIntegration.DLL
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
-
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
Microsoft.SqlServer.Express.SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlWorkbench.Interfaces.DLL
-
Microsoft.SqlServer.Express.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlTDiagM.DLL
-
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
-
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
-
Microsoft.SqlServer.Express.ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ObjectExplorer.DLL
-
Microsoft.SqlServer.Express.SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlMgmt.DLL
-
Microsoft.SqlServer.Express.ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ConnectionDlg.DLL
-
Microsoft.VisualStudio
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 built by: RTM
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.dll
-
Microsoft.VisualStudio.Shell
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.dll
-
Microsoft.VisualStudio.Shell.Interop.8.0
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.8.0.dll
-
System.Drawing.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
-
Microsoft.VisualStudio.Designer.Interfaces
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Designer.Interfaces/1.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Designer.Interfaces.dll
-
Microsoft.SqlServer.Express.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.RegSvrEnum.DLL
-
Microsoft.SqlServer.Express.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.CustomControls.DLL
-
Microsoft.SqlServer.Express.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.Smo.DLL
-
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
-
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
--
**********************************************************************************************
--
To me that looks like a problem with the .NET framework. Try doing a full reinstall of the framework.
You might want to ask in one of the .NET forums and see if they can shead any light.
|||That's what I thought too, so I ended up uninstalling the framework, rebooting, and reinstalling. No issues on the reinstall.
Still the error exists. However, I have found that I get errors in the SQL Surface Area Configuration Wizard as well. I'm assuming this runs off the ".NET Framework" as well. I've read some issues with this happening with some .NET controls, but I'm assuming that these are working fine as this seems to be the only machine with these issues. What concerns me is that if SQL Server uses any of hte .NET framework (besides the CLR) then I'm not sure if I want to continue on this machine.
Any ideas on what do look for?
|||Ok, i'm convinced that this is an issue with .NET framework on this machine. It seems to be related to the System.Drawing DLL. I can get into the program but, it'll throw another error if I right click, however, this error comes from System.Drawing.Font
I'm going to move this thread to under a .NET Thread.
Thanks,
|||Moved to:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1
|||
Ryan Slimmon wrote:
Moved to:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1
Any update on this issue - I am getting same message when trying to import SQL 2000 Server registration details
Error opening Management Studio (Express)
Hello all,
I'm having an error opening the SSMS Express on a machine. This is a new install on this machine, so i've never had this running. However, i've install SSMSE many times and this is the first error that I've come across. I have the minimum requirements on the machine (Framework, XML, Windows Installer)
The error is:
Header: "Microsoft .Net Framework"
"Unhandled exception has occured in a component in your application. If you click Continue, the application will igonore this error and attempt to continue.
Attempted to read or write protected memory. This is often an indication that the other memory is corrupt"
(Details at end of post)
Now what this machine is running is:
OS: SBS 2003 SP1
Memory: 1.5 GB (over 1 GB is free)
Hard Disk: 7 GB of free space
Windows Updates are done up to just before SP2
SQL Server Express (SP2) is installed on this machine.
SSMSE Version: 3042
What I've done trying to resolve this issue:
1) reboot the machine
2) apply remaining windows updates (save for W2K3 SP2)
3) Re-install of SSMSE
4) Re-download of SSMSE install package and an uninstall & reinstall
5) Repair of .Net Framework 2.0
6) Repair of SQL Native Client
I'm not sure what to attempt next, if anyone can give me any insite at all, that would be great. All I did was install the requirements, install SQL Server Express SP2, then install SSMSE. This has worked in the past for me.
Any and all help greatly appreciated!!
Thanks,
Ryan
Note: here is the stack track that the application generates:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.GdipGetLogFontW(HandleRef font, HandleRef graphics, Object lf)
at System.Drawing.Font.ToLogFont(Object logFont, Graphics graphics)
at System.Drawing.Font.ToLogFont(Object logFont)
at System.Drawing.Font.ToHfont()
at System.Windows.Forms.Control.FontHandleWrapper..ctor(Font font)
at System.Windows.Forms.Control.get_FontHandle()
at System.Windows.Forms.Control.SetWindowFont()
at System.Windows.Forms.Control.OnHandleCreated(EventArgs e)
at System.Windows.Forms.TreeView.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
Microsoft.SqlServer.Express.AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.AppIDPackage.DLL
-
Microsoft.SqlServer.Express.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.VSIntegration.DLL
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
-
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
Microsoft.SqlServer.Express.SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlWorkbench.Interfaces.DLL
-
Microsoft.SqlServer.Express.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlTDiagM.DLL
-
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
-
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
-
Microsoft.SqlServer.Express.ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ObjectExplorer.DLL
-
Microsoft.SqlServer.Express.SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlMgmt.DLL
-
Microsoft.SqlServer.Express.ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ConnectionDlg.DLL
-
Microsoft.VisualStudio
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 built by: RTM
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.dll
-
Microsoft.VisualStudio.Shell
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.dll
-
Microsoft.VisualStudio.Shell.Interop.8.0
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.8.0.dll
-
System.Drawing.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
-
Microsoft.VisualStudio.Designer.Interfaces
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Designer.Interfaces/1.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Designer.Interfaces.dll
-
Microsoft.SqlServer.Express.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.RegSvrEnum.DLL
-
Microsoft.SqlServer.Express.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.CustomControls.DLL
-
Microsoft.SqlServer.Express.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.Smo.DLL
-
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
-
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
--
**********************************************************************************************
--
To me that looks like a problem with the .NET framework. Try doing a full reinstall of the framework.
You might want to ask in one of the .NET forums and see if they can shead any light.
|||That's what I thought too, so I ended up uninstalling the framework, rebooting, and reinstalling. No issues on the reinstall.
Still the error exists. However, I have found that I get errors in the SQL Surface Area Configuration Wizard as well. I'm assuming this runs off the ".NET Framework" as well. I've read some issues with this happening with some .NET controls, but I'm assuming that these are working fine as this seems to be the only machine with these issues. What concerns me is that if SQL Server uses any of hte .NET framework (besides the CLR) then I'm not sure if I want to continue on this machine.
Any ideas on what do look for?
|||Ok, i'm convinced that this is an issue with .NET framework on this machine. It seems to be related to the System.Drawing DLL. I can get into the program but, it'll throw another error if I right click, however, this error comes from System.Drawing.Font
I'm going to move this thread to under a .NET Thread.
Thanks,
|||Moved to:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1
|||
Moved to:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1
Any update on this issue - I am getting same message when trying to import SQL 2000 Server registration details
sqlWednesday, March 21, 2012
error on one machine and working on another
Dear sir this is a typical problem i am facing.
We have 4 web servers in out establishment.
this code works on some and does not work on some.
in all servers i have installed crystal reports the same way.
the database server is a separate server.
please help.
i must deploy this web page and the report on the one of the 2 servers( both hcl machines) allotted to me. the other 2 on which this code is working are ibm machines but i cannot deploy on them.
Error Type:
webReporting.dll (0x8004100F)
Logon failed. Details: ADO Error Code: 0x80040e21 Source: Provider Description: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. Native Error: -2147217887 Error in File C:\WINNT\TEMP\{A687C3B5-8F52-40E2-9433-C2FF1D56D225}.rpt: Unable to connect: incorrect log on parameters.
/stores_crystal/expendable.asp, line 72
<%@. Language=VBScript %>
<!--#include file="connections.asp"-->
<!--#include file="userdate.asp"-->
<!--#include file="checkscriptfordatatype.asp"-->
<HTML>
<HEAD>
<META NAME="GENERATOR" Content="Microsoft Visual Studio 6.0">
</HEAD>
<BODY>
<center>
<form name=expendable method=post>
<%if request.form("dummy")="" then
set rs=server.CreateObject ("adodb.recordset")
q="sELECT item_code,item from exp_binmst order by item"
rs.Open q,conn_inventory
%>ITEM<select size=10 multiple name=eitem>
<%while not rs.eof
v="'"&rs(0)&"'"%>
<option value="<%=v%>"><%=rs(1)%></option>
<%rs.movenext
wend%>
</select>
<BR><BR><BR><BR><BR>From Date<%call urdate("mustbox-date/from date","from_date",date)%>
No From Date??<input type=checkbox name=No_From_date >
To Date<%call urdate("mustbox-date/to date","to_date",date)
%>
<BR><BR><BR><input type=submit value=show><input name=dummy value=dummy type=hidden>
<%else
dim objectfactory,htmlviewer,conInfo,coninfos
set objectfactory=createobject("crystalreports.objectfactory.2")
set htmlviewer=createobject("crystalreports.crystalreportviewer")
set conInfos=createobject("crystalreports.ConnectionInfos")
set conInfo=createobject("crystalreports.ConnectionInfo")
conInfo.UserName="sa"
conInfo.Password="3blind"
conInfos.Add(conInfo)
if Request.Form("no_from_date")="on" then
q="{Command.item_code} in ["&request.form("eitem")&"] and {Command.bin_dt} <=cdate('"&cdate(Request.Form("to_Date"))&"')"
else
q="{Command.item_code} in ["&request.form("eitem")&"] and {Command.bin_dt} >=cdate('"&cdate(request.form("from_Date"))&"') and {Command.bin_dt} <=cdate('"&cdate(Request.Form("to_Date"))&"')"
end if
with htmlviewer
.HasCrystalLogo=false
.HasExportButton=false
.HasGotoPageButton=false
.HasPageNavigationButtons=false
.HasPrintButton=false
.HasRefreshButton=false
.HasSearchButton=false
.HasToggleGroupTreeButton=false
.HasViewList=false
.HasZoomFactorList=false
.IsOwnForm=true
.IsOwnPage=true
.pageToTreeRatio=100
.ReportSource="expendable.rpt"
.EnableLogonPrompt=false
.DatabaseLogonInfos=conInfos
.SelectionFormula=q
end with
call htmlviewer.ProcessHttpRequest(request,Response,session)
'''' line no 72
end if%>
</BODY>
</HTML>
:(I encountered the same problem a couple of days before, it made me very hard to fix that, I found none solution provided on the line, finally I got the solution :
Just using ODBC connection instead of OLEDB.
Because the crystal versioning is very picky.
We have 4 web servers in out establishment.
this code works on some and does not work on some.
in all servers i have installed crystal reports the same way.
the database server is a separate server.
please help.
i must deploy this web page and the report on the one of the 2 servers( both hcl machines) allotted to me. the other 2 on which this code is working are ibm machines but i cannot deploy on them.
Error Type:
webReporting.dll (0x8004100F)
Logon failed. Details: ADO Error Code: 0x80040e21 Source: Provider Description: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. Native Error: -2147217887 Error in File C:\WINNT\TEMP\{A687C3B5-8F52-40E2-9433-C2FF1D56D225}.rpt: Unable to connect: incorrect log on parameters.
/stores_crystal/expendable.asp, line 72
<%@. Language=VBScript %>
<!--#include file="connections.asp"-->
<!--#include file="userdate.asp"-->
<!--#include file="checkscriptfordatatype.asp"-->
<HTML>
<HEAD>
<META NAME="GENERATOR" Content="Microsoft Visual Studio 6.0">
</HEAD>
<BODY>
<center>
<form name=expendable method=post>
<%if request.form("dummy")="" then
set rs=server.CreateObject ("adodb.recordset")
q="sELECT item_code,item from exp_binmst order by item"
rs.Open q,conn_inventory
%>ITEM<select size=10 multiple name=eitem>
<%while not rs.eof
v="'"&rs(0)&"'"%>
<option value="<%=v%>"><%=rs(1)%></option>
<%rs.movenext
wend%>
</select>
<BR><BR><BR><BR><BR>From Date<%call urdate("mustbox-date/from date","from_date",date)%>
No From Date??<input type=checkbox name=No_From_date >
To Date<%call urdate("mustbox-date/to date","to_date",date)
%>
<BR><BR><BR><input type=submit value=show><input name=dummy value=dummy type=hidden>
<%else
dim objectfactory,htmlviewer,conInfo,coninfos
set objectfactory=createobject("crystalreports.objectfactory.2")
set htmlviewer=createobject("crystalreports.crystalreportviewer")
set conInfos=createobject("crystalreports.ConnectionInfos")
set conInfo=createobject("crystalreports.ConnectionInfo")
conInfo.UserName="sa"
conInfo.Password="3blind"
conInfos.Add(conInfo)
if Request.Form("no_from_date")="on" then
q="{Command.item_code} in ["&request.form("eitem")&"] and {Command.bin_dt} <=cdate('"&cdate(Request.Form("to_Date"))&"')"
else
q="{Command.item_code} in ["&request.form("eitem")&"] and {Command.bin_dt} >=cdate('"&cdate(request.form("from_Date"))&"') and {Command.bin_dt} <=cdate('"&cdate(Request.Form("to_Date"))&"')"
end if
with htmlviewer
.HasCrystalLogo=false
.HasExportButton=false
.HasGotoPageButton=false
.HasPageNavigationButtons=false
.HasPrintButton=false
.HasRefreshButton=false
.HasSearchButton=false
.HasToggleGroupTreeButton=false
.HasViewList=false
.HasZoomFactorList=false
.IsOwnForm=true
.IsOwnPage=true
.pageToTreeRatio=100
.ReportSource="expendable.rpt"
.EnableLogonPrompt=false
.DatabaseLogonInfos=conInfos
.SelectionFormula=q
end with
call htmlviewer.ProcessHttpRequest(request,Response,session)
'''' line no 72
end if%>
</BODY>
</HTML>
:(I encountered the same problem a couple of days before, it made me very hard to fix that, I found none solution provided on the line, finally I got the solution :
Just using ODBC connection instead of OLEDB.
Because the crystal versioning is very picky.
error on installing sql express 2005
I'm having trouble loging into sql...then I remebered when I first installed it on my XP pro machine the system config check showed everything passed except the following:
System Configuration Check
-
- COM Plus Catalog Requirement (Warning)
Messages
COM Plus Catalog Requirement
If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.
- Can this be the reason I cannot log into sql ?
Did you resolve this issue?error on installing sql express 2005
I'm having trouble loging into sql...then I remebered when I first installed it on my XP pro machine the system config check showed everything passed except the following:
System Configuration Check
-
- COM Plus Catalog Requirement (Warning)
Messages
COM Plus Catalog Requirement
If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.
- Can this be the reason I cannot log into sql ?
Did you resolve this issue?sqlError on Executing SSIS packages on a remote machine using code
Hello all,
I am trying to execute the ssis packages using code.These packages are hosted on remote server under MSDB in local Network.
Below is the code tried to Execute
--
DTSExecResult execRslt = _dtsxPackage.Execute();
foreach (DtsError dtserr in _dtsxPackage.Errors)
{
Console.WriteLine("Source: " + dtserr.Source + ", Description: " + dtserr.Description);
}
I get hte following Error
--
"Dupaco Load MMAs"-"An OLE DB error has occurred. Error code: 0x80004005.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80004005 Description: \"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.\".\r\n"
"Data Flow Task" -"The AcquireConnection method call to the connection manager \"Dupaco\" failed with error code 0xC0202009.\r\n"
"Data Flow Task" -"component \"OLE DB Destination\" (119) failed validation and returned error code 0xC020801C.\r\n"
"One or more component failed validation.\r\n"
"There were errors during task validation.\r\n"
When i try to execute the same code on the server where all the package are hosted. It is working fine.
More Info:
In thepackage we are using one "Source Flat file connection" and one "Oledb Destination connection"
Please help me to solve this problem, as my client needs it very badly
Thanks
Subin
"Dupaco Load MMAs"-"An OLE DB error has occurred. Error code: 0x80004005.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80004005 Description: \"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.\".\r\n"
The problem appears to be that whatever address or alias was used to create the OLE DB connection can't be resolved from where the package is executing. Maybe it was set up using (local) or something. Maybe the server doesn't allow TCP/IP connections (the default for SQL Server 2005).
|||
Hi Jay,
Earlier We were using sql server name now we have changes that to IP address,
we have saved the password in the "Oledb Destination connection" by checking in the checkbox to save the password.
now we are getting the following Error
"An OLE DB error has occurred. Error code: 0x80040E4D.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80040E4D Description: \"Login failed for user 'sa'.\".\r\n"
|||
"An OLE DB error has occurred. Error code: 0x80040E4D.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80040E4D Description: \"Login failed for user 'sa'.\".\r\n"
I've already answered that one today, so all you get is a link.
See if this helps.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1453667&SiteID=1
|||
"An OLE DB error has occurred. Error code: 0x80040E4D.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80040E4D Description: \"Login failed for user 'sa'.\".\r\n"
Are you intending to be logging in as the user 'sa'?|||
Hello all,
I am trying to execute the ssis packages using code.These packages are hosted on remote server under MSDB in local Network.
...
To clarify possible confusion: you are not executing the package on a remote machine (as the title of your question suggests).
You are loading package from a remote machine and running it locally (where your application runs).
http://blogs.msdn.com/michen/archive/2006/08/11/package-exec-location.aspx
Michael.
|||Hello Michael,
You are absolutely correct. Sorry for confusion.
I am not executing the package on a remote machine (as the title of question suggests),loading package from a remote machine and running it locally (where my application runs).
Thanks
Subin
|||Hello All,
Thank you all for help.
I have solved the problem.
The package which i had tried to execute was a password protected package and I was not setting the PackagePassword property of Application class before loading package from remote machine. So that the loaded package does not have sensitive information. That was the problem.
Application app = new Application();
app.PackagePassword = "test";
Package package = app.LoadFromSqlServer(@."PackTest", "Circle-DotNet57", "ssisdeveloper", "circle_123", null);
//package.ProtectionLevel = DTSProtectionLevel.EncryptSensitiveWithPassword;
//package.PackagePassword = "test";
DTSExecResult result = package.Execute();
Thank you
Subin
Error on Executing SSIS packages on a remote machine using code
Hello all,
I am trying to execute the ssis packages using code.These packages are hosted on remote server under MSDB in local Network.
Below is the code tried to Execute
--
DTSExecResult execRslt = _dtsxPackage.Execute();
foreach (DtsError dtserr in _dtsxPackage.Errors)
{
Console.WriteLine("Source: " + dtserr.Source + ", Description: " + dtserr.Description);
}
I get hte following Error
--
"Dupaco Load MMAs"-"An OLE DB error has occurred. Error code: 0x80004005.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80004005 Description: \"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.\".\r\n"
"Data Flow Task" -"The AcquireConnection method call to the connection manager \"Dupaco\" failed with error code 0xC0202009.\r\n"
"Data Flow Task" -"component \"OLE DB Destination\" (119) failed validation and returned error code 0xC020801C.\r\n"
"One or more component failed validation.\r\n"
"There were errors during task validation.\r\n"
When i try to execute the same code on the server where all the package are hosted. It is working fine.
More Info:
In thepackage we are using one "Source Flat file connection" and one "Oledb Destination connection"
Please help me to solve this problem, as my client needs it very badly
Thanks
Subin
"Dupaco Load MMAs"-"An OLE DB error has occurred. Error code: 0x80004005.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80004005 Description: \"[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.\".\r\n"
The problem appears to be that whatever address or alias was used to create the OLE DB connection can't be resolved from where the package is executing. Maybe it was set up using (local) or something. Maybe the server doesn't allow TCP/IP connections (the default for SQL Server 2005).
|||
Hi Jay,
Earlier We were using sql server name now we have changes that to IP address,
we have saved the password in the "Oledb Destination connection" by checking in the checkbox to save the password.
now we are getting the following Error
"An OLE DB error has occurred. Error code: 0x80040E4D.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80040E4D Description: \"Login failed for user 'sa'.\".\r\n"
|||
"An OLE DB error has occurred. Error code: 0x80040E4D.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80040E4D Description: \"Login failed for user 'sa'.\".\r\n"
I've already answered that one today, so all you get is a link.
See if this helps.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1453667&SiteID=1
|||
"An OLE DB error has occurred. Error code: 0x80040E4D.\r\nAn OLE DB record is available. Source: \"Microsoft OLE DB Provider for SQL Server\" Hresult: 0x80040E4D Description: \"Login failed for user 'sa'.\".\r\n"
Are you intending to be logging in as the user 'sa'?|||
Hello all,
I am trying to execute the ssis packages using code.These packages are hosted on remote server under MSDB in local Network.
...
To clarify possible confusion: you are not executing the package on a remote machine (as the title of your question suggests).
You are loading package from a remote machine and running it locally (where your application runs).
http://blogs.msdn.com/michen/archive/2006/08/11/package-exec-location.aspx
Michael.
|||Hello Michael,
You are absolutely correct. Sorry for confusion.
I am not executing the package on a remote machine (as the title of question suggests),loading package from a remote machine and running it locally (where my application runs).
Thanks
Subin
|||Hello All,
Thank you all for help.
I have solved the problem.
The package which i had tried to execute was a password protected package and I was not setting the PackagePassword property of Application class before loading package from remote machine. So that the loaded package does not have sensitive information. That was the problem.
Application app = new Application();
app.PackagePassword = "test";
Package package = app.LoadFromSqlServer(@."PackTest", "Circle-DotNet57", "ssisdeveloper", "circle_123", null);
//package.ProtectionLevel = DTSProtectionLevel.EncryptSensitiveWithPassword;
//package.PackagePassword = "test";
DTSExecResult result = package.Execute();
Thank you
Subin
Friday, March 9, 2012
Error Msg 8120
Hello all,
I am using SQL Server 2005 Express on my local machine and am having a hard time figuring out why this problem is occuring. I am creating a stored procedure just fyi. 8120 = Column 's.Spread' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause. And also...Column 's.Pay End Dt' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause.
Both of these fields are being used in an expression not actually pulled into the query. I have bolded the line that the error refers to...Here is the sql:
USE ForecastSQLDBA
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE PROCEDURE GetHistoricalData
@.AccountName varchar(50),
@.MaxDate smalldatetime
AS
BEGIN
SELECTDivision,
SUM(CASE WHEN [Pay End Dt] BETWEEN '2005-01-01' AND '2005-12-31' THEN Spread ELSE 0 END) AS [05Spread],
SUM(CASE WHEN [Pay End Dt] BETWEEN '2006-01-01' AND '2006-12-31' THEN Spread ELSE 0 END) AS [06Spread],
SUM(CASE WHEN [Pay End Dt] BETWEEN '2005-01-01' AND '2005-12-31' THEN [Bill] ELSE 0 END)/SUM(CASE WHEN [Pay End Dt] BETWEEN '2005-01-01' AND '2005-12-31' THEN [Cost] ELSE 0 END) AS [05MarkUp],
SUM(CASE WHEN [Pay End Dt] BETWEEN '2006-01-01' AND '2006-12-31' THEN [Bill] ELSE 0 END)/SUM(CASE WHEN [Pay End Dt] BETWEEN '2006-01-01' AND '2006-12-31' THEN [Cost] ELSE 0 END) AS [06MarkUp],
SUM(CASE WHEN [Pay End Dt] BETWEEN '2007-01-01' AND @.maxdate THEN [Bill] ELSE 0 END)/SUM(CASE WHEN [Pay End Dt] BETWEEN '2007-01-01' AND @.maxdate THEN [Cost] ELSE 0 END) AS [07MarkUp],
SUM(CASE WHEN [Pay End Dt] BETWEEN '2005-01-01' AND '2005-12-31' THEN Spread ELSE 0 END)/SUM(CASE WHEN [Pay End Dt] BETWEEN '2005-01-01' AND '2005-12-31' THEN [Emp] ELSE 0 END) AS [05SPC],
SUM(CASE WHEN [Pay End Dt] BETWEEN '2006-01-01' AND '2006-12-31' THEN Spread ELSE 0 END)/SUM(CASE WHEN [Pay End Dt] BETWEEN '2006-01-01' AND '2006-12-31' THEN [Emp] ELSE 0 END) AS [06SPC],
SUM(CASE WHEN [Pay End Dt] BETWEEN '2007-01-01' AND @.maxdate THEN Spread ELSE 0 END)/SUM(CASE WHEN [Pay End Dt] BETWEEN '2007-01-01' AND @.maxdate THEN [Emp] ELSE 0 END) AS [07SPC],
SUM(CASE WHEN [Pay End Dt] = @.maxdate THEN [Bill] ELSE 0 END)/SUM(CASE [Pay End Dt] WHEN @.maxdate THEN [Cost] ELSE 0 END) AS [07CurMarkUp],
AVG(CASE WHEN [Pay End Dt] BETWEEN '2005-01-01' AND '2005-12-31' THEN [Emp] ELSE 0 END) AS [05AvgEmp],
AVG(CASE WHEN [Pay End Dt] BETWEEN '2006-01-01' AND '2006-12-31' THEN [Emp] ELSE 0 END) AS [06AvgEmp],
AVG(CASE WHEN [Pay End Dt] BETWEEN '2007-01-01' AND @.maxdate THEN [Emp] ELSE 0 END) AS [07AvgEmp],
MAX(CASE WHEN [Pay End Dt] BETWEEN '2005-01-01' AND '2005-12-31' THEN [Spread] ELSE 0 END) AS [05High],
MAX(CASE WHEN [Pay End Dt] BETWEEN '2006-01-01' AND '2006-12-31' THEN Spread ELSE 0 END) AS [06High],
MAX(CASE WHEN [Pay End Dt] BETWEEN '2007-01-01' AND @.maxdate THEN Spread ELSE 0 END) AS [07High],
CASE Spread WHEN MAX(CASE WHEN [Pay End Dt] BETWEEN '2005-01-01' AND '2005-12-31' THEN Spread ELSE 0 END) THEN [Pay End Dt] ELSE '' END AS [05MaxWeek],
CASE Spread WHEN MAX(CASE WHEN [Pay End Dt] BETWEEN '2006-01-01' AND '2006-12-31' THEN Spread ELSE 0 END) THEN [Pay End Dt] ELSE '' END AS [06MaxWeek],
CASE Spread WHEN MAX(CASE WHEN [Pay End Dt] BETWEEN '2007-01-01' AND @.maxdate THEN Spread ELSE 0 END) THEN [Pay End Dt] ELSE '' END AS [05MaxWeek]
FROM (SELECT Division, [Pay End Dt], Sum(isnull([SumOfNum of Emp],0)) AS Emp, SUM(isnull([SumOfNet Spread],0)) AS Spread, SUM(isnull([SumOfTotal Bill],0)) AS Bill, SUM(isnull([SumOfCost],0)) AS Cost FROM dbo.tbl_NAHistory WHERE [Generic Customer] = @.AccountName GROUP BY Division, [Pay End Dt]) AS s
GROUP BY [Division];
END
Thanks in advance,
-BOK, I was wrong...the last three CASE expressions need to go in the GROUP BY but they can't because they have aggregates. Any ideas?
Wednesday, March 7, 2012
error- microsoft ODBC sql server driver - timeout expired
Hi everyone
I have installed SQL server on my server machine. using localsystem and mixmode option.
It is working fine.
I installed sql server with connectivity tools only option on my client computer.
now, When i try to connect to server using data source from control panel --> Administrative tools --> Data source(ODBC).
but I cant connect.It gives me error as below.
Connection Failed:
SQLState:'HYT00'
Sql Server Error:0
[Microsoft][ODBC SQL Server Driver] Timeout Expired.
I uninstalled sql server from my client and server computer. and installed again.
I tried to ping from client computer to server computer it is working.
even i tried telnet sqlservername 1433
this on is also ok.
even thiough i m facing.
But same error facing
Please help me out.
Regards,
ASIF
Check your SQL Server alias. This is sometimes causing errors as your client is having difficulty mapping names to IP addresses. If you are using ODBC DSN, in the Which SQL Server do you want to connect to ? drop down, type the IP Address of your SQL Server box instead of the alias.
Error message: server component is not supported
I try to install Microsoft SQL Server 2000 Enterprise in my Windows 2000 Pro
machine.
When I run the setup, I clicked SQL Server 2000 Components | Install
Database Server
But it pops up an error message dialog saying
"Microsoft SQL Server 2000 Enterprise Edition server component is not
supported on this operating system. only client components will be available
for installation"
Any ideas? I can only install client, but not server'
Please help!You need a better OS to run Enterprise edition. You can run the developer's
edition on 2000.
"Matthew Louden" <mattloude@.hotmail.com> wrote in message
news:uN9f10YyDHA.556@.TK2MSFTNGP11.phx.gbl...
> I try to install Microsoft SQL Server 2000 Enterprise in my Windows 2000
Pro
> machine.
> When I run the setup, I clicked SQL Server 2000 Components | Install
> Database Server
> But it pops up an error message dialog saying
> "Microsoft SQL Server 2000 Enterprise Edition server component is not
> supported on this operating system. only client components will be
available
> for installation"
> Any ideas? I can only install client, but not server'
> Please help!
>
>
>|||You can't install SQL Server Enterprise Edition on Windows 2000 Pro. You
need Windows 2000 Server or Advanced Server. Alternatively, you can install
MSDE, Developer Edition, Personal Edition, or Evaluation Edition on Windows
2000 Pro.
"Matthew Louden" <mattloude@.hotmail.com> wrote in message
news:uN9f10YyDHA.556@.TK2MSFTNGP11.phx.gbl...
> I try to install Microsoft SQL Server 2000 Enterprise in my Windows 2000
Pro
> machine.
> When I run the setup, I clicked SQL Server 2000 Components | Install
> Database Server
> But it pops up an error message dialog saying
> "Microsoft SQL Server 2000 Enterprise Edition server component is not
> supported on this operating system. only client components will be
available
> for installation"
> Any ideas? I can only install client, but not server'
> Please help!
>
>
>|||How about Windows XP?
"Casey Vanlandingham" <cvanlan@.no.spam.iastate.edu> wrote in message
news:%23%23UkvDZyDHA.1088@.tk2msftngp13.phx.gbl...
> You can't install SQL Server Enterprise Edition on Windows 2000 Pro. You
> need Windows 2000 Server or Advanced Server. Alternatively, you can
install
> MSDE, Developer Edition, Personal Edition, or Evaluation Edition on
Windows
> 2000 Pro.
>
> "Matthew Louden" <mattloude@.hotmail.com> wrote in message
> news:uN9f10YyDHA.556@.TK2MSFTNGP11.phx.gbl...
> > I try to install Microsoft SQL Server 2000 Enterprise in my Windows 2000
> Pro
> > machine.
> >
> > When I run the setup, I clicked SQL Server 2000 Components | Install
> > Database Server
> >
> > But it pops up an error message dialog saying
> > "Microsoft SQL Server 2000 Enterprise Edition server component is not
> > supported on this operating system. only client components will be
> available
> > for installation"
> >
> > Any ideas? I can only install client, but not server'
> >
> > Please help!
> >
> >
> >
> >
> >
>|||The same considerations apply to XP as well.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Matthew Louden" <mattloude@.hotmail.com> wrote in message
news:O5gwcIbyDHA.2304@.TK2MSFTNGP12.phx.gbl...
> How about Windows XP?
>
> "Casey Vanlandingham" <cvanlan@.no.spam.iastate.edu> wrote in message
> news:%23%23UkvDZyDHA.1088@.tk2msftngp13.phx.gbl...
> > You can't install SQL Server Enterprise Edition on Windows 2000 Pro.
You
> > need Windows 2000 Server or Advanced Server. Alternatively, you can
> install
> > MSDE, Developer Edition, Personal Edition, or Evaluation Edition on
> Windows
> > 2000 Pro.
> >
> >
> > "Matthew Louden" <mattloude@.hotmail.com> wrote in message
> > news:uN9f10YyDHA.556@.TK2MSFTNGP11.phx.gbl...
> > > I try to install Microsoft SQL Server 2000 Enterprise in my Windows
2000
> > Pro
> > > machine.
> > >
> > > When I run the setup, I clicked SQL Server 2000 Components | Install
> > > Database Server
> > >
> > > But it pops up an error message dialog saying
> > > "Microsoft SQL Server 2000 Enterprise Edition server component is not
> > > supported on this operating system. only client components will be
> > available
> > > for installation"
> > >
> > > Any ideas? I can only install client, but not server'
> > >
> > > Please help!
> > >
> > >
> > >
> > >
> > >
> >
> >
>
machine.
When I run the setup, I clicked SQL Server 2000 Components | Install
Database Server
But it pops up an error message dialog saying
"Microsoft SQL Server 2000 Enterprise Edition server component is not
supported on this operating system. only client components will be available
for installation"
Any ideas? I can only install client, but not server'
Please help!You need a better OS to run Enterprise edition. You can run the developer's
edition on 2000.
"Matthew Louden" <mattloude@.hotmail.com> wrote in message
news:uN9f10YyDHA.556@.TK2MSFTNGP11.phx.gbl...
> I try to install Microsoft SQL Server 2000 Enterprise in my Windows 2000
Pro
> machine.
> When I run the setup, I clicked SQL Server 2000 Components | Install
> Database Server
> But it pops up an error message dialog saying
> "Microsoft SQL Server 2000 Enterprise Edition server component is not
> supported on this operating system. only client components will be
available
> for installation"
> Any ideas? I can only install client, but not server'
> Please help!
>
>
>|||You can't install SQL Server Enterprise Edition on Windows 2000 Pro. You
need Windows 2000 Server or Advanced Server. Alternatively, you can install
MSDE, Developer Edition, Personal Edition, or Evaluation Edition on Windows
2000 Pro.
"Matthew Louden" <mattloude@.hotmail.com> wrote in message
news:uN9f10YyDHA.556@.TK2MSFTNGP11.phx.gbl...
> I try to install Microsoft SQL Server 2000 Enterprise in my Windows 2000
Pro
> machine.
> When I run the setup, I clicked SQL Server 2000 Components | Install
> Database Server
> But it pops up an error message dialog saying
> "Microsoft SQL Server 2000 Enterprise Edition server component is not
> supported on this operating system. only client components will be
available
> for installation"
> Any ideas? I can only install client, but not server'
> Please help!
>
>
>|||How about Windows XP?
"Casey Vanlandingham" <cvanlan@.no.spam.iastate.edu> wrote in message
news:%23%23UkvDZyDHA.1088@.tk2msftngp13.phx.gbl...
> You can't install SQL Server Enterprise Edition on Windows 2000 Pro. You
> need Windows 2000 Server or Advanced Server. Alternatively, you can
install
> MSDE, Developer Edition, Personal Edition, or Evaluation Edition on
Windows
> 2000 Pro.
>
> "Matthew Louden" <mattloude@.hotmail.com> wrote in message
> news:uN9f10YyDHA.556@.TK2MSFTNGP11.phx.gbl...
> > I try to install Microsoft SQL Server 2000 Enterprise in my Windows 2000
> Pro
> > machine.
> >
> > When I run the setup, I clicked SQL Server 2000 Components | Install
> > Database Server
> >
> > But it pops up an error message dialog saying
> > "Microsoft SQL Server 2000 Enterprise Edition server component is not
> > supported on this operating system. only client components will be
> available
> > for installation"
> >
> > Any ideas? I can only install client, but not server'
> >
> > Please help!
> >
> >
> >
> >
> >
>|||The same considerations apply to XP as well.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Matthew Louden" <mattloude@.hotmail.com> wrote in message
news:O5gwcIbyDHA.2304@.TK2MSFTNGP12.phx.gbl...
> How about Windows XP?
>
> "Casey Vanlandingham" <cvanlan@.no.spam.iastate.edu> wrote in message
> news:%23%23UkvDZyDHA.1088@.tk2msftngp13.phx.gbl...
> > You can't install SQL Server Enterprise Edition on Windows 2000 Pro.
You
> > need Windows 2000 Server or Advanced Server. Alternatively, you can
> install
> > MSDE, Developer Edition, Personal Edition, or Evaluation Edition on
> Windows
> > 2000 Pro.
> >
> >
> > "Matthew Louden" <mattloude@.hotmail.com> wrote in message
> > news:uN9f10YyDHA.556@.TK2MSFTNGP11.phx.gbl...
> > > I try to install Microsoft SQL Server 2000 Enterprise in my Windows
2000
> > Pro
> > > machine.
> > >
> > > When I run the setup, I clicked SQL Server 2000 Components | Install
> > > Database Server
> > >
> > > But it pops up an error message dialog saying
> > > "Microsoft SQL Server 2000 Enterprise Edition server component is not
> > > supported on this operating system. only client components will be
> > available
> > > for installation"
> > >
> > > Any ideas? I can only install client, but not server'
> > >
> > > Please help!
> > >
> > >
> > >
> > >
> > >
> >
> >
>
Sunday, February 26, 2012
Error Message When Deploying Report - The Item '/Data Sources'
Hi All,
I am wondering is someone can point me in the right direction,
I updated to the latest service pack on my Report Server Production Machine
and now when I attempt to deloy a report I get the following message
The Item '/Data Sources' already exists
I have tried everything I can think of to stop the message
~ Disabling and Enabling the OverwriteDataSources
~ Adding the Shared Datasource directly into the SQL frontend...
~ Running around like a chicken with no head
all seem to have the same effect...
Currently all other reports seem to work ok...
Has anyone got idea... apart from never ever ever updating to the latest
patches ;)
...Cheers
MattOn Sep 11, 10:26 pm, Aussie Matt
<AussieM...@.discussions.microsoft.com> wrote:
> Hi All,
> I am wondering is someone can point me in the right direction,
> I updated to the latest service pack on my Report Server Production Machine
> and now when I attempt to deloy a report I get the following message
> The Item '/Data Sources' already exists
> I have tried everything I can think of to stop the message
> ~ Disabling and Enabling the OverwriteDataSources
> ~ Adding the Shared Datasource directly into the SQL frontend...
> ~ Running around like a chicken with no head
> all seem to have the same effect...
> Currently all other reports seem to work ok...
> Has anyone got idea... apart from never ever ever updating to the latest
> patches ;)
> ...Cheers
> Matt
This might be overly simplistic, but have you tried to reselect the
datasource in the Report Mgr for the report? I have installed SP2 on a
couple different Report Servers w/no problems.
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Enrique,
Hi mate... yes that seems to be ok..
The report actually renders ok in the development environment...
I even tried creating a new report to see if that would overwrite the
existing shared data source but it has the same problemâ?¦. I am wondering if
it actually related to IIS6 somehow.. thou all the permissions look ok...
Thanks for the advice thou,
Cheers
Matt
"EMartinez" wrote:
> On Sep 11, 10:26 pm, Aussie Matt
> <AussieM...@.discussions.microsoft.com> wrote:
> > Hi All,
> > I am wondering is someone can point me in the right direction,
> > I updated to the latest service pack on my Report Server Production Machine
> > and now when I attempt to deloy a report I get the following message
> >
> > The Item '/Data Sources' already exists
> >
> > I have tried everything I can think of to stop the message
> > ~ Disabling and Enabling the OverwriteDataSources
> > ~ Adding the Shared Datasource directly into the SQL frontend...
> > ~ Running around like a chicken with no head
> >
> > all seem to have the same effect...
> >
> > Currently all other reports seem to work ok...
> >
> > Has anyone got idea... apart from never ever ever updating to the latest
> > patches ;)
> >
> > ...Cheers
> >
> > Matt
>
> This might be overly simplistic, but have you tried to reselect the
> datasource in the Report Mgr for the report? I have installed SP2 on a
> couple different Report Servers w/no problems.
> Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||Hello Again,
Well I fixed it, not sure how / why it got screwy, to fix it I went to the
Reporting Services Configuration Manager
and reset the default properties for the the Report Server Virtual
Directory and Report Manager Virtual Directory... this seem to rectify
whatever the problem
was...
Cheers
Matt
"Aussie Matt" wrote:
> Enrique,
> Hi mate... yes that seems to be ok..
> The report actually renders ok in the development environment...
> I even tried creating a new report to see if that would overwrite the
> existing shared data source but it has the same problemâ?¦. I am wondering if
> it actually related to IIS6 somehow.. thou all the permissions look ok...
> Thanks for the advice thou,
> Cheers
> Matt
> "EMartinez" wrote:
> > On Sep 11, 10:26 pm, Aussie Matt
> > <AussieM...@.discussions.microsoft.com> wrote:
> > > Hi All,
> > > I am wondering is someone can point me in the right direction,
> > > I updated to the latest service pack on my Report Server Production Machine
> > > and now when I attempt to deloy a report I get the following message
> > >
> > > The Item '/Data Sources' already exists
> > >
> > > I have tried everything I can think of to stop the message
> > > ~ Disabling and Enabling the OverwriteDataSources
> > > ~ Adding the Shared Datasource directly into the SQL frontend...
> > > ~ Running around like a chicken with no head
> > >
> > > all seem to have the same effect...
> > >
> > > Currently all other reports seem to work ok...
> > >
> > > Has anyone got idea... apart from never ever ever updating to the latest
> > > patches ;)
> > >
> > > ...Cheers
> > >
> > > Matt
> >
> >
> > This might be overly simplistic, but have you tried to reselect the
> > datasource in the Report Mgr for the report? I have installed SP2 on a
> > couple different Report Servers w/no problems.
> > Hope this helps.
> >
> > Regards,
> >
> > Enrique Martinez
> > Sr. Software Consultant
> >
> >|||On Sep 12, 5:24 am, Aussie Matt <AussieM...@.discussions.microsoft.com>
wrote:
> Hello Again,
> Well I fixed it, not sure how / why it got screwy, to fix it I went to the
> Reporting Services Configuration Manager
> and reset the default properties for the the Report Server Virtual
> Directory and Report Manager Virtual Directory... this seem to rectify
> whatever the problem
> was...
> Cheers
> Matt
> "Aussie Matt" wrote:
> > Enrique,
> > Hi mate... yes that seems to be ok..
> > The report actually renders ok in the development environment...
> > I even tried creating a new report to see if that would overwrite the
> > existing shared data source but it has the same problem... I am wondering if
> > it actually related to IIS6 somehow.. thou all the permissions look ok...
> > Thanks for the advice thou,
> > Cheers
> > Matt
> > "EMartinez" wrote:
> > > On Sep 11, 10:26 pm, Aussie Matt
> > > <AussieM...@.discussions.microsoft.com> wrote:
> > > > Hi All,
> > > > I am wondering is someone can point me in the right direction,
> > > > I updated to the latest service pack on my Report Server Production Machine
> > > > and now when I attempt to deloy a report I get the following message
> > > > The Item '/Data Sources' already exists
> > > > I have tried everything I can think of to stop the message
> > > > ~ Disabling and Enabling the OverwriteDataSources
> > > > ~ Adding the Shared Datasource directly into the SQL frontend...
> > > > ~ Running around like a chicken with no head
> > > > all seem to have the same effect...
> > > > Currently all other reports seem to work ok...
> > > > Has anyone got idea... apart from never ever ever updating to the latest
> > > > patches ;)
> > > > ...Cheers
> > > > Matt
> > > This might be overly simplistic, but have you tried to reselect the
> > > datasource in the Report Mgr for the report? I have installed SP2 on a
> > > couple different Report Servers w/no problems.
> > > Hope this helps.
> > > Regards,
> > > Enrique Martinez
> > > Sr. Software Consultant
I'm surprised that this resolved the issue; however, I'm glad you
fixed the problem. Let me know if I can be of further assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||I just spent a considerable amount of time trying to debug this error, and in
the end it was a permissions problem. As a new employee I had been given
access to the Reports folder but not to the Data Sources folder.
Hopefully this note can save someone else some time (and frustration)
diagnosing this error.
I am wondering is someone can point me in the right direction,
I updated to the latest service pack on my Report Server Production Machine
and now when I attempt to deloy a report I get the following message
The Item '/Data Sources' already exists
I have tried everything I can think of to stop the message
~ Disabling and Enabling the OverwriteDataSources
~ Adding the Shared Datasource directly into the SQL frontend...
~ Running around like a chicken with no head
all seem to have the same effect...
Currently all other reports seem to work ok...
Has anyone got idea... apart from never ever ever updating to the latest
patches ;)
...Cheers
MattOn Sep 11, 10:26 pm, Aussie Matt
<AussieM...@.discussions.microsoft.com> wrote:
> Hi All,
> I am wondering is someone can point me in the right direction,
> I updated to the latest service pack on my Report Server Production Machine
> and now when I attempt to deloy a report I get the following message
> The Item '/Data Sources' already exists
> I have tried everything I can think of to stop the message
> ~ Disabling and Enabling the OverwriteDataSources
> ~ Adding the Shared Datasource directly into the SQL frontend...
> ~ Running around like a chicken with no head
> all seem to have the same effect...
> Currently all other reports seem to work ok...
> Has anyone got idea... apart from never ever ever updating to the latest
> patches ;)
> ...Cheers
> Matt
This might be overly simplistic, but have you tried to reselect the
datasource in the Report Mgr for the report? I have installed SP2 on a
couple different Report Servers w/no problems.
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Enrique,
Hi mate... yes that seems to be ok..
The report actually renders ok in the development environment...
I even tried creating a new report to see if that would overwrite the
existing shared data source but it has the same problemâ?¦. I am wondering if
it actually related to IIS6 somehow.. thou all the permissions look ok...
Thanks for the advice thou,
Cheers
Matt
"EMartinez" wrote:
> On Sep 11, 10:26 pm, Aussie Matt
> <AussieM...@.discussions.microsoft.com> wrote:
> > Hi All,
> > I am wondering is someone can point me in the right direction,
> > I updated to the latest service pack on my Report Server Production Machine
> > and now when I attempt to deloy a report I get the following message
> >
> > The Item '/Data Sources' already exists
> >
> > I have tried everything I can think of to stop the message
> > ~ Disabling and Enabling the OverwriteDataSources
> > ~ Adding the Shared Datasource directly into the SQL frontend...
> > ~ Running around like a chicken with no head
> >
> > all seem to have the same effect...
> >
> > Currently all other reports seem to work ok...
> >
> > Has anyone got idea... apart from never ever ever updating to the latest
> > patches ;)
> >
> > ...Cheers
> >
> > Matt
>
> This might be overly simplistic, but have you tried to reselect the
> datasource in the Report Mgr for the report? I have installed SP2 on a
> couple different Report Servers w/no problems.
> Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||Hello Again,
Well I fixed it, not sure how / why it got screwy, to fix it I went to the
Reporting Services Configuration Manager
and reset the default properties for the the Report Server Virtual
Directory and Report Manager Virtual Directory... this seem to rectify
whatever the problem
was...
Cheers
Matt
"Aussie Matt" wrote:
> Enrique,
> Hi mate... yes that seems to be ok..
> The report actually renders ok in the development environment...
> I even tried creating a new report to see if that would overwrite the
> existing shared data source but it has the same problemâ?¦. I am wondering if
> it actually related to IIS6 somehow.. thou all the permissions look ok...
> Thanks for the advice thou,
> Cheers
> Matt
> "EMartinez" wrote:
> > On Sep 11, 10:26 pm, Aussie Matt
> > <AussieM...@.discussions.microsoft.com> wrote:
> > > Hi All,
> > > I am wondering is someone can point me in the right direction,
> > > I updated to the latest service pack on my Report Server Production Machine
> > > and now when I attempt to deloy a report I get the following message
> > >
> > > The Item '/Data Sources' already exists
> > >
> > > I have tried everything I can think of to stop the message
> > > ~ Disabling and Enabling the OverwriteDataSources
> > > ~ Adding the Shared Datasource directly into the SQL frontend...
> > > ~ Running around like a chicken with no head
> > >
> > > all seem to have the same effect...
> > >
> > > Currently all other reports seem to work ok...
> > >
> > > Has anyone got idea... apart from never ever ever updating to the latest
> > > patches ;)
> > >
> > > ...Cheers
> > >
> > > Matt
> >
> >
> > This might be overly simplistic, but have you tried to reselect the
> > datasource in the Report Mgr for the report? I have installed SP2 on a
> > couple different Report Servers w/no problems.
> > Hope this helps.
> >
> > Regards,
> >
> > Enrique Martinez
> > Sr. Software Consultant
> >
> >|||On Sep 12, 5:24 am, Aussie Matt <AussieM...@.discussions.microsoft.com>
wrote:
> Hello Again,
> Well I fixed it, not sure how / why it got screwy, to fix it I went to the
> Reporting Services Configuration Manager
> and reset the default properties for the the Report Server Virtual
> Directory and Report Manager Virtual Directory... this seem to rectify
> whatever the problem
> was...
> Cheers
> Matt
> "Aussie Matt" wrote:
> > Enrique,
> > Hi mate... yes that seems to be ok..
> > The report actually renders ok in the development environment...
> > I even tried creating a new report to see if that would overwrite the
> > existing shared data source but it has the same problem... I am wondering if
> > it actually related to IIS6 somehow.. thou all the permissions look ok...
> > Thanks for the advice thou,
> > Cheers
> > Matt
> > "EMartinez" wrote:
> > > On Sep 11, 10:26 pm, Aussie Matt
> > > <AussieM...@.discussions.microsoft.com> wrote:
> > > > Hi All,
> > > > I am wondering is someone can point me in the right direction,
> > > > I updated to the latest service pack on my Report Server Production Machine
> > > > and now when I attempt to deloy a report I get the following message
> > > > The Item '/Data Sources' already exists
> > > > I have tried everything I can think of to stop the message
> > > > ~ Disabling and Enabling the OverwriteDataSources
> > > > ~ Adding the Shared Datasource directly into the SQL frontend...
> > > > ~ Running around like a chicken with no head
> > > > all seem to have the same effect...
> > > > Currently all other reports seem to work ok...
> > > > Has anyone got idea... apart from never ever ever updating to the latest
> > > > patches ;)
> > > > ...Cheers
> > > > Matt
> > > This might be overly simplistic, but have you tried to reselect the
> > > datasource in the Report Mgr for the report? I have installed SP2 on a
> > > couple different Report Servers w/no problems.
> > > Hope this helps.
> > > Regards,
> > > Enrique Martinez
> > > Sr. Software Consultant
I'm surprised that this resolved the issue; however, I'm glad you
fixed the problem. Let me know if I can be of further assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||I just spent a considerable amount of time trying to debug this error, and in
the end it was a permissions problem. As a new employee I had been given
access to the Reports folder but not to the Data Sources folder.
Hopefully this note can save someone else some time (and frustration)
diagnosing this error.
Subscribe to:
Posts (Atom)