Howdy - -
Is there some kind of problem backing up to FAT32? We have a HUGE
drive, and we get a write failure (status = 112) even though there is
way more than enough space for the backup.
Any ideas?
- - Herb
FAT32 limits file sizes to 4GB. We had this problem with some filegroups
that filled up
even though the disks had adequate space.
"Herb Ray" <herb@.ad-co.com> wrote in message
news:ukhUe.15$yu1.325681@.news.sisna.com...
> Howdy - -
> Is there some kind of problem backing up to FAT32? We have a HUGE
> drive, and we get a write failure (status = 112) even though there is
> way more than enough space for the backup.
> Any ideas?
> - - Herb
|||Armando Prato wrote:
> FAT32 limits file sizes to 4GB. We had this problem with some filegroups
> that filled up
> even though the disks had adequate space.
> "Herb Ray" <herb@.ad-co.com> wrote in message
> news:ukhUe.15$yu1.325681@.news.sisna.com...
>
>
Armando - -
Thanks for your reply. That sounds like it's our problem.
- - Herb
Showing posts with label failure. Show all posts
Showing posts with label failure. Show all posts
Monday, March 12, 2012
FAT32 and Status 112
Howdy - -
Is there some kind of problem backing up to FAT32? We have a HUGE
drive, and we get a write failure (status = 112) even though there is
way more than enough space for the backup.
Any ideas?
- - HerbFAT32 limits file sizes to 4GB. We had this problem with some filegroups
that filled up
even though the disks had adequate space.
"Herb Ray" <herb@.ad-co.com> wrote in message
news:ukhUe.15$yu1.325681@.news.sisna.com...
> Howdy - -
> Is there some kind of problem backing up to FAT32? We have a HUGE
> drive, and we get a write failure (status = 112) even though there is
> way more than enough space for the backup.
> Any ideas?
> - - Herb|||Armando Prato wrote:
> FAT32 limits file sizes to 4GB. We had this problem with some filegroups
> that filled up
> even though the disks had adequate space.
> "Herb Ray" <herb@.ad-co.com> wrote in message
> news:ukhUe.15$yu1.325681@.news.sisna.com...
>
>
>
Armando - -
Thanks for your reply. That sounds like it's our problem.
- - Herb
Is there some kind of problem backing up to FAT32? We have a HUGE
drive, and we get a write failure (status = 112) even though there is
way more than enough space for the backup.
Any ideas?
- - HerbFAT32 limits file sizes to 4GB. We had this problem with some filegroups
that filled up
even though the disks had adequate space.
"Herb Ray" <herb@.ad-co.com> wrote in message
news:ukhUe.15$yu1.325681@.news.sisna.com...
> Howdy - -
> Is there some kind of problem backing up to FAT32? We have a HUGE
> drive, and we get a write failure (status = 112) even though there is
> way more than enough space for the backup.
> Any ideas?
> - - Herb|||Armando Prato wrote:
> FAT32 limits file sizes to 4GB. We had this problem with some filegroups
> that filled up
> even though the disks had adequate space.
> "Herb Ray" <herb@.ad-co.com> wrote in message
> news:ukhUe.15$yu1.325681@.news.sisna.com...
>
>
>
Armando - -
Thanks for your reply. That sounds like it's our problem.
- - Herb
FAT32 and Status 112
Howdy - -
Is there some kind of problem backing up to FAT32? We have a HUGE
drive, and we get a write failure (status = 112) even though there is
way more than enough space for the backup.
Any ideas?
- - HerbFAT32 limits file sizes to 4GB. We had this problem with some filegroups
that filled up
even though the disks had adequate space.
"Herb Ray" <herb@.ad-co.com> wrote in message
news:ukhUe.15$yu1.325681@.news.sisna.com...
> Howdy - -
> Is there some kind of problem backing up to FAT32? We have a HUGE
> drive, and we get a write failure (status = 112) even though there is
> way more than enough space for the backup.
> Any ideas?
> - - Herb|||Armando Prato wrote:
> FAT32 limits file sizes to 4GB. We had this problem with some filegroups
> that filled up
> even though the disks had adequate space.
> "Herb Ray" <herb@.ad-co.com> wrote in message
> news:ukhUe.15$yu1.325681@.news.sisna.com...
>>Howdy - -
>>Is there some kind of problem backing up to FAT32? We have a HUGE
>>drive, and we get a write failure (status = 112) even though there is
>>way more than enough space for the backup.
>>Any ideas?
>>- - Herb
>
>
Armando - -
Thanks for your reply. That sounds like it's our problem.
- - Herb
Is there some kind of problem backing up to FAT32? We have a HUGE
drive, and we get a write failure (status = 112) even though there is
way more than enough space for the backup.
Any ideas?
- - HerbFAT32 limits file sizes to 4GB. We had this problem with some filegroups
that filled up
even though the disks had adequate space.
"Herb Ray" <herb@.ad-co.com> wrote in message
news:ukhUe.15$yu1.325681@.news.sisna.com...
> Howdy - -
> Is there some kind of problem backing up to FAT32? We have a HUGE
> drive, and we get a write failure (status = 112) even though there is
> way more than enough space for the backup.
> Any ideas?
> - - Herb|||Armando Prato wrote:
> FAT32 limits file sizes to 4GB. We had this problem with some filegroups
> that filled up
> even though the disks had adequate space.
> "Herb Ray" <herb@.ad-co.com> wrote in message
> news:ukhUe.15$yu1.325681@.news.sisna.com...
>>Howdy - -
>>Is there some kind of problem backing up to FAT32? We have a HUGE
>>drive, and we get a write failure (status = 112) even though there is
>>way more than enough space for the backup.
>>Any ideas?
>>- - Herb
>
>
Armando - -
Thanks for your reply. That sounds like it's our problem.
- - Herb
Sunday, February 26, 2012
Failure writing properties running SSIS package from a Web Service
I am attempting to run an SSIS package from a web service. Right now both the service and package are on my local machine which is running XP. I have accessed the web service from a client application in debug mode. I am not sure if it is actually running under aspnet_wp.exe because it is XP and a development environment? (separate question)? The package fails with a series of OnError messages similar to:
The result of the expression ""/c DEL /F /Q \"" + @.DeployFolder + "\\catalog.diff.lz\""" on property "Arguments" cannot be written to the property. The expression was evaluated, but cannot be set on the property.
An initial supposition is that the permissions of the web service are inadequate for the package. I have the authentication as "Windows" and <identity impersonate="true" /> in the Web.Config file. When I break in the debugger the Environment.UserName and Environment.UserDomainName are mine and I am an Admin on the box.
the authorization is 'deny users="?".
The article that describes basic implementation of this in a Web Service states:
With its default settings for authentication and authorization, a Web
service generally does not have sufficient permissions to access SQL
Server or the file system to load and execute packages. You may have to
assign appropriate permissions to the Web service by configuring its
authentication and authorization settings in the web.config
file and assigning database and file system permissions as appropriate.
A complete discussion of Web, database, and file system permissions is
beyond the scope of this topic.
And how!
Note that the load is fine and that this is a run time error and that the package runs correctly when run manually from SQL Server using the 'run package' menu item in the Object Explorer tree of the SQL Server Management Console.
I need to know if this is an ASP.NET issue per se or XP or if this is even a security issue. And how to solve it! This is critical path so an expeditious reply with a solution would be greatly appreciated.Can't believe I left this out but the the web service is running under Integrated Windows authentication.
Friday, February 24, 2012
Failure writing file
I get "Failure writing file" ... when my subscription runs? Does any one know
how to fix it?Can you post the error message in the ReportServerService<date>.log file.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"AbiBaby" <AbiBaby@.discussions.microsoft.com> wrote in message
news:17C09CC5-47F8-447A-B185-34143ABDAE2C@.microsoft.com...
> I get "Failure writing file" ... when my subscription runs? Does any one
know
> how to fix it?|||you should give to you network user the right to access (write) the folder
where you report are delivred.
"AbiBaby" wrote:
> I get "Failure writing file" ... when my subscription runs? Does any one know
> how to fix it?|||It has all Rights, i eneabled everyone. I wrote my own subscription service.
And it works!
"Tino [Securitas.fr]" wrote:
> you should give to you network user the right to access (write) the folder
> where you report are delivred.
> "AbiBaby" wrote:
> > I get "Failure writing file" ... when my subscription runs? Does any one know
> > how to fix it?
how to fix it?Can you post the error message in the ReportServerService<date>.log file.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"AbiBaby" <AbiBaby@.discussions.microsoft.com> wrote in message
news:17C09CC5-47F8-447A-B185-34143ABDAE2C@.microsoft.com...
> I get "Failure writing file" ... when my subscription runs? Does any one
know
> how to fix it?|||you should give to you network user the right to access (write) the folder
where you report are delivred.
"AbiBaby" wrote:
> I get "Failure writing file" ... when my subscription runs? Does any one know
> how to fix it?|||It has all Rights, i eneabled everyone. I wrote my own subscription service.
And it works!
"Tino [Securitas.fr]" wrote:
> you should give to you network user the right to access (write) the folder
> where you report are delivred.
> "AbiBaby" wrote:
> > I get "Failure writing file" ... when my subscription runs? Does any one know
> > how to fix it?
Failure Workflow Does Not Fire
Hello,
I have a SQL Server 2000 DTS package in which the first step executes a batch file. The batch file contains FTP commands that log into an FTP server, and pull down whatever file is there.
I set up a failure workflow to send an email if the step fails. When I have a SQL Server job run this package, and there is no file to dowload, the whole package fails without the failure workflow result firing.
For the step (DTSStep_DTSCreateProcessTask_1), I have the 'FailPackageOnError' property set to -1. In the package properties, I have the check box for 'Fail Package on First Error' cleared.
What do I need to do so that the failure workflow occurs when the step fails?
Thank you for your help!
cdun2Are you sure the fact that no file is there will cause the step to error out?|||u need to trap errors from external programs like bat files to have the failed workflow activated. aslo not all external programs returns error code to the calling application. for bat files, u will have to set errorlevel to make the calling program understand the success/failure
for example when using xp_cmdshell, this will call the failure workflow, if present
declare @.err int
exec @.err = master..xp_cmdshell 'C:\xx.bat'
if @.err = 1
RAISERROR ('err',16,1)
the above code will not fire the failure workflow if u just execute
exec master..xp_cmdshell 'C:\xx.bat'
and even if the xx.bat is not present in folder C:\|||Thank you for your help!
cdun2|||Another option is to create an operator when you scheduled the job and an e-mail will be sent out if the job fails.
Good luck
I have a SQL Server 2000 DTS package in which the first step executes a batch file. The batch file contains FTP commands that log into an FTP server, and pull down whatever file is there.
I set up a failure workflow to send an email if the step fails. When I have a SQL Server job run this package, and there is no file to dowload, the whole package fails without the failure workflow result firing.
For the step (DTSStep_DTSCreateProcessTask_1), I have the 'FailPackageOnError' property set to -1. In the package properties, I have the check box for 'Fail Package on First Error' cleared.
What do I need to do so that the failure workflow occurs when the step fails?
Thank you for your help!
cdun2Are you sure the fact that no file is there will cause the step to error out?|||u need to trap errors from external programs like bat files to have the failed workflow activated. aslo not all external programs returns error code to the calling application. for bat files, u will have to set errorlevel to make the calling program understand the success/failure
for example when using xp_cmdshell, this will call the failure workflow, if present
declare @.err int
exec @.err = master..xp_cmdshell 'C:\xx.bat'
if @.err = 1
RAISERROR ('err',16,1)
the above code will not fire the failure workflow if u just execute
exec master..xp_cmdshell 'C:\xx.bat'
and even if the xx.bat is not present in folder C:\|||Thank you for your help!
cdun2|||Another option is to create an operator when you scheduled the job and an e-mail will be sent out if the job fails.
Good luck
Failure with transactional replication with immediate updating subscriptions
I have set up a transactional replication with immediate updating
subscriptions,
Distributor and Subscriber on diff servers.
When I try to update rows in the subscriber I have the following error:
[Microsoft][ODBC SQL Server Driver][SQLServer] Login failed for user 'sa'
(Both servers have the same 'sa' password)
Does anybody know how can I do that ?
Thank you
Hernn Rado
review this kb article:
http://support.microsoft.com/default...b;en-us;320773
"Hernn Rado" <hernan_radovitzki@.hotmail.com> wrote in message
news:eAt7HgE6EHA.2592@.TK2MSFTNGP09.phx.gbl...
> I have set up a transactional replication with immediate updating
> subscriptions,
> Distributor and Subscriber on diff servers.
>
> When I try to update rows in the subscriber I have the following error:
> [Microsoft][ODBC SQL Server Driver][SQLServer] Login failed for user 'sa'
> (Both servers have the same 'sa' password)
> Does anybody know how can I do that ?
> Thank you
> Hernn Rado
>
|||Thanks Hilary !
I changed the SA password to a blank one and its works ! Later, I changed
again both password (to the original) and ran the sp_link_publication on the
subscriber (specifying the SA psw) but its doesnt work !!
What can I do?
"Hilary Cotter" <hilary.cotter@.gmail.com> escribi en el mensaje
news:O5fVNsE6EHA.248@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> review this kb article:
> http://support.microsoft.com/default...b;en-us;320773
> "Hernn Rado" <hernan_radovitzki@.hotmail.com> wrote in message
> news:eAt7HgE6EHA.2592@.TK2MSFTNGP09.phx.gbl...
'sa'
>
subscriptions,
Distributor and Subscriber on diff servers.
When I try to update rows in the subscriber I have the following error:
[Microsoft][ODBC SQL Server Driver][SQLServer] Login failed for user 'sa'
(Both servers have the same 'sa' password)
Does anybody know how can I do that ?
Thank you
Hernn Rado
review this kb article:
http://support.microsoft.com/default...b;en-us;320773
"Hernn Rado" <hernan_radovitzki@.hotmail.com> wrote in message
news:eAt7HgE6EHA.2592@.TK2MSFTNGP09.phx.gbl...
> I have set up a transactional replication with immediate updating
> subscriptions,
> Distributor and Subscriber on diff servers.
>
> When I try to update rows in the subscriber I have the following error:
> [Microsoft][ODBC SQL Server Driver][SQLServer] Login failed for user 'sa'
> (Both servers have the same 'sa' password)
> Does anybody know how can I do that ?
> Thank you
> Hernn Rado
>
|||Thanks Hilary !
I changed the SA password to a blank one and its works ! Later, I changed
again both password (to the original) and ran the sp_link_publication on the
subscriber (specifying the SA psw) but its doesnt work !!
What can I do?
"Hilary Cotter" <hilary.cotter@.gmail.com> escribi en el mensaje
news:O5fVNsE6EHA.248@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> review this kb article:
> http://support.microsoft.com/default...b;en-us;320773
> "Hernn Rado" <hernan_radovitzki@.hotmail.com> wrote in message
> news:eAt7HgE6EHA.2592@.TK2MSFTNGP09.phx.gbl...
'sa'
>
Failure with transactional replication
I have set up a transactional replication with immediate updating push
subscriptions:
Distributor: W2003, SQL 2000 Standard SP3
Subscriber: WXPSP2, MSDE2000A (SP3)
When I try to update rows at the subscriber with Enterprise Manager, I have
the following error:
Database error: [Microsoft][ODBC SQL Server Driver][SQLServer][OLE/DB
provider returned message: Login failed for user 'sa']
Both servers have strong 'sa' password.
I tried the methods in KB320773, but i receive the error message.
Does anybody know how can I do that?
Thank you
Lajos Szabo
have a look at this kb article
http://support.microsoft.com/default...b;en-us;320773
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Now available on Amazon.com
http://www.amazon.com/gp/product/off...?condition=all
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Lajos Szabo" <Lajos Szabo@.discussions.microsoft.com> wrote in message
news:45B1C0ED-F6CC-4377-A3D2-21F1602FC429@.microsoft.com...
> I have set up a transactional replication with immediate updating push
> subscriptions:
> Distributor: W2003, SQL 2000 Standard SP3
> Subscriber: WXPSP2, MSDE2000A (SP3)
> When I try to update rows at the subscriber with Enterprise Manager, I
have
> the following error:
> Database error: [Microsoft][ODBC SQL Server Driver][SQLServer][OLE/DB
> provider returned message: Login failed for user 'sa']
> Both servers have strong 'sa' password.
> I tried the methods in KB320773, but i receive the error message.
> Does anybody know how can I do that?
> Thank you
> Lajos Szabo
subscriptions:
Distributor: W2003, SQL 2000 Standard SP3
Subscriber: WXPSP2, MSDE2000A (SP3)
When I try to update rows at the subscriber with Enterprise Manager, I have
the following error:
Database error: [Microsoft][ODBC SQL Server Driver][SQLServer][OLE/DB
provider returned message: Login failed for user 'sa']
Both servers have strong 'sa' password.
I tried the methods in KB320773, but i receive the error message.
Does anybody know how can I do that?
Thank you
Lajos Szabo
have a look at this kb article
http://support.microsoft.com/default...b;en-us;320773
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Now available on Amazon.com
http://www.amazon.com/gp/product/off...?condition=all
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Lajos Szabo" <Lajos Szabo@.discussions.microsoft.com> wrote in message
news:45B1C0ED-F6CC-4377-A3D2-21F1602FC429@.microsoft.com...
> I have set up a transactional replication with immediate updating push
> subscriptions:
> Distributor: W2003, SQL 2000 Standard SP3
> Subscriber: WXPSP2, MSDE2000A (SP3)
> When I try to update rows at the subscriber with Enterprise Manager, I
have
> the following error:
> Database error: [Microsoft][ODBC SQL Server Driver][SQLServer][OLE/DB
> provider returned message: Login failed for user 'sa']
> Both servers have strong 'sa' password.
> I tried the methods in KB320773, but i receive the error message.
> Does anybody know how can I do that?
> Thank you
> Lajos Szabo
Failure when installing SQL 2005 SP1 on Windows 2003 Server
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.Thanks,
Sam Lester (MSFT)|||
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.
It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.
|||That did the trick!
Many thanks for the help.
|||I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.
What's strange is there is nothing that should've set this to registry entry to 2.
Failure when installing SQL 2005 SP1 on Windows 2003 Server
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.Thanks,
Sam Lester (MSFT)|||
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.
It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.
|||That did the trick!
Many thanks for the help.
|||I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.
What's strange is there is nothing that should've set this to registry entry to 2.
Failure when installing SQL 2005 SP1 on Windows 2003 Server
Hello.
When I installed SQL 2005 SP1 on Windows 2003 Server, I received the following message:
"A recently applied update, KB913090, failed to install."
At the end, "Database Services" was marked as "Failure".
I have tried everything I could find in the knowledge base and on the forums, but still
was not able to install SP1.
For example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;918357
Any insights would be greatly appreciated.
Can you search your hotfix logs (%WINDIR%/hotfix directory) for the text string "value 3" and include the 10-20 lines above it? That should give us a more descriptive error.Thanks,
Sam Lester (MSFT)|||
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (B0!C0) [22:08:08:355]: Transforming table _sqlAction.
MSI (s) (B0!C0) [22:08:08:355]: Note: 1: 2262 2: _sqlAction 3: -2147287038
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup failed to parse the SQL script "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Upgrade\procsyst.sql". The error code is The system cannot find the file specified.
. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='2' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sat Sep 23 22:08:08 2006
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='2' GetLastError='0'>
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (B0:A8) [22:08:09:370]: Transforming table InstallExecuteSequence.
MSI (s) (B0:A8) [22:08:09:370]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:08:09: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
It seams there was a failure during previous upgrade. At this point I would suggest that you go to AddRemove Programs select MS SQL Server 2005 and Change. Then you select the SQL instance that failed and Database Engine. Proceed to Change or Remove Instance dialog and I assume there is an option Complete the suspended installation so select that one.
It is possible that setup needs access to the original installation media so if you installed from CD insert it before launching the setup.
|||That did the trick!
Many thanks for the help.
|||I ran into this issue and resolved it by changing the registry. Under: Software\Policies\Microsoft\Windows\Installer, I found that DisableMSI was not set to 0. For some reason it was set to 2. After changing this to 0, SP1 installed fine.
What's strange is there is nothing that should've set this to registry entry to 2.
Failure to start up SQL Server
SQL fails to start up - no error message is given- in SQL Server Service
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)
Leonard wrote:
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)
and the error message is:??
|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)
|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)
|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)
Leonard wrote:
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)
and the error message is:??
|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)
|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)
|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Failure to start up SQL Server
SQL fails to start up - no error message is given- in SQL Server Service
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)Leonard wrote:[vbcol=seagreen]
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)[/vbcol
]
and the error message is:'?|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)Leonard wrote:[vbcol=seagreen]
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)[/vbcol
]
and the error message is:'?|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Failure to start up SQL Server
SQL fails to start up - no error message is given- in SQL Server Service
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)Leonard wrote:
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)
and the error message is:'?|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)Leonard wrote:
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)
and the error message is:'?|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Failure to run when using DTC
Does anyone hany any experience of using SSIS with MS DTC?
I have a package that runs successfully. When I switch it to using transactions (i.e. TransactionOption=Required) it fails. I get the following messages in the log:
-Starting distributed transaction for this container.
-Failed to acquire connection "<connection-manager-name>". Connection may not be configured correctly or you may not have the right permissions on this connection.
-Aborting the current distributed transaction.
I have a package that runs successfully. When I switch it to using transactions (i.e. TransactionOption=Required) it fails. I get the following messages in the log:
-Starting distributed transaction for this container.
-Failed to acquire connection "<connection-manager-name>". Connection may not be configured correctly or you may not have the right permissions on this connection.
-Aborting the current distributed transaction.
So - it seems it is having trouble enlisting that connection manager in a distributed transaction. My connection manager points at a SQL Server database on a different server to where I am running the package.
The connection string on the connection manager is: Data Source=ABENTAH3D02\DEVDBINSTANCE;Initial Catalog=CUESeerMetadata;Provider=SQLOLEDB.1;Integrated Security=SSPI;Auto Translate=False;
OK, so I kind of know where the error is but I don't know exactly what's causing it or how to go about diagnosing the problem. I don't have much experience of MS DTC although I have used it from SSIS in the past successfully.
Does anyone know the pre-requisites for using MS DTC?
How can I go about finding the problem?
Thanks
JamieThis sounds like a DTC issue with your permissions.
I'm not sure what the problem is, but here are a few things to check:
Are you able to enlist in a transaction on the remote machine where the SServer is? Run the package on that machine if you can. Is it successful there?
Is DTC started and running on both machines?
Do you have the priviledges to access the connection on the remote machine?
You might check the Windows Event Viewer on both machines to see if there are any messages that may give you more information about the problem.
HTH,
K|||I don't have the ability to run the package on the SQL box - or more accurately don't have time to install all the pre-reqs- but I'm pretyt sure that it IS a problem enlisting remote connections in the txn. i.e. I have a local connection in my package which enlists in the transaction without a problem.
In my local dtc trace log I have the following messages (many times)
"transaction got begun, description : '<NULL>"
"received request to abort the transaction from beginner"
"transaction is aborting"
"transaction has been aborted"
Nothing in the event viewer.
I'm working on it being a priviledges problem! Unfortunately I have no experience with DTC so its a slow process.
-Jamie|||Jamie, is DTC running on the server machine, i.e. ABENTAH3D02?This can be found out through the following steps:
1. Open "Control Panel"
2. Open "Administrative Tools"
3. Open "Component Services"
4. Expand "Computer", right-click on "My Computer", switch to page "MSDTC"
Look for Service Control Status. Is it "Started"?|||
Runying Mao wrote:
Jamie, is DTC running on the server machine, i.e. ABENTAH3D02?This can be found out through the following steps:
1. Open "Control Panel"
2. Open "Administrative Tools"
3. Open "Component Services"
4. Expand "Computer", right-click on "My Computer", switch to page "MSDTC"Look for Service Control Status. Is it "Started"?
Yeah it is. First thing I checked 
Ok. Good.
Then in the same page "MSDTC", click "Security Configuration". There are "Allow Inbound" and "Allow Outbound" in Transaction Manager Communication. Are they both checked?
|||Ok. Good.
Then in the same page "MSDTC", click "Security Configuration". There are "Allow Inbound" and "Allow Outbound" in Transaction Manager Communication. Are they both checked?
Yes they are!
Can the choice of logon account affect it? Currently it is set to "NT Authority\NetworkService" on both machines.
I've also tried selecting "No authentication required" on the server. It didn't make any difference.
In fact, here are all the settings on the server (as taken from the event log):
MS DTC started with the following settings (OFF = 0 and ON = 1):
Security Configuration:
Network Administration of Transactions = 1,
Network Clients = 1,
Inbound Distributed Transactions using Native MSDTC Protocol = 1,
Outbound Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 0
Filtering Duplicate events = 1
And here are the local settings:
MS DTC started with the following settings:
Security Configuration (OFF = 0 and ON = 1):
Network Administration of Transactions = 1,
Network Clients = 1,
Inbound Distributed Transactions using Native MSDTC Protocol = 1,
Outbound Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 0
-Jamie|||IGNORE THIS!!!!
I've got it working. You've got to turn Windows Firewall off
http://support.microsoft.com/default.aspx/kb/839279
YEEESSSSS!!!!
(Very happy right now
-Jamie|||
This DTC seems not to work...
I have a package with a single data flow that copies a table from Informix to SQL Server. It finishes "all green", but ask me if I got any data on the target table...
Failure to run when using DTC
Does anyone hany any experience of using SSIS with MS DTC?
I have a package that runs successfully. When I switch it to using transactions (i.e. TransactionOption=Required) it fails. I get the following messages in the log:
-Starting distributed transaction for this container.
-Failed to acquire connection "<connection-manager-name>". Connection may not be configured correctly or you may not have the right permissions on this connection.
-Aborting the current distributed transaction.
I have a package that runs successfully. When I switch it to using transactions (i.e. TransactionOption=Required) it fails. I get the following messages in the log:
-Starting distributed transaction for this container.
-Failed to acquire connection "<connection-manager-name>". Connection may not be configured correctly or you may not have the right permissions on this connection.
-Aborting the current distributed transaction.
So - it seems it is having trouble enlisting that connection manager in a distributed transaction. My connection manager points at a SQL Server database on a different server to where I am running the package.
The connection string on the connection manager is: Data Source=ABENTAH3D02\DEVDBINSTANCE;Initial Catalog=CUESeerMetadata;Provider=SQLOLEDB.1;Integrated Security=SSPI;Auto Translate=False;
OK, so I kind of know where the error is but I don't know exactly what's causing it or how to go about diagnosing the problem. I don't have much experience of MS DTC although I have used it from SSIS in the past successfully.
Does anyone know the pre-requisites for using MS DTC?
How can I go about finding the problem?
Thanks
JamieThis sounds like a DTC issue with your permissions.
I'm not sure what the problem is, but here are a few things to check:
Are you able to enlist in a transaction on the remote machine where the SServer is? Run the package on that machine if you can. Is it successful there?
Is DTC started and running on both machines?
Do you have the priviledges to access the connection on the remote machine?
You might check the Windows Event Viewer on both machines to see if there are any messages that may give you more information about the problem.
HTH,
K|||I don't have the ability to run the package on the SQL box - or more accurately don't have time to install all the pre-reqs- but I'm pretyt sure that it IS a problem enlisting remote connections in the txn. i.e. I have a local connection in my package which enlists in the transaction without a problem.
In my local dtc trace log I have the following messages (many times)
"transaction got begun, description : '<NULL>"
"received request to abort the transaction from beginner"
"transaction is aborting"
"transaction has been aborted"
Nothing in the event viewer.
I'm working on it being a priviledges problem! Unfortunately I have no experience with DTC so its a slow process.
-Jamie|||Jamie, is DTC running on the server machine, i.e. ABENTAH3D02?This can be found out through the following steps:
1. Open "Control Panel"
2. Open "Administrative Tools"
3. Open "Component Services"
4. Expand "Computer", right-click on "My Computer", switch to page "MSDTC"
Look for Service Control Status. Is it "Started"?|||
Jamie, is DTC running on the server machine, i.e. ABENTAH3D02?This can be found out through the following steps:
1. Open "Control Panel"
2. Open "Administrative Tools"
3. Open "Component Services"
4. Expand "Computer", right-click on "My Computer", switch to page "MSDTC"Look for Service Control Status. Is it "Started"?
Yeah it is. First thing I checked
Ok. Good.
Then in the same page "MSDTC", click "Security Configuration". There are "Allow Inbound" and "Allow Outbound" in Transaction Manager Communication. Are they both checked?
|||Ok. Good.
Then in the same page "MSDTC", click "Security Configuration". There are "Allow Inbound" and "Allow Outbound" in Transaction Manager Communication. Are they both checked?
Yes they are!
Can the choice of logon account affect it? Currently it is set to "NT Authority\NetworkService" on both machines.
I've also tried selecting "No authentication required" on the server. It didn't make any difference.
In fact, here are all the settings on the server (as taken from the event log):
MS DTC started with the following settings (OFF = 0 and ON = 1):
Security Configuration:
Network Administration of Transactions = 1,
Network Clients = 1,
Inbound Distributed Transactions using Native MSDTC Protocol = 1,
Outbound Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 0
Filtering Duplicate events = 1
And here are the local settings:
MS DTC started with the following settings:
Security Configuration (OFF = 0 and ON = 1):
Network Administration of Transactions = 1,
Network Clients = 1,
Inbound Distributed Transactions using Native MSDTC Protocol = 1,
Outbound Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 0
-Jamie|||IGNORE THIS!!!!
I've got it working. You've got to turn Windows Firewall off
http://support.microsoft.com/default.aspx/kb/839279
YEEESSSSS!!!!
(Very happy right now
-Jamie|||
This DTC seems not to work...
I have a package with a single data flow that copies a table from Informix to SQL Server. It finishes "all green", but ask me if I got any data on the target table...
Failure to Remove Old Transaction Log Backups
I've just become the DBA. The origianl Maintenance Plan was setup to remove
old TRasact Log Backups. This has not worked in several months. Does anyone
have an idea why a working plan would fail? Everything appears to be set
correctly. Is there any advantage to placing optimimization in a seperate
plan from the backups?
Here is a post from Bill at MS that outlines the most common reasons for
this:
-- Log files don't delete --
http://support.microsoft.com/default...;en-us;Q303292
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Andrew J. Kelly SQL MVP
"mark_at_msb" <mark_at_msb@.discussions.microsoft.com> wrote in message
news:486897A4-7C19-4924-845D-0A724D4E4899@.microsoft.com...
> I've just become the DBA. The origianl Maintenance Plan was setup to
remove
> old TRasact Log Backups. This has not worked in several months. Does
anyone
> have an idea why a working plan would fail? Everything appears to be set
> correctly. Is there any advantage to placing optimimization in a seperate
> plan from the backups?
old TRasact Log Backups. This has not worked in several months. Does anyone
have an idea why a working plan would fail? Everything appears to be set
correctly. Is there any advantage to placing optimimization in a seperate
plan from the backups?
Here is a post from Bill at MS that outlines the most common reasons for
this:
-- Log files don't delete --
http://support.microsoft.com/default...;en-us;Q303292
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Andrew J. Kelly SQL MVP
"mark_at_msb" <mark_at_msb@.discussions.microsoft.com> wrote in message
news:486897A4-7C19-4924-845D-0A724D4E4899@.microsoft.com...
> I've just become the DBA. The origianl Maintenance Plan was setup to
remove
> old TRasact Log Backups. This has not worked in several months. Does
anyone
> have an idea why a working plan would fail? Everything appears to be set
> correctly. Is there any advantage to placing optimimization in a seperate
> plan from the backups?
failure to publish an indexed view logbased publication
i am trying to publish an indexed view logbased publication but I'm getting "must be a schema-bound view with at least a clustered index to be published as a log-based indexed view article."
The table has clustered index and the view is schema-bound.
this is the script for schemabinding
SETANSI_NULLSON
GO
SETQUOTED_IDENTIFIERON
GO
ALTERVIEW [nth].[musictracks1] withschemabinding
AS
SELECT autoid,idtrack,songname,singer,writer,composer,center
FROM nth.musictracks
GO
SETANSI_NULLSOFF
GO
SETQUOTED_IDENTIFIEROFF
GO
and this is for making the publication an indexed view logbased publication
execsp_addarticle
@.publication = N'lb_publication',
@.article = N'musictracks1',
@.source_owner = N'nth',
@.source_object = N'musictracks1',
@.type = N'indexed view logbased',
@.description =null,
@.creation_script =null,
@.pre_creation_cmd = N'none',
@.schema_option = 0x0000000008000001,
/* table name doesn’t have to be the same as view name */
@.destination_table = N'musictracks1',
@.destination_owner = N'nth'
GO
Any idea what is wrong?
Thanks,
Salah
If you want to use logbased for an indexed view, then you have to create a unique clustered index on the indexed view as the error msg indicates. if you just want to replicate the view schema, then you can used indexed view schema only.|||can you tell how can I create a unique clustered index on the indexed view ?
Thanks
|||you create an index on it like you do with any other table, for example:
create unqiue clustered index [uc_index1] on musictracks1 (autoid)
Failure to open SQL Server with given connect string
hello, Connect via an IP address
im working with VB 2005 and i have this error when triyng to connecting to the server database from my pocket pc application.
"Failure to open SQL Server with given connect string."
this is part of my code:
rdaOleDbConnectString = "Provider=sqloledb;Data Source=localhost;Persist Security Info=SSPI;User ID=id;Password=password;Initial Catalog=praia"
rdaUrl = "http://server/SqlMobile/sqlcesa30.dll"
localConnection = "Data Source=\My Documents\PraiaDB6.sdf"
If File.Exists("\My Documents\PraiaDB6.sdf") Then
File.Delete("\My Documents\PraiaDB6.sdf")
End If
Dim engine As New SqlCeEngine
engine.LocalConnectionString = localConnection
engine.CreateDatabase()
engine.Dispose()
MsgBox("DB Mobil empty created!")
'Init RDA Object
Dim rda As SqlCeRemoteDataAccess = Nothing
rda = New SqlCeRemoteDataAccess(rdaUrl, localConnection)
rda.InternetUrl = rdaUrl
rda.LocalConnectionString = localConnection
rda.Pull("Reserva", "select * from Reserva", rdaOleDbConnectString, RdaTrackOption.TrackingOn)
rda.Dispose()
the problem is in rda.Pull(...)
it can not connect to rdaOleDbConnectString
please help me
Thanks!
Jo?o
It is not likely that the datasource is "localhost", as this refers to the Pocket PC device, it should probably be the machine name or the ip address of the machine running SQL Server|||
Hi ErikEJ, thanks for the reply
i also tried the connectString with the machine name, like : Data Source=machinename; and i got the same error
also tried the ip adress of the server..
i dont understand whats supose the connect string look like...
anybody? thanks!
|||Can you connect via Internet Explorer on the device to: http://server/SqlMobile/sqlcesa30.dll
If that is not possible, this may be the cause of the error.
yes i can!
i read somewhere that when connecting via device (ppc) its need it to put ip adress instead server name.
i've found this link and im going to try now with this connecting string. ill post the result. thanks in advance for your help
http://www.connectionstrings.com/?carrier=sqlserver2005
Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;
Jo?o.
|||Same error...:(
|||solution:
rdaOleDbConnectString = "Provider=SQLOLEDB.1;Data Source=machineName,1433;Persist Security Info=False;Initial Catalog=praiateste;User ID=teste;Password=password;"
|||hello,
i was olso working on RDA sync and with the same connection string but in C# and i'm having the same problem the error message i'm getting is:
Failure to open SQL Server with given connect string. [connect string = Provider=SQLOLEDB.1;Data Source=localhost; Persist Security Info= True; User ID=MobileUser;Password=password;Initial Catalog=MobileDemo; ]
i'd tryed out all the alternatives posted on the forum but i'm still getting the same error the intial connection string was:
@."Provider=SQLOLEDB.1;Data Source=localhost;Persist Security Info=True;User ID=MobileUser;Password=password;Initial Catalog=MobileDemo";
hope you can help me thanks|||rdaOleDbConnectString = "Provider=SQLOLEDB.1;Data Source=machineName,1433;Persist Security Info=False;Initial Catalog=praiateste;User ID=teste;Password=password;"
try using the actual server name and open the port 1433 at SQL server
Failure to open SQL Server with given connect string
hello,Connect via an IP address
im working with VB 2005 and i have this error when triyng to connecting to the server database from my pocket pc application.
"Failure to open SQL Server with given connect string."
this is part of my code:
rdaOleDbConnectString = "Provider=sqloledb;Data Source=localhost;Persist Security Info=SSPI;User ID=id;Password=password;Initial Catalog=praia"
rdaUrl = "http://server/SqlMobile/sqlcesa30.dll"
localConnection = "Data Source=\My Documents\PraiaDB6.sdf"
If File.Exists("\My Documents\PraiaDB6.sdf") Then
File.Delete("\My Documents\PraiaDB6.sdf")
End If
Dim engine As New SqlCeEngine
engine.LocalConnectionString = localConnection
engine.CreateDatabase()
engine.Dispose()
MsgBox("DB Mobil empty created!")
'Init RDA Object
Dim rda As SqlCeRemoteDataAccess = Nothing
rda = New SqlCeRemoteDataAccess(rdaUrl, localConnection)
rda.InternetUrl = rdaUrl
rda.LocalConnectionString = localConnection
rda.Pull("Reserva", "select * from Reserva", rdaOleDbConnectString, RdaTrackOption.TrackingOn)
rda.Dispose()
the problem is in rda.Pull(...)
it can not connect to rdaOleDbConnectString
please help me
Thanks!
Jo?o
It is not likely that the datasource is "localhost", as this refers to the Pocket PC device, it should probably be the machine name or the ip address of the machine running SQL Server|||
Hi ErikEJ, thanks for the reply
i also tried the connectString with the machine name, like : Data Source=machinename; and i got the same error
also tried the ip adress of the server..
i dont understand whats supose the connect string look like...
anybody? thanks!
|||Can you connect via Internet Explorer on the device to: http://server/SqlMobile/sqlcesa30.dll
If that is not possible, this may be the cause of the error.
yes i can!
i read somewhere that when connecting via device (ppc) its need it to put ip adress instead server name.
i've found this link and im going to try now with this connecting string. ill post the result. thanks in advance for your help
http://www.connectionstrings.com/?carrier=sqlserver2005
Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;
Jo?o.
|||Same error...:(|||solution:
rdaOleDbConnectString = "Provider=SQLOLEDB.1;Data Source=machineName,1433;Persist Security Info=False;Initial Catalog=praiateste;User ID=teste;Password=password;"|||hello,
i was olso working on RDA sync and with the same connection string but in C# and i'm having the same problem the error message i'm getting is:
Failure to open SQL Server with given connect string. [connect string = Provider=SQLOLEDB.1;Data Source=localhost; Persist Security Info= True; User ID=MobileUser;Password=password;Initial Catalog=MobileDemo; ]
i'd tryed out all the alternatives posted on the forum but i'm still getting the same error the intial connection string was:
@."Provider=SQLOLEDB.1;Data Source=localhost;Persist Security Info=True;User ID=MobileUser;Password=password;Initial Catalog=MobileDemo";
hope you can help me thanks|||rdaOleDbConnectString = "Provider=SQLOLEDB.1;Data Source=machineName,1433;Persist Security Info=False;Initial Catalog=praiateste;User ID=teste;Password=password;"
try using the actual server name and open the port 1433 at SQL server
Subscribe to:
Posts (Atom)