I'm pretty new to SQL, and am running into a problem. I had setup a
Maintenance plan on one of my databases and the Transaction Log Backups are
not working. I'm not getting any feedback in the error on why they are not
working. This is the error that I get:
JOB RUN: 'Transaction Log Backup Job for DB Maintenance Plan 'CRMDEV DB
Maintenance Plan'' was run on 9/7/2006 at 5:30:00 PM
DURATION: 0 hours, 0 minutes, 0 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 2 (Schedule 1).
The last step to run was step 1 (Step 1).
Does anyone know what could be causing the error? I first thought it was
because of the account assigned to run the job, so I switched it from the
administrator to the SA account. But, still fails. Any suggestions on what
could be going on would be appreciated...My daily backups configured in the
Maintenance plan of the database are working though.
Thank you, Sara
Thanks!Saral6978 wrote:
> I'm pretty new to SQL, and am running into a problem. I had setup a
> Maintenance plan on one of my databases and the Transaction Log Backups are
> not working. I'm not getting any feedback in the error on why they are not
> working. This is the error that I get:
> JOB RUN: 'Transaction Log Backup Job for DB Maintenance Plan 'CRMDEV DB
> Maintenance Plan'' was run on 9/7/2006 at 5:30:00 PM
> DURATION: 0 hours, 0 minutes, 0 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 2 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Does anyone know what could be causing the error? I first thought it was
> because of the account assigned to run the job, so I switched it from the
> administrator to the SA account. But, still fails. Any suggestions on what
> could be going on would be appreciated...My daily backups configured in the
> Maintenance plan of the database are working though.
> Thank you, Sara
> Thanks!
>
>
Are you possibly trying to do a transaction log backup on a database
that is in Simple recovery mode?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I guess I'm not sure...how would I know that?
"Tracy McKibben" wrote:
> Saral6978 wrote:
> > I'm pretty new to SQL, and am running into a problem. I had setup a
> > Maintenance plan on one of my databases and the Transaction Log Backups are
> > not working. I'm not getting any feedback in the error on why they are not
> > working. This is the error that I get:
> >
> > JOB RUN: 'Transaction Log Backup Job for DB Maintenance Plan 'CRMDEV DB
> > Maintenance Plan'' was run on 9/7/2006 at 5:30:00 PM
> > DURATION: 0 hours, 0 minutes, 0 seconds
> > STATUS: Failed
> > MESSAGES: The job failed. The Job was invoked by Schedule 2 (Schedule 1).
> > The last step to run was step 1 (Step 1).
> >
> > Does anyone know what could be causing the error? I first thought it was
> > because of the account assigned to run the job, so I switched it from the
> > administrator to the SA account. But, still fails. Any suggestions on what
> > could be going on would be appreciated...My daily backups configured in the
> > Maintenance plan of the database are working though.
> >
> > Thank you, Sara
> >
> > Thanks!
> >
> >
> >
> Are you possibly trying to do a transaction log backup on a database
> that is in Simple recovery mode?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Saral6978 wrote:
> I guess I'm not sure...how would I know that?
>
Check the database properties of each database you're attempting to back
up. If the recovery model is "Simple", you can't (nor do you need to)
run a transaction log backup against that database. Consult Books
Online to learn what the various recovery models (Simple, Full,
Bulk-Logged) mean and what they offer.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thank you, Tracy. The recovery model IS Simple...I will be taking a 2day
course on SQL in the next month, so I'm sure that will help too. Thank you
so much for your input.
"Tracy McKibben" wrote:
> Saral6978 wrote:
> > I guess I'm not sure...how would I know that?
> >
> Check the database properties of each database you're attempting to back
> up. If the recovery model is "Simple", you can't (nor do you need to)
> run a transaction log backup against that database. Consult Books
> Online to learn what the various recovery models (Simple, Full,
> Bulk-Logged) mean and what they offer.
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Saral6978 wrote:
> Thank you, Tracy. The recovery model IS Simple...I will be taking a 2day
> course on SQL in the next month, so I'm sure that will help too. Thank you
> so much for your input.
>
No problem. I won't go into my rant about the maintenance plan wizards
allowing you to do this to yourself... After you finish your course,
you should learn how to write your own maintenance scripts without
relying on those wizards.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Aww, c'mon Tracy. We love your rants. ;)
To the poster, I found that the SQL Server Unleashed book is invaluable
as a resource. I picked it up on Ebay for under $30 and I use it
nearly every day.
Tracy McKibben wrote:
> Saral6978 wrote:
> > Thank you, Tracy. The recovery model IS Simple...I will be taking a 2day
> > course on SQL in the next month, so I'm sure that will help too. Thank you
> > so much for your input.
> >
> No problem. I won't go into my rant about the maintenance plan wizards
> allowing you to do this to yourself... After you finish your course,
> you should learn how to write your own maintenance scripts without
> relying on those wizards.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Showing posts with label setup. Show all posts
Showing posts with label setup. Show all posts
Friday, March 23, 2012
Issues with Transaction Log backups
I'm pretty new to SQL, and am running into a problem. I had setup a
Maintenance plan on one of my databases and the Transaction Log Backups are
not working. I'm not getting any feedback in the error on why they are not
working. This is the error that I get:
JOB RUN: 'Transaction Log Backup Job for DB Maintenance Plan 'CRMDEV DB
Maintenance Plan'' was run on 9/7/2006 at 5:30:00 PM
DURATION: 0 hours, 0 minutes, 0 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 2 (Schedule 1).
The last step to run was step 1 (Step 1).
Does anyone know what could be causing the error? I first thought it was
because of the account assigned to run the job, so I switched it from the
administrator to the SA account. But, still fails. Any suggestions on what
could be going on would be appreciated...My daily backups configured in the
Maintenance plan of the database are working though.
Thank you, Sara
Thanks!Saral6978 wrote:
> I'm pretty new to SQL, and am running into a problem. I had setup a
> Maintenance plan on one of my databases and the Transaction Log Backups ar
e
> not working. I'm not getting any feedback in the error on why they are no
t
> working. This is the error that I get:
> JOB RUN: 'Transaction Log Backup Job for DB Maintenance Plan 'CRMDEV DB
> Maintenance Plan'' was run on 9/7/2006 at 5:30:00 PM
> DURATION: 0 hours, 0 minutes, 0 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 2 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Does anyone know what could be causing the error? I first thought it was
> because of the account assigned to run the job, so I switched it from the
> administrator to the SA account. But, still fails. Any suggestions on wh
at
> could be going on would be appreciated...My daily backups configured in th
e
> Maintenance plan of the database are working though.
> Thank you, Sara
> Thanks!
>
>
Are you possibly trying to do a transaction log backup on a database
that is in Simple recovery mode?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I guess I'm not sure...how would I know that?
"Tracy McKibben" wrote:
> Saral6978 wrote:
> Are you possibly trying to do a transaction log backup on a database
> that is in Simple recovery mode?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Saral6978 wrote:
> I guess I'm not sure...how would I know that?
>
Check the database properties of each database you're attempting to back
up. If the recovery model is "Simple", you can't (nor do you need to)
run a transaction log backup against that database. Consult Books
Online to learn what the various recovery models (Simple, Full,
Bulk-Logged) mean and what they offer.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thank you, Tracy. The recovery model IS Simple...I will be taking a 2day
course on SQL in the next month, so I'm sure that will help too. Thank you
so much for your input.
"Tracy McKibben" wrote:
> Saral6978 wrote:
> Check the database properties of each database you're attempting to back
> up. If the recovery model is "Simple", you can't (nor do you need to)
> run a transaction log backup against that database. Consult Books
> Online to learn what the various recovery models (Simple, Full,
> Bulk-Logged) mean and what they offer.
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Saral6978 wrote:
> Thank you, Tracy. The recovery model IS Simple...I will be taking a 2day
> course on SQL in the next month, so I'm sure that will help too. Thank yo
u
> so much for your input.
>
No problem. I won't go into my rant about the maintenance plan wizards
allowing you to do this to yourself... After you finish your course,
you should learn how to write your own maintenance scripts without
relying on those wizards.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Aww, c'mon Tracy. We love your rants. ;)
To the poster, I found that the SQL Server Unleashed book is invaluable
as a resource. I picked it up on Ebay for under $30 and I use it
nearly every day.
Tracy McKibben wrote:
> Saral6978 wrote:
> No problem. I won't go into my rant about the maintenance plan wizards
> allowing you to do this to yourself... After you finish your course,
> you should learn how to write your own maintenance scripts without
> relying on those wizards.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Maintenance plan on one of my databases and the Transaction Log Backups are
not working. I'm not getting any feedback in the error on why they are not
working. This is the error that I get:
JOB RUN: 'Transaction Log Backup Job for DB Maintenance Plan 'CRMDEV DB
Maintenance Plan'' was run on 9/7/2006 at 5:30:00 PM
DURATION: 0 hours, 0 minutes, 0 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 2 (Schedule 1).
The last step to run was step 1 (Step 1).
Does anyone know what could be causing the error? I first thought it was
because of the account assigned to run the job, so I switched it from the
administrator to the SA account. But, still fails. Any suggestions on what
could be going on would be appreciated...My daily backups configured in the
Maintenance plan of the database are working though.
Thank you, Sara
Thanks!Saral6978 wrote:
> I'm pretty new to SQL, and am running into a problem. I had setup a
> Maintenance plan on one of my databases and the Transaction Log Backups ar
e
> not working. I'm not getting any feedback in the error on why they are no
t
> working. This is the error that I get:
> JOB RUN: 'Transaction Log Backup Job for DB Maintenance Plan 'CRMDEV DB
> Maintenance Plan'' was run on 9/7/2006 at 5:30:00 PM
> DURATION: 0 hours, 0 minutes, 0 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 2 (Schedule 1).
> The last step to run was step 1 (Step 1).
> Does anyone know what could be causing the error? I first thought it was
> because of the account assigned to run the job, so I switched it from the
> administrator to the SA account. But, still fails. Any suggestions on wh
at
> could be going on would be appreciated...My daily backups configured in th
e
> Maintenance plan of the database are working though.
> Thank you, Sara
> Thanks!
>
>
Are you possibly trying to do a transaction log backup on a database
that is in Simple recovery mode?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I guess I'm not sure...how would I know that?
"Tracy McKibben" wrote:
> Saral6978 wrote:
> Are you possibly trying to do a transaction log backup on a database
> that is in Simple recovery mode?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Saral6978 wrote:
> I guess I'm not sure...how would I know that?
>
Check the database properties of each database you're attempting to back
up. If the recovery model is "Simple", you can't (nor do you need to)
run a transaction log backup against that database. Consult Books
Online to learn what the various recovery models (Simple, Full,
Bulk-Logged) mean and what they offer.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thank you, Tracy. The recovery model IS Simple...I will be taking a 2day
course on SQL in the next month, so I'm sure that will help too. Thank you
so much for your input.
"Tracy McKibben" wrote:
> Saral6978 wrote:
> Check the database properties of each database you're attempting to back
> up. If the recovery model is "Simple", you can't (nor do you need to)
> run a transaction log backup against that database. Consult Books
> Online to learn what the various recovery models (Simple, Full,
> Bulk-Logged) mean and what they offer.
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Saral6978 wrote:
> Thank you, Tracy. The recovery model IS Simple...I will be taking a 2day
> course on SQL in the next month, so I'm sure that will help too. Thank yo
u
> so much for your input.
>
No problem. I won't go into my rant about the maintenance plan wizards
allowing you to do this to yourself... After you finish your course,
you should learn how to write your own maintenance scripts without
relying on those wizards.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Aww, c'mon Tracy. We love your rants. ;)
To the poster, I found that the SQL Server Unleashed book is invaluable
as a resource. I picked it up on Ebay for under $30 and I use it
nearly every day.
Tracy McKibben wrote:
> Saral6978 wrote:
> No problem. I won't go into my rant about the maintenance plan wizards
> allowing you to do this to yourself... After you finish your course,
> you should learn how to write your own maintenance scripts without
> relying on those wizards.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Wednesday, March 21, 2012
Issues with moving existing single production server setup to a New Cluster installation
According to the documentation the chosen Cluster name and IP address need
to be unused before installing the cluster. The IP address is not a problem,
but it will be a difficult task with the Cluster Name as the business
processes have many scripts, DTS packages, stored procedures and views that
have the production server name hard coded. There are many other servers
involved for updating and transferring data, so there was no way around it
and I would like to keep it that way if possible.
Therefore, my question is how can I reuse the production server name for the
cluster without jeopardising the Cluster installation ?
Hello,
You may need to rename the current production server name "ServerA" to
another name before installing virtual server. After that, you could reuse
the name "ServerA" as the virtual server name.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||You can't, however there are a lot of workarounds. If you are in an AD/DNS
envorinment, you can create an alias record that points the old name to the
new server. You can also set up a SQL alias on each client, but that is
generally harder.
Geoff N. Hiten
Microsoft SQL Server MVP
"GMG" <nospam@.nospam.com> wrote in message
news:uNQ4jV6dFHA.4060@.TK2MSFTNGP10.phx.gbl...
> According to the documentation the chosen Cluster name and IP address need
> to be unused before installing the cluster. The IP address is not a
> problem,
> but it will be a difficult task with the Cluster Name as the business
> processes have many scripts, DTS packages, stored procedures and views
> that
> have the production server name hard coded. There are many other servers
> involved for updating and transferring data, so there was no way around it
> and I would like to keep it that way if possible.
> Therefore, my question is how can I reuse the production server name for
> the
> cluster without jeopardising the Cluster installation ?
>
to be unused before installing the cluster. The IP address is not a problem,
but it will be a difficult task with the Cluster Name as the business
processes have many scripts, DTS packages, stored procedures and views that
have the production server name hard coded. There are many other servers
involved for updating and transferring data, so there was no way around it
and I would like to keep it that way if possible.
Therefore, my question is how can I reuse the production server name for the
cluster without jeopardising the Cluster installation ?
Hello,
You may need to rename the current production server name "ServerA" to
another name before installing virtual server. After that, you could reuse
the name "ServerA" as the virtual server name.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||You can't, however there are a lot of workarounds. If you are in an AD/DNS
envorinment, you can create an alias record that points the old name to the
new server. You can also set up a SQL alias on each client, but that is
generally harder.
Geoff N. Hiten
Microsoft SQL Server MVP
"GMG" <nospam@.nospam.com> wrote in message
news:uNQ4jV6dFHA.4060@.TK2MSFTNGP10.phx.gbl...
> According to the documentation the chosen Cluster name and IP address need
> to be unused before installing the cluster. The IP address is not a
> problem,
> but it will be a difficult task with the Cluster Name as the business
> processes have many scripts, DTS packages, stored procedures and views
> that
> have the production server name hard coded. There are many other servers
> involved for updating and transferring data, so there was no way around it
> and I would like to keep it that way if possible.
> Therefore, my question is how can I reuse the production server name for
> the
> cluster without jeopardising the Cluster installation ?
>
Monday, March 19, 2012
Issues with 2000 SP4 Upgrade.
I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I se
e
that the server starts but nothing happens......Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>|||Here is the last portion of the log.
....
....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directo
ry
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>
>
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I se
e
that the server starts but nothing happens......Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>|||Here is the last portion of the log.
....
....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directo
ry
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>
>
Issues with 2000 SP4 Upgrade.
I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I see
that the server starts but nothing happens......
Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>
|||Here is the last portion of the log.
.....
.....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>
>
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I see
that the server starts but nothing happens......
Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>
|||Here is the last portion of the log.
.....
.....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>
>
Issues with 2000 SP4 Upgrade.
I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I see
that the server starts but nothing happens......Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>|||Here is the last portion of the log.
....
....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
> >I have two servers now, which I am getting the same issue. The servers are
> > Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> > through copying files and then says "Initializing Server for Upgrade". I
> > see
> > that the server starts but nothing happens......
> >
> >
> >
>
>
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I see
that the server starts but nothing happens......Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>|||Here is the last portion of the log.
....
....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
> >I have two servers now, which I am getting the same issue. The servers are
> > Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> > through copying files and then says "Initializing Server for Upgrade". I
> > see
> > that the server starts but nothing happens......
> >
> >
> >
>
>
Friday, March 9, 2012
Issue with Page Breaking
I'm having an issue with Page Breaks within a SQL Report. The report
consisting of a single table with two groups. The report is setup to
insert a page break after the first group. Grand totals are calculated
in the footer of the main table. The report renders correctly in HTML.
When the report is exported to PDF, the Grand Totals section is render
on it's own page. The Grand Totals should render right after the last
group on the report. Is there a way in SQL Reporting to prevent the
last page break on a report?
Report Group Layout
Single table containing the the following:
Table Header
Group Header 1 - Page Break after group
Group Header 2
Detail Row -
Group Footer 2 - Contains Subtotals
Group Footer 1 - Contains Subtotals
Table Footer - Grand Total
Thanks
ChadHi, make sure that the page width and height is big enough for the 2nd page
to fit in. In layout, go to Report, Report Properties, Layout. Play around
with the Page Width and Page Height (increasing height most likely) until you
come right.
"Chad McKee" wrote:
> I'm having an issue with Page Breaks within a SQL Report. The report
> consisting of a single table with two groups. The report is setup to
> insert a page break after the first group. Grand totals are calculated
> in the footer of the main table. The report renders correctly in HTML.
> When the report is exported to PDF, the Grand Totals section is render
> on it's own page. The Grand Totals should render right after the last
> group on the report. Is there a way in SQL Reporting to prevent the
> last page break on a report?
>
> Report Group Layout
> Single table containing the the following:
> Table Header
> Group Header 1 - Page Break after group
> Group Header 2
> Detail Row -
> Group Footer 2 - Contains Subtotals
> Group Footer 1 - Contains Subtotals
> Table Footer - Grand Total
> Thanks
> Chad
>|||Hello,
I have checked the Page Width and Height. Everything fits within the
page size. If I remove the "Page Break after group" on the first group.
Everything renders without the extra page break. I think something is
wrong with the "Page Break after group" when rendering to PDF.
Thanks
Chad
jagberg wrote:
> Hi, make sure that the page width and height is big enough for the 2nd page
> to fit in. In layout, go to Report, Report Properties, Layout. Play around
> with the Page Width and Page Height (increasing height most likely) until you
> come right.
> "Chad McKee" wrote:
>
>>I'm having an issue with Page Breaks within a SQL Report. The report
>>consisting of a single table with two groups. The report is setup to
>>insert a page break after the first group. Grand totals are calculated
>>in the footer of the main table. The report renders correctly in HTML.
>> When the report is exported to PDF, the Grand Totals section is render
>>on it's own page. The Grand Totals should render right after the last
>>group on the report. Is there a way in SQL Reporting to prevent the
>>last page break on a report?
>>
>>Report Group Layout
>>Single table containing the the following:
>>Table Header
>> Group Header 1 - Page Break after group
>> Group Header 2
>> Detail Row -
>> Group Footer 2 - Contains Subtotals
>> Group Footer 1 - Contains Subtotals
>>Table Footer - Grand Total
>>Thanks
>>Chad|||This is a known limitation in our PDF renderer. I don't know of a
workaround, though someone more creative than me in this group might have
one up their sleeves. :)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chad McKee" <cmckee@.startech-comp.com> wrote in message
news:uTHDB67MFHA.1172@.TK2MSFTNGP12.phx.gbl...
> I'm having an issue with Page Breaks within a SQL Report. The report
> consisting of a single table with two groups. The report is setup to
> insert a page break after the first group. Grand totals are calculated in
> the footer of the main table. The report renders correctly in HTML. When
> the report is exported to PDF, the Grand Totals section is render on it's
> own page. The Grand Totals should render right after the last group on
> the report. Is there a way in SQL Reporting to prevent the last page
> break on a report?
>
> Report Group Layout
> Single table containing the the following:
> Table Header
> Group Header 1 - Page Break after group
> Group Header 2
> Detail Row -
> Group Footer 2 - Contains Subtotals
> Group Footer 1 - Contains Subtotals
> Table Footer - Grand Total
> Thanks
> Chad|||Hello Donovan,
Thanks for the reply. Do you know if/when this issue is going to be
fixed? Will the fix be included within the next Service Pack for
Reporting Services.
Thanks
Chad
Donovan Smith [MSFT] wrote:
> This is a known limitation in our PDF renderer. I don't know of a
> workaround, though someone more creative than me in this group might have
> one up their sleeves. :)
>|||Sorry, this won't make it into RS 2000 SP2 and is not currently on our plate
for Yukon (RS 2005).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chad McKee" <cmckee@.startech-comp.com> wrote in message
news:425ACA37.5090704@.startech-comp.com...
> Hello Donovan,
> Thanks for the reply. Do you know if/when this issue is going to be
> fixed? Will the fix be included within the next Service Pack for
> Reporting Services.
> Thanks
> Chad
> Donovan Smith [MSFT] wrote:
>> This is a known limitation in our PDF renderer. I don't know of a
>> workaround, though someone more creative than me in this group might have
>> one up their sleeves. :)|||Hi Donovan,
Do you know where I can find a workaround for this problem?
Thanks
Chad
Donovan Smith [MSFT] wrote:
> Sorry, this won't make it into RS 2000 SP2 and is not currently on our plate
> for Yukon (RS 2005).
>|||I am encountering a similar problem when displaying/printing a .pdf file from
a report containing a sub report. I have tried placing the sub report in both
rectangles and lists. I've adjusted all the margins (left, right, top and
bottom) to 0 in the sub report. There is a property called KeepTogether in a
list which I've set to both true and false without any impact. I can't seem
to find any property of any control that enables text in a sub report to span
multiple pages. I've also played with the page width and page height of the
sub report to no avail. Any help would be appreciated
"Chad McKee" wrote:
> Hi Donovan,
> Do you know where I can find a workaround for this problem?
> Thanks
> Chad
> Donovan Smith [MSFT] wrote:
> > Sorry, this won't make it into RS 2000 SP2 and is not currently on our plate
> > for Yukon (RS 2005).
> >
>|||Sorry, no. It's a limitation with our renderer. I don't have a creative
RDL solution though someone else in this group might.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chad McKee" <cmckee@.startech-comp.com> wrote in message
news:425AD6E0.9000201@.startech-comp.com...
> Hi Donovan,
> Do you know where I can find a workaround for this problem?
> Thanks
> Chad
> Donovan Smith [MSFT] wrote:
>> Sorry, this won't make it into RS 2000 SP2 and is not currently on our
>> plate for Yukon (RS 2005).|||Donovan with all due respect this issue should be easy to resolve. It's a
simple conditional check to render the table footer output on last page
following a group break.
I suspect that literally 1000's if not 10,000's of your customers are going
to be having the same issues since this is a very common scenario. If that's
justification enough for giving this a higher priority I don't know what is.
Send me the source code and I would be glad to fix... and I'm being serious!
Regards,
Kevin Weir
OmniLogic Systems
www.omnilogic.net
"Donovan Smith [MSFT]" wrote:
> Sorry, no. It's a limitation with our renderer. I don't have a creative
> RDL solution though someone else in this group might.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Chad McKee" <cmckee@.startech-comp.com> wrote in message
> news:425AD6E0.9000201@.startech-comp.com...
> > Hi Donovan,
> >
> > Do you know where I can find a workaround for this problem?
> >
> > Thanks
> > Chad
> >
> > Donovan Smith [MSFT] wrote:
> >> Sorry, this won't make it into RS 2000 SP2 and is not currently on our
> >> plate for Yukon (RS 2005).
> >>
>
>|||I agree with Kevin. Its a very common practice to have page breaks
after groups in a report containing a grand total. I just ran into the
issue again with a different report yesterday. This should be moved up
the priority list.
By the way. There is no way of working around the issue since you can't
place expressions on the page break property.
Thanks
Chad
Kevin Weir wrote:
> Donovan with all due respect this issue should be easy to resolve. It's a
> simple conditional check to render the table footer output on last page
> following a group break.
> I suspect that literally 1000's if not 10,000's of your customers are going
> to be having the same issues since this is a very common scenario. If that's
> justification enough for giving this a higher priority I don't know what is.
> Send me the source code and I would be glad to fix... and I'm being serious!
> Regards,
> Kevin Weir
> OmniLogic Systems
> www.omnilogic.net
>
> "Donovan Smith [MSFT]" wrote:
>
>>Sorry, no. It's a limitation with our renderer. I don't have a creative
>>RDL solution though someone else in this group might.
>>--
>>This posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>"Chad McKee" <cmckee@.startech-comp.com> wrote in message
>>news:425AD6E0.9000201@.startech-comp.com...
>>Hi Donovan,
>>Do you know where I can find a workaround for this problem?
>>Thanks
>>Chad
>>Donovan Smith [MSFT] wrote:
>>Sorry, this won't make it into RS 2000 SP2 and is not currently on our
>>plate for Yukon (RS 2005).
>>
>>|||I Thought I'd chime in with another vote for pushing this to the top of the
request heap. It is the main issue we've had with RS. We were going to
migrate all our reports from Crystal until we found grouping/page break
problems. I guess we'll keep writing Crystal / Business Objects until
Microsoft wakes up and realizes that this issue is a deal breaker. Even the
lowly Access Report Writer has this built in.
"Chad McKee" wrote:
> I agree with Kevin. Its a very common practice to have page breaks
> after groups in a report containing a grand total. I just ran into the
> issue again with a different report yesterday. This should be moved up
> the priority list.
> By the way. There is no way of working around the issue since you can't
> place expressions on the page break property.
> Thanks
> Chad
> Kevin Weir wrote:
> > Donovan with all due respect this issue should be easy to resolve. It's a
> > simple conditional check to render the table footer output on last page
> > following a group break.
> >
> > I suspect that literally 1000's if not 10,000's of your customers are going
> > to be having the same issues since this is a very common scenario. If that's
> > justification enough for giving this a higher priority I don't know what is.
> > Send me the source code and I would be glad to fix... and I'm being serious!
> >
> > Regards,
> > Kevin Weir
> > OmniLogic Systems
> > www.omnilogic.net
> >
> >
> >
> > "Donovan Smith [MSFT]" wrote:
> >
> >
> >>Sorry, no. It's a limitation with our renderer. I don't have a creative
> >>RDL solution though someone else in this group might.
> >>
> >>--
> >>This posting is provided "AS IS" with no warranties, and confers no rights.
> >>
> >>
> >>"Chad McKee" <cmckee@.startech-comp.com> wrote in message
> >>news:425AD6E0.9000201@.startech-comp.com...
> >>
> >>Hi Donovan,
> >>
> >>Do you know where I can find a workaround for this problem?
> >>
> >>Thanks
> >>Chad
> >>
> >>Donovan Smith [MSFT] wrote:
> >>
> >>Sorry, this won't make it into RS 2000 SP2 and is not currently on our
> >>plate for Yukon (RS 2005).
> >>
> >>
> >>
> >>
>|||Hi guys I have had this issue with this.
I have discoverd two work arounds for this
1. Put everything in the group headers and simply don't use the group
footers. The extra page breaks problem vanish. I rather have Totals in the
footers below the detail but this avoids the problem
OR
2. Select the Repeat Group Footers on each page option (which looks a
little crowded) but will give your report a little "running total" look to
it.The extra page breaks problem vanishs once again.
--
Message posted via http://www.sqlmonster.com|||We really shouldn't have to preform work arounds for functionally like
page breaking. These work arounds may work in some situations, but not
all. Here is another instant of breaking not working.
I have a report that contains four tables. The second to the last table
has the page break at start set to true. The report renders correctly
and inserts page breaks in the correct places.
Now I need to add an expression to the table's visible property to hide
the table on specific records. The expression works, but when the table
is visible the page break is ignored. I'm not sure why an expression on
the visible property causes the page breaks to stop working.
There seem to be issues with page breaks in general.
Thanks
Chad
Paul Mauriello via SQLMonster.com wrote:
> Hi guys I have had this issue with this.
> I have discoverd two work arounds for this
> 1. Put everything in the group headers and simply don't use the group
> footers. The extra page breaks problem vanish. I rather have Totals in the
> footers below the detail but this avoids the problem
> OR
> 2. Select the Repeat Group Footers on each page option (which looks a
> little crowded) but will give your report a little "running total" look to
> it.The extra page breaks problem vanishs once again.
>|||I use a workaround to do RunningValue counts over a group and then show
the GrandTotal on the last page when the RunningValue count for the
recordset equals the Count of all records in the recordset.
This is an unacceptable workaround for this product. Grand Totals
should have the "Keep Together" option with the last group. This is
seriously slowing down development.
consisting of a single table with two groups. The report is setup to
insert a page break after the first group. Grand totals are calculated
in the footer of the main table. The report renders correctly in HTML.
When the report is exported to PDF, the Grand Totals section is render
on it's own page. The Grand Totals should render right after the last
group on the report. Is there a way in SQL Reporting to prevent the
last page break on a report?
Report Group Layout
Single table containing the the following:
Table Header
Group Header 1 - Page Break after group
Group Header 2
Detail Row -
Group Footer 2 - Contains Subtotals
Group Footer 1 - Contains Subtotals
Table Footer - Grand Total
Thanks
ChadHi, make sure that the page width and height is big enough for the 2nd page
to fit in. In layout, go to Report, Report Properties, Layout. Play around
with the Page Width and Page Height (increasing height most likely) until you
come right.
"Chad McKee" wrote:
> I'm having an issue with Page Breaks within a SQL Report. The report
> consisting of a single table with two groups. The report is setup to
> insert a page break after the first group. Grand totals are calculated
> in the footer of the main table. The report renders correctly in HTML.
> When the report is exported to PDF, the Grand Totals section is render
> on it's own page. The Grand Totals should render right after the last
> group on the report. Is there a way in SQL Reporting to prevent the
> last page break on a report?
>
> Report Group Layout
> Single table containing the the following:
> Table Header
> Group Header 1 - Page Break after group
> Group Header 2
> Detail Row -
> Group Footer 2 - Contains Subtotals
> Group Footer 1 - Contains Subtotals
> Table Footer - Grand Total
> Thanks
> Chad
>|||Hello,
I have checked the Page Width and Height. Everything fits within the
page size. If I remove the "Page Break after group" on the first group.
Everything renders without the extra page break. I think something is
wrong with the "Page Break after group" when rendering to PDF.
Thanks
Chad
jagberg wrote:
> Hi, make sure that the page width and height is big enough for the 2nd page
> to fit in. In layout, go to Report, Report Properties, Layout. Play around
> with the Page Width and Page Height (increasing height most likely) until you
> come right.
> "Chad McKee" wrote:
>
>>I'm having an issue with Page Breaks within a SQL Report. The report
>>consisting of a single table with two groups. The report is setup to
>>insert a page break after the first group. Grand totals are calculated
>>in the footer of the main table. The report renders correctly in HTML.
>> When the report is exported to PDF, the Grand Totals section is render
>>on it's own page. The Grand Totals should render right after the last
>>group on the report. Is there a way in SQL Reporting to prevent the
>>last page break on a report?
>>
>>Report Group Layout
>>Single table containing the the following:
>>Table Header
>> Group Header 1 - Page Break after group
>> Group Header 2
>> Detail Row -
>> Group Footer 2 - Contains Subtotals
>> Group Footer 1 - Contains Subtotals
>>Table Footer - Grand Total
>>Thanks
>>Chad|||This is a known limitation in our PDF renderer. I don't know of a
workaround, though someone more creative than me in this group might have
one up their sleeves. :)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chad McKee" <cmckee@.startech-comp.com> wrote in message
news:uTHDB67MFHA.1172@.TK2MSFTNGP12.phx.gbl...
> I'm having an issue with Page Breaks within a SQL Report. The report
> consisting of a single table with two groups. The report is setup to
> insert a page break after the first group. Grand totals are calculated in
> the footer of the main table. The report renders correctly in HTML. When
> the report is exported to PDF, the Grand Totals section is render on it's
> own page. The Grand Totals should render right after the last group on
> the report. Is there a way in SQL Reporting to prevent the last page
> break on a report?
>
> Report Group Layout
> Single table containing the the following:
> Table Header
> Group Header 1 - Page Break after group
> Group Header 2
> Detail Row -
> Group Footer 2 - Contains Subtotals
> Group Footer 1 - Contains Subtotals
> Table Footer - Grand Total
> Thanks
> Chad|||Hello Donovan,
Thanks for the reply. Do you know if/when this issue is going to be
fixed? Will the fix be included within the next Service Pack for
Reporting Services.
Thanks
Chad
Donovan Smith [MSFT] wrote:
> This is a known limitation in our PDF renderer. I don't know of a
> workaround, though someone more creative than me in this group might have
> one up their sleeves. :)
>|||Sorry, this won't make it into RS 2000 SP2 and is not currently on our plate
for Yukon (RS 2005).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chad McKee" <cmckee@.startech-comp.com> wrote in message
news:425ACA37.5090704@.startech-comp.com...
> Hello Donovan,
> Thanks for the reply. Do you know if/when this issue is going to be
> fixed? Will the fix be included within the next Service Pack for
> Reporting Services.
> Thanks
> Chad
> Donovan Smith [MSFT] wrote:
>> This is a known limitation in our PDF renderer. I don't know of a
>> workaround, though someone more creative than me in this group might have
>> one up their sleeves. :)|||Hi Donovan,
Do you know where I can find a workaround for this problem?
Thanks
Chad
Donovan Smith [MSFT] wrote:
> Sorry, this won't make it into RS 2000 SP2 and is not currently on our plate
> for Yukon (RS 2005).
>|||I am encountering a similar problem when displaying/printing a .pdf file from
a report containing a sub report. I have tried placing the sub report in both
rectangles and lists. I've adjusted all the margins (left, right, top and
bottom) to 0 in the sub report. There is a property called KeepTogether in a
list which I've set to both true and false without any impact. I can't seem
to find any property of any control that enables text in a sub report to span
multiple pages. I've also played with the page width and page height of the
sub report to no avail. Any help would be appreciated
"Chad McKee" wrote:
> Hi Donovan,
> Do you know where I can find a workaround for this problem?
> Thanks
> Chad
> Donovan Smith [MSFT] wrote:
> > Sorry, this won't make it into RS 2000 SP2 and is not currently on our plate
> > for Yukon (RS 2005).
> >
>|||Sorry, no. It's a limitation with our renderer. I don't have a creative
RDL solution though someone else in this group might.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chad McKee" <cmckee@.startech-comp.com> wrote in message
news:425AD6E0.9000201@.startech-comp.com...
> Hi Donovan,
> Do you know where I can find a workaround for this problem?
> Thanks
> Chad
> Donovan Smith [MSFT] wrote:
>> Sorry, this won't make it into RS 2000 SP2 and is not currently on our
>> plate for Yukon (RS 2005).|||Donovan with all due respect this issue should be easy to resolve. It's a
simple conditional check to render the table footer output on last page
following a group break.
I suspect that literally 1000's if not 10,000's of your customers are going
to be having the same issues since this is a very common scenario. If that's
justification enough for giving this a higher priority I don't know what is.
Send me the source code and I would be glad to fix... and I'm being serious!
Regards,
Kevin Weir
OmniLogic Systems
www.omnilogic.net
"Donovan Smith [MSFT]" wrote:
> Sorry, no. It's a limitation with our renderer. I don't have a creative
> RDL solution though someone else in this group might.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Chad McKee" <cmckee@.startech-comp.com> wrote in message
> news:425AD6E0.9000201@.startech-comp.com...
> > Hi Donovan,
> >
> > Do you know where I can find a workaround for this problem?
> >
> > Thanks
> > Chad
> >
> > Donovan Smith [MSFT] wrote:
> >> Sorry, this won't make it into RS 2000 SP2 and is not currently on our
> >> plate for Yukon (RS 2005).
> >>
>
>|||I agree with Kevin. Its a very common practice to have page breaks
after groups in a report containing a grand total. I just ran into the
issue again with a different report yesterday. This should be moved up
the priority list.
By the way. There is no way of working around the issue since you can't
place expressions on the page break property.
Thanks
Chad
Kevin Weir wrote:
> Donovan with all due respect this issue should be easy to resolve. It's a
> simple conditional check to render the table footer output on last page
> following a group break.
> I suspect that literally 1000's if not 10,000's of your customers are going
> to be having the same issues since this is a very common scenario. If that's
> justification enough for giving this a higher priority I don't know what is.
> Send me the source code and I would be glad to fix... and I'm being serious!
> Regards,
> Kevin Weir
> OmniLogic Systems
> www.omnilogic.net
>
> "Donovan Smith [MSFT]" wrote:
>
>>Sorry, no. It's a limitation with our renderer. I don't have a creative
>>RDL solution though someone else in this group might.
>>--
>>This posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>"Chad McKee" <cmckee@.startech-comp.com> wrote in message
>>news:425AD6E0.9000201@.startech-comp.com...
>>Hi Donovan,
>>Do you know where I can find a workaround for this problem?
>>Thanks
>>Chad
>>Donovan Smith [MSFT] wrote:
>>Sorry, this won't make it into RS 2000 SP2 and is not currently on our
>>plate for Yukon (RS 2005).
>>
>>|||I Thought I'd chime in with another vote for pushing this to the top of the
request heap. It is the main issue we've had with RS. We were going to
migrate all our reports from Crystal until we found grouping/page break
problems. I guess we'll keep writing Crystal / Business Objects until
Microsoft wakes up and realizes that this issue is a deal breaker. Even the
lowly Access Report Writer has this built in.
"Chad McKee" wrote:
> I agree with Kevin. Its a very common practice to have page breaks
> after groups in a report containing a grand total. I just ran into the
> issue again with a different report yesterday. This should be moved up
> the priority list.
> By the way. There is no way of working around the issue since you can't
> place expressions on the page break property.
> Thanks
> Chad
> Kevin Weir wrote:
> > Donovan with all due respect this issue should be easy to resolve. It's a
> > simple conditional check to render the table footer output on last page
> > following a group break.
> >
> > I suspect that literally 1000's if not 10,000's of your customers are going
> > to be having the same issues since this is a very common scenario. If that's
> > justification enough for giving this a higher priority I don't know what is.
> > Send me the source code and I would be glad to fix... and I'm being serious!
> >
> > Regards,
> > Kevin Weir
> > OmniLogic Systems
> > www.omnilogic.net
> >
> >
> >
> > "Donovan Smith [MSFT]" wrote:
> >
> >
> >>Sorry, no. It's a limitation with our renderer. I don't have a creative
> >>RDL solution though someone else in this group might.
> >>
> >>--
> >>This posting is provided "AS IS" with no warranties, and confers no rights.
> >>
> >>
> >>"Chad McKee" <cmckee@.startech-comp.com> wrote in message
> >>news:425AD6E0.9000201@.startech-comp.com...
> >>
> >>Hi Donovan,
> >>
> >>Do you know where I can find a workaround for this problem?
> >>
> >>Thanks
> >>Chad
> >>
> >>Donovan Smith [MSFT] wrote:
> >>
> >>Sorry, this won't make it into RS 2000 SP2 and is not currently on our
> >>plate for Yukon (RS 2005).
> >>
> >>
> >>
> >>
>|||Hi guys I have had this issue with this.
I have discoverd two work arounds for this
1. Put everything in the group headers and simply don't use the group
footers. The extra page breaks problem vanish. I rather have Totals in the
footers below the detail but this avoids the problem
OR
2. Select the Repeat Group Footers on each page option (which looks a
little crowded) but will give your report a little "running total" look to
it.The extra page breaks problem vanishs once again.
--
Message posted via http://www.sqlmonster.com|||We really shouldn't have to preform work arounds for functionally like
page breaking. These work arounds may work in some situations, but not
all. Here is another instant of breaking not working.
I have a report that contains four tables. The second to the last table
has the page break at start set to true. The report renders correctly
and inserts page breaks in the correct places.
Now I need to add an expression to the table's visible property to hide
the table on specific records. The expression works, but when the table
is visible the page break is ignored. I'm not sure why an expression on
the visible property causes the page breaks to stop working.
There seem to be issues with page breaks in general.
Thanks
Chad
Paul Mauriello via SQLMonster.com wrote:
> Hi guys I have had this issue with this.
> I have discoverd two work arounds for this
> 1. Put everything in the group headers and simply don't use the group
> footers. The extra page breaks problem vanish. I rather have Totals in the
> footers below the detail but this avoids the problem
> OR
> 2. Select the Repeat Group Footers on each page option (which looks a
> little crowded) but will give your report a little "running total" look to
> it.The extra page breaks problem vanishs once again.
>|||I use a workaround to do RunningValue counts over a group and then show
the GrandTotal on the last page when the RunningValue count for the
recordset equals the Count of all records in the recordset.
This is an unacceptable workaround for this product. Grand Totals
should have the "Keep Together" option with the last group. This is
seriously slowing down development.
issue with linked server connecting to Access
Hi,
I have a linked server setup to connect to an access file from a filer
server. If I am on the server computer logged in using Windows NT
authencation, the connections works. However, if I use a native SQL login
(with sys admin rights) it gave the following error:
Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine can
not
open the file '\\filer-la03p\Mbs\Credit Mortgage
Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The linked server has security mapping as remote user:"admin" with password
null.
I also have noticed that if I connect to the server using EM from my desktop
using NT authencation, the error ocurrs as well. In this case I will say it
is a "double-hopping" issue. But why when using a native SQL account will
have a problem?
From my understanding when using linked server to connect to an access file,
it is using the service account that starts SQL Server. I had setup all
privilages required for the SQL Service account. And as I inicated earlier,
it connects ok if I am at the server using NT authencation to log in.
I rearch online and it seems like I am not the only one who has problems
with linked server for access from other computers. Unfortunately, nobody ha
s
given the resolutions that works for the requester.
Someone please help, we are a microsoft shop and everything is microsoft.
This problem has stopped our development for the business units a great deal
.
Our clients were just bought in to convert a lot of their stuff to SQL
Server. Now they are going to back off!
Thanks if someone can respond quickly.
ChristineA few suggestions:
--Make sure that the Access mdb (and mdw) reside on a file share that
the Windows account has read/write/delete ACLs on for the files and
folders.
--Make sure that the Access mdb is totally unsecured (check the owner
property -- it should NOT say 'unknown').
--Make sure that the login you are using is Admin with an empty string
(''), not null.
--Use filemon (www.sysinternals.com) to check to see if SQLS is
getting access to the files/folders.
FWIW, linked servers to Access are a real PITA. You'd have a much
easier time if you worked it the other way around, linking to SQL
Server from the Access .mdb.
--Mary
On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
C@.discussions.microsoft.com> wrote:
>Hi,
>I have a linked server setup to connect to an access file from a filer
>server. If I am on the server computer logged in using Windows NT
>authencation, the connections works. However, if I use a native SQL login
>(with sys admin rights) it gave the following error:
>Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine ca
nnot
>open the file '\\filer-la03p\Mbs\Credit Mortgage
>Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>The linked server has security mapping as remote user:"admin" with password
>null.
>I also have noticed that if I connect to the server using EM from my deskto
p
>using NT authencation, the error ocurrs as well. In this case I will say it
>is a "double-hopping" issue. But why when using a native SQL account will
>have a problem?
>From my understanding when using linked server to connect to an access file
,
>it is using the service account that starts SQL Server. I had setup all
>privilages required for the SQL Service account. And as I inicated earlier,
>it connects ok if I am at the server using NT authencation to log in.
>I rearch online and it seems like I am not the only one who has problems
>with linked server for access from other computers. Unfortunately, nobody h
as
>given the resolutions that works for the requester.
>Someone please help, we are a microsoft shop and everything is microsoft.
>This problem has stopped our development for the business units a great dea
l.
>Our clients were just bought in to convert a lot of their stuff to SQL
>Server. Now they are going to back off!
>Thanks if someone can respond quickly.
>Christine
>|||Mary,
Thanks for replying.
All the checklists you suggested are all there and correct, otherwise it
wouldn't have worked for some cases. It would just not work AT ALL.
I have found the fix for one issue now, but not another:
1. After I added the spn for the server to the AD account that started SQL
Server, I was able to connect from my desktop to the linked server through N
T
authencation.
Before this is only possible if I am at the server.
2. If I connect to SQL Server using SQL accounts, it still doesn't work on
either from the server or my desktop. So I was wondering if I login as 'sa',
what kind of security context that was verified against the file server on
the network? After it gets through the file system then the security check
will use "Admin" to open Access as specified in my linked server security
tab. But what happened before then?
I would assume either way (login as SQL or NT authencation to my SQL Server)
it should use the service account that starts SQL Server, but apparently it
is not the case.
I am really puzzled now...
"Mary Chipman" wrote:
> A few suggestions:
> --Make sure that the Access mdb (and mdw) reside on a file share that
> the Windows account has read/write/delete ACLs on for the files and
> folders.
> --Make sure that the Access mdb is totally unsecured (check the owner
> property -- it should NOT say 'unknown').
> --Make sure that the login you are using is Admin with an empty string
> (''), not null.
> --Use filemon (www.sysinternals.com) to check to see if SQLS is
> getting access to the files/folders.
> FWIW, linked servers to Access are a real PITA. You'd have a much
> easier time if you worked it the other way around, linking to SQL
> Server from the Access .mdb.
> --Mary
> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
> C@.discussions.microsoft.com> wrote:
>
>|||What did filemon show?
--Mary
On Thu, 14 Oct 2004 16:31:02 -0700, "Christine C"
<ChristineC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mary,
>Thanks for replying.
>All the checklists you suggested are all there and correct, otherwise it
>wouldn't have worked for some cases. It would just not work AT ALL.
>I have found the fix for one issue now, but not another:
>1. After I added the spn for the server to the AD account that started SQL
>Server, I was able to connect from my desktop to the linked server through
NT
>authencation.
>Before this is only possible if I am at the server.
>2. If I connect to SQL Server using SQL accounts, it still doesn't work on
>either from the server or my desktop. So I was wondering if I login as 'sa'
,
>what kind of security context that was verified against the file server on
>the network? After it gets through the file system then the security check
>will use "Admin" to open Access as specified in my linked server security
>tab. But what happened before then?
>I would assume either way (login as SQL or NT authencation to my SQL Server
)
>it should use the service account that starts SQL Server, but apparently it
>is not the case.
>I am really puzzled now...
>
>"Mary Chipman" wrote:
>
I have a linked server setup to connect to an access file from a filer
server. If I am on the server computer logged in using Windows NT
authencation, the connections works. However, if I use a native SQL login
(with sys admin rights) it gave the following error:
Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine can
not
open the file '\\filer-la03p\Mbs\Credit Mortgage
Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The linked server has security mapping as remote user:"admin" with password
null.
I also have noticed that if I connect to the server using EM from my desktop
using NT authencation, the error ocurrs as well. In this case I will say it
is a "double-hopping" issue. But why when using a native SQL account will
have a problem?
From my understanding when using linked server to connect to an access file,
it is using the service account that starts SQL Server. I had setup all
privilages required for the SQL Service account. And as I inicated earlier,
it connects ok if I am at the server using NT authencation to log in.
I rearch online and it seems like I am not the only one who has problems
with linked server for access from other computers. Unfortunately, nobody ha
s
given the resolutions that works for the requester.
Someone please help, we are a microsoft shop and everything is microsoft.
This problem has stopped our development for the business units a great deal
.
Our clients were just bought in to convert a lot of their stuff to SQL
Server. Now they are going to back off!
Thanks if someone can respond quickly.
ChristineA few suggestions:
--Make sure that the Access mdb (and mdw) reside on a file share that
the Windows account has read/write/delete ACLs on for the files and
folders.
--Make sure that the Access mdb is totally unsecured (check the owner
property -- it should NOT say 'unknown').
--Make sure that the login you are using is Admin with an empty string
(''), not null.
--Use filemon (www.sysinternals.com) to check to see if SQLS is
getting access to the files/folders.
FWIW, linked servers to Access are a real PITA. You'd have a much
easier time if you worked it the other way around, linking to SQL
Server from the Access .mdb.
--Mary
On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
C@.discussions.microsoft.com> wrote:
>Hi,
>I have a linked server setup to connect to an access file from a filer
>server. If I am on the server computer logged in using Windows NT
>authencation, the connections works. However, if I use a native SQL login
>(with sys admin rights) it gave the following error:
>Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine ca
nnot
>open the file '\\filer-la03p\Mbs\Credit Mortgage
>Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>The linked server has security mapping as remote user:"admin" with password
>null.
>I also have noticed that if I connect to the server using EM from my deskto
p
>using NT authencation, the error ocurrs as well. In this case I will say it
>is a "double-hopping" issue. But why when using a native SQL account will
>have a problem?
>From my understanding when using linked server to connect to an access file
,
>it is using the service account that starts SQL Server. I had setup all
>privilages required for the SQL Service account. And as I inicated earlier,
>it connects ok if I am at the server using NT authencation to log in.
>I rearch online and it seems like I am not the only one who has problems
>with linked server for access from other computers. Unfortunately, nobody h
as
>given the resolutions that works for the requester.
>Someone please help, we are a microsoft shop and everything is microsoft.
>This problem has stopped our development for the business units a great dea
l.
>Our clients were just bought in to convert a lot of their stuff to SQL
>Server. Now they are going to back off!
>Thanks if someone can respond quickly.
>Christine
>|||Mary,
Thanks for replying.
All the checklists you suggested are all there and correct, otherwise it
wouldn't have worked for some cases. It would just not work AT ALL.
I have found the fix for one issue now, but not another:
1. After I added the spn for the server to the AD account that started SQL
Server, I was able to connect from my desktop to the linked server through N
T
authencation.
Before this is only possible if I am at the server.
2. If I connect to SQL Server using SQL accounts, it still doesn't work on
either from the server or my desktop. So I was wondering if I login as 'sa',
what kind of security context that was verified against the file server on
the network? After it gets through the file system then the security check
will use "Admin" to open Access as specified in my linked server security
tab. But what happened before then?
I would assume either way (login as SQL or NT authencation to my SQL Server)
it should use the service account that starts SQL Server, but apparently it
is not the case.
I am really puzzled now...
"Mary Chipman" wrote:
> A few suggestions:
> --Make sure that the Access mdb (and mdw) reside on a file share that
> the Windows account has read/write/delete ACLs on for the files and
> folders.
> --Make sure that the Access mdb is totally unsecured (check the owner
> property -- it should NOT say 'unknown').
> --Make sure that the login you are using is Admin with an empty string
> (''), not null.
> --Use filemon (www.sysinternals.com) to check to see if SQLS is
> getting access to the files/folders.
> FWIW, linked servers to Access are a real PITA. You'd have a much
> easier time if you worked it the other way around, linking to SQL
> Server from the Access .mdb.
> --Mary
> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
> C@.discussions.microsoft.com> wrote:
>
>|||What did filemon show?
--Mary
On Thu, 14 Oct 2004 16:31:02 -0700, "Christine C"
<ChristineC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mary,
>Thanks for replying.
>All the checklists you suggested are all there and correct, otherwise it
>wouldn't have worked for some cases. It would just not work AT ALL.
>I have found the fix for one issue now, but not another:
>1. After I added the spn for the server to the AD account that started SQL
>Server, I was able to connect from my desktop to the linked server through
NT
>authencation.
>Before this is only possible if I am at the server.
>2. If I connect to SQL Server using SQL accounts, it still doesn't work on
>either from the server or my desktop. So I was wondering if I login as 'sa'
,
>what kind of security context that was verified against the file server on
>the network? After it gets through the file system then the security check
>will use "Admin" to open Access as specified in my linked server security
>tab. But what happened before then?
>I would assume either way (login as SQL or NT authencation to my SQL Server
)
>it should use the service account that starts SQL Server, but apparently it
>is not the case.
>I am really puzzled now...
>
>"Mary Chipman" wrote:
>
issue with linked server connecting to Access
Hi,
I have a linked server setup to connect to an access file from a filer
server. If I am on the server computer logged in using Windows NT
authencation, the connections works. However, if I use a native SQL login
(with sys admin rights) it gave the following error:
Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot
open the file '\\filer-la03p\Mbs\Credit Mortgage
Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The linked server has security mapping as remote user:"admin" with password
null.
I also have noticed that if I connect to the server using EM from my desktop
using NT authencation, the error ocurrs as well. In this case I will say it
is a "double-hopping" issue. But why when using a native SQL account will
have a problem?
From my understanding when using linked server to connect to an access file,
it is using the service account that starts SQL Server. I had setup all
privilages required for the SQL Service account. And as I inicated earlier,
it connects ok if I am at the server using NT authencation to log in.
I rearch online and it seems like I am not the only one who has problems
with linked server for access from other computers. Unfortunately, nobody has
given the resolutions that works for the requester.
Someone please help, we are a microsoft shop and everything is microsoft.
This problem has stopped our development for the business units a great deal.
Our clients were just bought in to convert a lot of their stuff to SQL
Server. Now they are going to back off!
Thanks if someone can respond quickly.
Christine
A few suggestions:
--Make sure that the Access mdb (and mdw) reside on a file share that
the Windows account has read/write/delete ACLs on for the files and
folders.
--Make sure that the Access mdb is totally unsecured (check the owner
property -- it should NOT say 'unknown').
--Make sure that the login you are using is Admin with an empty string
(''), not null.
--Use filemon (www.sysinternals.com) to check to see if SQLS is
getting access to the files/folders.
FWIW, linked servers to Access are a real PITA. You'd have a much
easier time if you worked it the other way around, linking to SQL
Server from the Access .mdb.
--Mary
On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
C@.discussions.microsoft.com> wrote:
>Hi,
>I have a linked server setup to connect to an access file from a filer
>server. If I am on the server computer logged in using Windows NT
>authencation, the connections works. However, if I use a native SQL login
>(with sys admin rights) it gave the following error:
>Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>open the file '\\filer-la03p\Mbs\Credit Mortgage
>Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>The linked server has security mapping as remote user:"admin" with password
>null.
>I also have noticed that if I connect to the server using EM from my desktop
>using NT authencation, the error ocurrs as well. In this case I will say it
>is a "double-hopping" issue. But why when using a native SQL account will
>have a problem?
>From my understanding when using linked server to connect to an access file,
>it is using the service account that starts SQL Server. I had setup all
>privilages required for the SQL Service account. And as I inicated earlier,
>it connects ok if I am at the server using NT authencation to log in.
>I rearch online and it seems like I am not the only one who has problems
>with linked server for access from other computers. Unfortunately, nobody has
>given the resolutions that works for the requester.
>Someone please help, we are a microsoft shop and everything is microsoft.
>This problem has stopped our development for the business units a great deal.
>Our clients were just bought in to convert a lot of their stuff to SQL
>Server. Now they are going to back off!
>Thanks if someone can respond quickly.
>Christine
>
|||Mary,
Thanks for replying.
All the checklists you suggested are all there and correct, otherwise it
wouldn't have worked for some cases. It would just not work AT ALL.
I have found the fix for one issue now, but not another:
1. After I added the spn for the server to the AD account that started SQL
Server, I was able to connect from my desktop to the linked server through NT
authencation.
Before this is only possible if I am at the server.
2. If I connect to SQL Server using SQL accounts, it still doesn't work on
either from the server or my desktop. So I was wondering if I login as 'sa',
what kind of security context that was verified against the file server on
the network? After it gets through the file system then the security check
will use "Admin" to open Access as specified in my linked server security
tab. But what happened before then?
I would assume either way (login as SQL or NT authencation to my SQL Server)
it should use the service account that starts SQL Server, but apparently it
is not the case.
I am really puzzled now...
"Mary Chipman" wrote:
> A few suggestions:
> --Make sure that the Access mdb (and mdw) reside on a file share that
> the Windows account has read/write/delete ACLs on for the files and
> folders.
> --Make sure that the Access mdb is totally unsecured (check the owner
> property -- it should NOT say 'unknown').
> --Make sure that the login you are using is Admin with an empty string
> (''), not null.
> --Use filemon (www.sysinternals.com) to check to see if SQLS is
> getting access to the files/folders.
> FWIW, linked servers to Access are a real PITA. You'd have a much
> easier time if you worked it the other way around, linking to SQL
> Server from the Access .mdb.
> --Mary
> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
> C@.discussions.microsoft.com> wrote:
>
>
|||What did filemon show?
--Mary
On Thu, 14 Oct 2004 16:31:02 -0700, "Christine C"
<ChristineC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mary,
>Thanks for replying.
>All the checklists you suggested are all there and correct, otherwise it
>wouldn't have worked for some cases. It would just not work AT ALL.
>I have found the fix for one issue now, but not another:
>1. After I added the spn for the server to the AD account that started SQL
>Server, I was able to connect from my desktop to the linked server through NT
>authencation.
>Before this is only possible if I am at the server.
>2. If I connect to SQL Server using SQL accounts, it still doesn't work on
>either from the server or my desktop. So I was wondering if I login as 'sa',
>what kind of security context that was verified against the file server on
>the network? After it gets through the file system then the security check
>will use "Admin" to open Access as specified in my linked server security
>tab. But what happened before then?
>I would assume either way (login as SQL or NT authencation to my SQL Server)
>it should use the service account that starts SQL Server, but apparently it
>is not the case.
>I am really puzzled now...
>
>"Mary Chipman" wrote:
I have a linked server setup to connect to an access file from a filer
server. If I am on the server computer logged in using Windows NT
authencation, the connections works. However, if I use a native SQL login
(with sys admin rights) it gave the following error:
Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot
open the file '\\filer-la03p\Mbs\Credit Mortgage
Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The linked server has security mapping as remote user:"admin" with password
null.
I also have noticed that if I connect to the server using EM from my desktop
using NT authencation, the error ocurrs as well. In this case I will say it
is a "double-hopping" issue. But why when using a native SQL account will
have a problem?
From my understanding when using linked server to connect to an access file,
it is using the service account that starts SQL Server. I had setup all
privilages required for the SQL Service account. And as I inicated earlier,
it connects ok if I am at the server using NT authencation to log in.
I rearch online and it seems like I am not the only one who has problems
with linked server for access from other computers. Unfortunately, nobody has
given the resolutions that works for the requester.
Someone please help, we are a microsoft shop and everything is microsoft.
This problem has stopped our development for the business units a great deal.
Our clients were just bought in to convert a lot of their stuff to SQL
Server. Now they are going to back off!
Thanks if someone can respond quickly.
Christine
A few suggestions:
--Make sure that the Access mdb (and mdw) reside on a file share that
the Windows account has read/write/delete ACLs on for the files and
folders.
--Make sure that the Access mdb is totally unsecured (check the owner
property -- it should NOT say 'unknown').
--Make sure that the login you are using is Admin with an empty string
(''), not null.
--Use filemon (www.sysinternals.com) to check to see if SQLS is
getting access to the files/folders.
FWIW, linked servers to Access are a real PITA. You'd have a much
easier time if you worked it the other way around, linking to SQL
Server from the Access .mdb.
--Mary
On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
C@.discussions.microsoft.com> wrote:
>Hi,
>I have a linked server setup to connect to an access file from a filer
>server. If I am on the server computer logged in using Windows NT
>authencation, the connections works. However, if I use a native SQL login
>(with sys admin rights) it gave the following error:
>Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>open the file '\\filer-la03p\Mbs\Credit Mortgage
>Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>The linked server has security mapping as remote user:"admin" with password
>null.
>I also have noticed that if I connect to the server using EM from my desktop
>using NT authencation, the error ocurrs as well. In this case I will say it
>is a "double-hopping" issue. But why when using a native SQL account will
>have a problem?
>From my understanding when using linked server to connect to an access file,
>it is using the service account that starts SQL Server. I had setup all
>privilages required for the SQL Service account. And as I inicated earlier,
>it connects ok if I am at the server using NT authencation to log in.
>I rearch online and it seems like I am not the only one who has problems
>with linked server for access from other computers. Unfortunately, nobody has
>given the resolutions that works for the requester.
>Someone please help, we are a microsoft shop and everything is microsoft.
>This problem has stopped our development for the business units a great deal.
>Our clients were just bought in to convert a lot of their stuff to SQL
>Server. Now they are going to back off!
>Thanks if someone can respond quickly.
>Christine
>
|||Mary,
Thanks for replying.
All the checklists you suggested are all there and correct, otherwise it
wouldn't have worked for some cases. It would just not work AT ALL.
I have found the fix for one issue now, but not another:
1. After I added the spn for the server to the AD account that started SQL
Server, I was able to connect from my desktop to the linked server through NT
authencation.
Before this is only possible if I am at the server.
2. If I connect to SQL Server using SQL accounts, it still doesn't work on
either from the server or my desktop. So I was wondering if I login as 'sa',
what kind of security context that was verified against the file server on
the network? After it gets through the file system then the security check
will use "Admin" to open Access as specified in my linked server security
tab. But what happened before then?
I would assume either way (login as SQL or NT authencation to my SQL Server)
it should use the service account that starts SQL Server, but apparently it
is not the case.
I am really puzzled now...
"Mary Chipman" wrote:
> A few suggestions:
> --Make sure that the Access mdb (and mdw) reside on a file share that
> the Windows account has read/write/delete ACLs on for the files and
> folders.
> --Make sure that the Access mdb is totally unsecured (check the owner
> property -- it should NOT say 'unknown').
> --Make sure that the login you are using is Admin with an empty string
> (''), not null.
> --Use filemon (www.sysinternals.com) to check to see if SQLS is
> getting access to the files/folders.
> FWIW, linked servers to Access are a real PITA. You'd have a much
> easier time if you worked it the other way around, linking to SQL
> Server from the Access .mdb.
> --Mary
> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
> C@.discussions.microsoft.com> wrote:
>
>
|||What did filemon show?
--Mary
On Thu, 14 Oct 2004 16:31:02 -0700, "Christine C"
<ChristineC@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mary,
>Thanks for replying.
>All the checklists you suggested are all there and correct, otherwise it
>wouldn't have worked for some cases. It would just not work AT ALL.
>I have found the fix for one issue now, but not another:
>1. After I added the spn for the server to the AD account that started SQL
>Server, I was able to connect from my desktop to the linked server through NT
>authencation.
>Before this is only possible if I am at the server.
>2. If I connect to SQL Server using SQL accounts, it still doesn't work on
>either from the server or my desktop. So I was wondering if I login as 'sa',
>what kind of security context that was verified against the file server on
>the network? After it gets through the file system then the security check
>will use "Admin" to open Access as specified in my linked server security
>tab. But what happened before then?
>I would assume either way (login as SQL or NT authencation to my SQL Server)
>it should use the service account that starts SQL Server, but apparently it
>is not the case.
>I am really puzzled now...
>
>"Mary Chipman" wrote:
issue with linked server connecting to Access
Hi,
I have a linked server setup to connect to an access file from a filer
server. If I am on the server computer logged in using Windows NT
authencation, the connections works. However, if I use a native SQL login
(with sys admin rights) it gave the following error:
Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot
open the file '\\filer-la03p\Mbs\Credit Mortgage
Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The linked server has security mapping as remote user:"admin" with password
null.
I also have noticed that if I connect to the server using EM from my desktop
using NT authencation, the error ocurrs as well. In this case I will say it
is a "double-hopping" issue. But why when using a native SQL account will
have a problem?
From my understanding when using linked server to connect to an access file,
it is using the service account that starts SQL Server. I had setup all
privilages required for the SQL Service account. And as I inicated earlier,
it connects ok if I am at the server using NT authencation to log in.
I rearch online and it seems like I am not the only one who has problems
with linked server for access from other computers. Unfortunately, nobody has
given the resolutions that works for the requester.
Someone please help, we are a microsoft shop and everything is microsoft.
This problem has stopped our development for the business units a great deal.
Our clients were just bought in to convert a lot of their stuff to SQL
Server. Now they are going to back off!
Thanks if someone can respond quickly.
ChristineA few suggestions:
--Make sure that the Access mdb (and mdw) reside on a file share that
the Windows account has read/write/delete ACLs on for the files and
folders.
--Make sure that the Access mdb is totally unsecured (check the owner
property -- it should NOT say 'unknown').
--Make sure that the login you are using is Admin with an empty string
(''), not null.
--Use filemon (www.sysinternals.com) to check to see if SQLS is
getting access to the files/folders.
FWIW, linked servers to Access are a real PITA. You'd have a much
easier time if you worked it the other way around, linking to SQL
Server from the Access .mdb.
--Mary
On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
C@.discussions.microsoft.com> wrote:
>Hi,
>I have a linked server setup to connect to an access file from a filer
>server. If I am on the server computer logged in using Windows NT
>authencation, the connections works. However, if I use a native SQL login
>(with sys admin rights) it gave the following error:
>Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>open the file '\\filer-la03p\Mbs\Credit Mortgage
>Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>The linked server has security mapping as remote user:"admin" with password
>null.
>I also have noticed that if I connect to the server using EM from my desktop
>using NT authencation, the error ocurrs as well. In this case I will say it
>is a "double-hopping" issue. But why when using a native SQL account will
>have a problem?
>From my understanding when using linked server to connect to an access file,
>it is using the service account that starts SQL Server. I had setup all
>privilages required for the SQL Service account. And as I inicated earlier,
>it connects ok if I am at the server using NT authencation to log in.
>I rearch online and it seems like I am not the only one who has problems
>with linked server for access from other computers. Unfortunately, nobody has
>given the resolutions that works for the requester.
>Someone please help, we are a microsoft shop and everything is microsoft.
>This problem has stopped our development for the business units a great deal.
>Our clients were just bought in to convert a lot of their stuff to SQL
>Server. Now they are going to back off!
>Thanks if someone can respond quickly.
>Christine
>|||Mary,
Thanks for replying.
All the checklists you suggested are all there and correct, otherwise it
wouldn't have worked for some cases. It would just not work AT ALL.
I have found the fix for one issue now, but not another:
1. After I added the spn for the server to the AD account that started SQL
Server, I was able to connect from my desktop to the linked server through NT
authencation.
Before this is only possible if I am at the server.
2. If I connect to SQL Server using SQL accounts, it still doesn't work on
either from the server or my desktop. So I was wondering if I login as 'sa',
what kind of security context that was verified against the file server on
the network? After it gets through the file system then the security check
will use "Admin" to open Access as specified in my linked server security
tab. But what happened before then?
I would assume either way (login as SQL or NT authencation to my SQL Server)
it should use the service account that starts SQL Server, but apparently it
is not the case.
I am really puzzled now...
"Mary Chipman" wrote:
> A few suggestions:
> --Make sure that the Access mdb (and mdw) reside on a file share that
> the Windows account has read/write/delete ACLs on for the files and
> folders.
> --Make sure that the Access mdb is totally unsecured (check the owner
> property -- it should NOT say 'unknown').
> --Make sure that the login you are using is Admin with an empty string
> (''), not null.
> --Use filemon (www.sysinternals.com) to check to see if SQLS is
> getting access to the files/folders.
> FWIW, linked servers to Access are a real PITA. You'd have a much
> easier time if you worked it the other way around, linking to SQL
> Server from the Access .mdb.
> --Mary
> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
> C@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I have a linked server setup to connect to an access file from a filer
> >server. If I am on the server computer logged in using Windows NT
> >authencation, the connections works. However, if I use a native SQL login
> >(with sys admin rights) it gave the following error:
> >
> >Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
> >
> >OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
> >
> >[OLE/DB provider returned message: The Microsoft Jet database engine cannot
> >open the file '\\filer-la03p\Mbs\Credit Mortgage
> >Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
> >exclusively by another user, or you need permission to view its data.]
> >
> >OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
> >IDBInitialize::Initialize returned 0x80004005: ].
> >
> >The linked server has security mapping as remote user:"admin" with password
> >null.
> >I also have noticed that if I connect to the server using EM from my desktop
> >using NT authencation, the error ocurrs as well. In this case I will say it
> >is a "double-hopping" issue. But why when using a native SQL account will
> >have a problem?
> >
> >From my understanding when using linked server to connect to an access file,
> >it is using the service account that starts SQL Server. I had setup all
> >privilages required for the SQL Service account. And as I inicated earlier,
> >it connects ok if I am at the server using NT authencation to log in.
> >
> >I rearch online and it seems like I am not the only one who has problems
> >with linked server for access from other computers. Unfortunately, nobody has
> >given the resolutions that works for the requester.
> >
> >Someone please help, we are a microsoft shop and everything is microsoft.
> >This problem has stopped our development for the business units a great deal.
> >Our clients were just bought in to convert a lot of their stuff to SQL
> >Server. Now they are going to back off!
> >
> >Thanks if someone can respond quickly.
> >
> >Christine
> >
>|||What did filemon show?
--Mary
On Thu, 14 Oct 2004 16:31:02 -0700, "Christine C"
<ChristineC@.discussions.microsoft.com> wrote:
>Mary,
>Thanks for replying.
>All the checklists you suggested are all there and correct, otherwise it
>wouldn't have worked for some cases. It would just not work AT ALL.
>I have found the fix for one issue now, but not another:
>1. After I added the spn for the server to the AD account that started SQL
>Server, I was able to connect from my desktop to the linked server through NT
>authencation.
>Before this is only possible if I am at the server.
>2. If I connect to SQL Server using SQL accounts, it still doesn't work on
>either from the server or my desktop. So I was wondering if I login as 'sa',
>what kind of security context that was verified against the file server on
>the network? After it gets through the file system then the security check
>will use "Admin" to open Access as specified in my linked server security
>tab. But what happened before then?
>I would assume either way (login as SQL or NT authencation to my SQL Server)
>it should use the service account that starts SQL Server, but apparently it
>is not the case.
>I am really puzzled now...
>
>"Mary Chipman" wrote:
>> A few suggestions:
>> --Make sure that the Access mdb (and mdw) reside on a file share that
>> the Windows account has read/write/delete ACLs on for the files and
>> folders.
>> --Make sure that the Access mdb is totally unsecured (check the owner
>> property -- it should NOT say 'unknown').
>> --Make sure that the login you are using is Admin with an empty string
>> (''), not null.
>> --Use filemon (www.sysinternals.com) to check to see if SQLS is
>> getting access to the files/folders.
>> FWIW, linked servers to Access are a real PITA. You'd have a much
>> easier time if you worked it the other way around, linking to SQL
>> Server from the Access .mdb.
>> --Mary
>> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
>> C@.discussions.microsoft.com> wrote:
>> >Hi,
>> >
>> >I have a linked server setup to connect to an access file from a filer
>> >server. If I am on the server computer logged in using Windows NT
>> >authencation, the connections works. However, if I use a native SQL login
>> >(with sys admin rights) it gave the following error:
>> >
>> >Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>> >
>> >OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>> >
>> >[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>> >open the file '\\filer-la03p\Mbs\Credit Mortgage
>> >Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>> >exclusively by another user, or you need permission to view its data.]
>> >
>> >OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>> >IDBInitialize::Initialize returned 0x80004005: ].
>> >
>> >The linked server has security mapping as remote user:"admin" with password
>> >null.
>> >I also have noticed that if I connect to the server using EM from my desktop
>> >using NT authencation, the error ocurrs as well. In this case I will say it
>> >is a "double-hopping" issue. But why when using a native SQL account will
>> >have a problem?
>> >
>> >From my understanding when using linked server to connect to an access file,
>> >it is using the service account that starts SQL Server. I had setup all
>> >privilages required for the SQL Service account. And as I inicated earlier,
>> >it connects ok if I am at the server using NT authencation to log in.
>> >
>> >I rearch online and it seems like I am not the only one who has problems
>> >with linked server for access from other computers. Unfortunately, nobody has
>> >given the resolutions that works for the requester.
>> >
>> >Someone please help, we are a microsoft shop and everything is microsoft.
>> >This problem has stopped our development for the business units a great deal.
>> >Our clients were just bought in to convert a lot of their stuff to SQL
>> >Server. Now they are going to back off!
>> >
>> >Thanks if someone can respond quickly.
>> >
>> >Christine
>> >
>>
I have a linked server setup to connect to an access file from a filer
server. If I am on the server computer logged in using Windows NT
authencation, the connections works. However, if I use a native SQL login
(with sys admin rights) it gave the following error:
Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
[OLE/DB provider returned message: The Microsoft Jet database engine cannot
open the file '\\filer-la03p\Mbs\Credit Mortgage
Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
exclusively by another user, or you need permission to view its data.]
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
IDBInitialize::Initialize returned 0x80004005: ].
The linked server has security mapping as remote user:"admin" with password
null.
I also have noticed that if I connect to the server using EM from my desktop
using NT authencation, the error ocurrs as well. In this case I will say it
is a "double-hopping" issue. But why when using a native SQL account will
have a problem?
From my understanding when using linked server to connect to an access file,
it is using the service account that starts SQL Server. I had setup all
privilages required for the SQL Service account. And as I inicated earlier,
it connects ok if I am at the server using NT authencation to log in.
I rearch online and it seems like I am not the only one who has problems
with linked server for access from other computers. Unfortunately, nobody has
given the resolutions that works for the requester.
Someone please help, we are a microsoft shop and everything is microsoft.
This problem has stopped our development for the business units a great deal.
Our clients were just bought in to convert a lot of their stuff to SQL
Server. Now they are going to back off!
Thanks if someone can respond quickly.
ChristineA few suggestions:
--Make sure that the Access mdb (and mdw) reside on a file share that
the Windows account has read/write/delete ACLs on for the files and
folders.
--Make sure that the Access mdb is totally unsecured (check the owner
property -- it should NOT say 'unknown').
--Make sure that the login you are using is Admin with an empty string
(''), not null.
--Use filemon (www.sysinternals.com) to check to see if SQLS is
getting access to the files/folders.
FWIW, linked servers to Access are a real PITA. You'd have a much
easier time if you worked it the other way around, linking to SQL
Server from the Access .mdb.
--Mary
On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
C@.discussions.microsoft.com> wrote:
>Hi,
>I have a linked server setup to connect to an access file from a filer
>server. If I am on the server computer logged in using Windows NT
>authencation, the connections works. However, if I use a native SQL login
>(with sys admin rights) it gave the following error:
>Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>open the file '\\filer-la03p\Mbs\Credit Mortgage
>Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>exclusively by another user, or you need permission to view its data.]
>OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>IDBInitialize::Initialize returned 0x80004005: ].
>The linked server has security mapping as remote user:"admin" with password
>null.
>I also have noticed that if I connect to the server using EM from my desktop
>using NT authencation, the error ocurrs as well. In this case I will say it
>is a "double-hopping" issue. But why when using a native SQL account will
>have a problem?
>From my understanding when using linked server to connect to an access file,
>it is using the service account that starts SQL Server. I had setup all
>privilages required for the SQL Service account. And as I inicated earlier,
>it connects ok if I am at the server using NT authencation to log in.
>I rearch online and it seems like I am not the only one who has problems
>with linked server for access from other computers. Unfortunately, nobody has
>given the resolutions that works for the requester.
>Someone please help, we are a microsoft shop and everything is microsoft.
>This problem has stopped our development for the business units a great deal.
>Our clients were just bought in to convert a lot of their stuff to SQL
>Server. Now they are going to back off!
>Thanks if someone can respond quickly.
>Christine
>|||Mary,
Thanks for replying.
All the checklists you suggested are all there and correct, otherwise it
wouldn't have worked for some cases. It would just not work AT ALL.
I have found the fix for one issue now, but not another:
1. After I added the spn for the server to the AD account that started SQL
Server, I was able to connect from my desktop to the linked server through NT
authencation.
Before this is only possible if I am at the server.
2. If I connect to SQL Server using SQL accounts, it still doesn't work on
either from the server or my desktop. So I was wondering if I login as 'sa',
what kind of security context that was verified against the file server on
the network? After it gets through the file system then the security check
will use "Admin" to open Access as specified in my linked server security
tab. But what happened before then?
I would assume either way (login as SQL or NT authencation to my SQL Server)
it should use the service account that starts SQL Server, but apparently it
is not the case.
I am really puzzled now...
"Mary Chipman" wrote:
> A few suggestions:
> --Make sure that the Access mdb (and mdw) reside on a file share that
> the Windows account has read/write/delete ACLs on for the files and
> folders.
> --Make sure that the Access mdb is totally unsecured (check the owner
> property -- it should NOT say 'unknown').
> --Make sure that the login you are using is Admin with an empty string
> (''), not null.
> --Use filemon (www.sysinternals.com) to check to see if SQLS is
> getting access to the files/folders.
> FWIW, linked servers to Access are a real PITA. You'd have a much
> easier time if you worked it the other way around, linking to SQL
> Server from the Access .mdb.
> --Mary
> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
> C@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I have a linked server setup to connect to an access file from a filer
> >server. If I am on the server computer logged in using Windows NT
> >authencation, the connections works. However, if I use a native SQL login
> >(with sys admin rights) it gave the following error:
> >
> >Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
> >
> >OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
> >
> >[OLE/DB provider returned message: The Microsoft Jet database engine cannot
> >open the file '\\filer-la03p\Mbs\Credit Mortgage
> >Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
> >exclusively by another user, or you need permission to view its data.]
> >
> >OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
> >IDBInitialize::Initialize returned 0x80004005: ].
> >
> >The linked server has security mapping as remote user:"admin" with password
> >null.
> >I also have noticed that if I connect to the server using EM from my desktop
> >using NT authencation, the error ocurrs as well. In this case I will say it
> >is a "double-hopping" issue. But why when using a native SQL account will
> >have a problem?
> >
> >From my understanding when using linked server to connect to an access file,
> >it is using the service account that starts SQL Server. I had setup all
> >privilages required for the SQL Service account. And as I inicated earlier,
> >it connects ok if I am at the server using NT authencation to log in.
> >
> >I rearch online and it seems like I am not the only one who has problems
> >with linked server for access from other computers. Unfortunately, nobody has
> >given the resolutions that works for the requester.
> >
> >Someone please help, we are a microsoft shop and everything is microsoft.
> >This problem has stopped our development for the business units a great deal.
> >Our clients were just bought in to convert a lot of their stuff to SQL
> >Server. Now they are going to back off!
> >
> >Thanks if someone can respond quickly.
> >
> >Christine
> >
>|||What did filemon show?
--Mary
On Thu, 14 Oct 2004 16:31:02 -0700, "Christine C"
<ChristineC@.discussions.microsoft.com> wrote:
>Mary,
>Thanks for replying.
>All the checklists you suggested are all there and correct, otherwise it
>wouldn't have worked for some cases. It would just not work AT ALL.
>I have found the fix for one issue now, but not another:
>1. After I added the spn for the server to the AD account that started SQL
>Server, I was able to connect from my desktop to the linked server through NT
>authencation.
>Before this is only possible if I am at the server.
>2. If I connect to SQL Server using SQL accounts, it still doesn't work on
>either from the server or my desktop. So I was wondering if I login as 'sa',
>what kind of security context that was verified against the file server on
>the network? After it gets through the file system then the security check
>will use "Admin" to open Access as specified in my linked server security
>tab. But what happened before then?
>I would assume either way (login as SQL or NT authencation to my SQL Server)
>it should use the service account that starts SQL Server, but apparently it
>is not the case.
>I am really puzzled now...
>
>"Mary Chipman" wrote:
>> A few suggestions:
>> --Make sure that the Access mdb (and mdw) reside on a file share that
>> the Windows account has read/write/delete ACLs on for the files and
>> folders.
>> --Make sure that the Access mdb is totally unsecured (check the owner
>> property -- it should NOT say 'unknown').
>> --Make sure that the login you are using is Admin with an empty string
>> (''), not null.
>> --Use filemon (www.sysinternals.com) to check to see if SQLS is
>> getting access to the files/folders.
>> FWIW, linked servers to Access are a real PITA. You'd have a much
>> easier time if you worked it the other way around, linking to SQL
>> Server from the Access .mdb.
>> --Mary
>> On Thu, 14 Oct 2004 11:35:04 -0700, "Christine C" <Christine
>> C@.discussions.microsoft.com> wrote:
>> >Hi,
>> >
>> >I have a linked server setup to connect to an access file from a filer
>> >server. If I am on the server computer logged in using Windows NT
>> >authencation, the connections works. However, if I use a native SQL login
>> >(with sys admin rights) it gave the following error:
>> >
>> >Server: Msg 7399, Level 16, State 1, Procedure sp_tables_ex, Line 20
>> >
>> >OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error.
>> >
>> >[OLE/DB provider returned message: The Microsoft Jet database engine cannot
>> >open the file '\\filer-la03p\Mbs\Credit Mortgage
>> >Group\Programs\Databases\Credit MBS Data.mdb'. It is already opened
>> >exclusively by another user, or you need permission to view its data.]
>> >
>> >OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0'
>> >IDBInitialize::Initialize returned 0x80004005: ].
>> >
>> >The linked server has security mapping as remote user:"admin" with password
>> >null.
>> >I also have noticed that if I connect to the server using EM from my desktop
>> >using NT authencation, the error ocurrs as well. In this case I will say it
>> >is a "double-hopping" issue. But why when using a native SQL account will
>> >have a problem?
>> >
>> >From my understanding when using linked server to connect to an access file,
>> >it is using the service account that starts SQL Server. I had setup all
>> >privilages required for the SQL Service account. And as I inicated earlier,
>> >it connects ok if I am at the server using NT authencation to log in.
>> >
>> >I rearch online and it seems like I am not the only one who has problems
>> >with linked server for access from other computers. Unfortunately, nobody has
>> >given the resolutions that works for the requester.
>> >
>> >Someone please help, we are a microsoft shop and everything is microsoft.
>> >This problem has stopped our development for the business units a great deal.
>> >Our clients were just bought in to convert a lot of their stuff to SQL
>> >Server. Now they are going to back off!
>> >
>> >Thanks if someone can respond quickly.
>> >
>> >Christine
>> >
>>
Issue with job run setup in Enterprise Manager
Hello All,
I have a job that consist of over 120 steps. I was able to setup it in Enter
prise Manager and run it. However, the job history can only show display 100
job steps 20 other job steps were missing. Is there a limit set on sysjobhi
story table or am I looking
at the wrong table? Please advice.
Thanks.
DavidThat is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David
I have a job that consist of over 120 steps. I was able to setup it in Enter
prise Manager and run it. However, the job history can only show display 100
job steps 20 other job steps were missing. Is there a limit set on sysjobhi
story table or am I looking
at the wrong table? Please advice.
Thanks.
DavidThat is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David
Issue with job run setup in Enterprise Manager
Hello All,
I have a job that consist of over 120 steps. I was able to setup it in Enterprise Manager and run it. However, the job history can only show display 100 job steps 20 other job steps were missing. Is there a limit set on sysjobhistory table or am I looking
at the wrong table? Please advice.
Thanks.
David
That is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David
I have a job that consist of over 120 steps. I was able to setup it in Enterprise Manager and run it. However, the job history can only show display 100 job steps 20 other job steps were missing. Is there a limit set on sysjobhistory table or am I looking
at the wrong table? Please advice.
Thanks.
David
That is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David
Issue with job run setup in Enterprise Manager
Hello All
I have a job that consist of over 120 steps. I was able to setup it in Enterprise Manager and run it. However, the job history can only show display 100 job steps 20 other job steps were missing. Is there a limit set on sysjobhistory table or am I looking at the wrong table? Please advice
Thanks
DavidThat is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David
I have a job that consist of over 120 steps. I was able to setup it in Enterprise Manager and run it. However, the job history can only show display 100 job steps 20 other job steps were missing. Is there a limit set on sysjobhistory table or am I looking at the wrong table? Please advice
Thanks
DavidThat is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David
Subscribe to:
Posts (Atom)