After changing the startup parameters and moving the database we are unable
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.
HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.
|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/de...servr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.
|||Error 5 is access denied. Make sure that the SQL Server service account has permissions to the file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.
|||Moved it based on Microsoft articel changed startup parameters and only moved
the master.mdf so I only changed that parameter.
"doller" wrote:
> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
>
|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters back
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/de...servr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
[vbcol=seagreen]
> Used this article to move the database also tried to start it from a command
> prompt and would not start. Also tried to change the startup parameters back
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and tried
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved[vbcol=seagreen]
> the master.mdf so I only changed that parameter.
> "doller" wrote:
unable[vbcol=seagreen]
log is[vbcol=seagreen]
|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...[vbcol=seagreen]
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:
Showing posts with label message. Show all posts
Showing posts with label message. Show all posts
Friday, March 23, 2012
Moved master db and now cannot start SQL
After changing the startup parameters and moving the database we are unable
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/d...>
rvr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Error 5 is access denied. Make sure that the SQL Server service account has
permissions to the file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Moved it based on Microsoft articel changed startup parameters and only move
d
the master.mdf so I only changed that parameter.
"doller" wrote:
> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
>|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters bac
k
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/d...
servr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
>|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
[vbcol=seagreen]
> Used this article to move the database also tried to start it from a comma
nd
> prompt and would not start. Also tried to change the startup parameters b
ack
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and trie
d
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
>|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved[vbcol=seagreen]
> the master.mdf so I only changed that parameter.
> "doller" wrote:
>
unable[vbcol=seagreen]
log is[vbcol=seagreen]|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...[vbcol=seagreen]
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:
>
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/d...>
rvr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Error 5 is access denied. Make sure that the SQL Server service account has
permissions to the file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Moved it based on Microsoft articel changed startup parameters and only move
d
the master.mdf so I only changed that parameter.
"doller" wrote:
> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
>|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters bac
k
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/d...
servr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
>|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
[vbcol=seagreen]
> Used this article to move the database also tried to start it from a comma
nd
> prompt and would not start. Also tried to change the startup parameters b
ack
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and trie
d
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
>|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved[vbcol=seagreen]
> the master.mdf so I only changed that parameter.
> "doller" wrote:
>
unable[vbcol=seagreen]
log is[vbcol=seagreen]|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...[vbcol=seagreen]
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:
>
Moved master db and now cannot start SQL
After changing the startup parameters and moving the database we are unable
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Error 5 is access denied. Make sure that the SQL Server service account has permissions to the file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Moved it based on Microsoft articel changed startup parameters and only moved
the master.mdf so I only changed that parameter.
"doller" wrote:
> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
> > After changing the startup parameters and moving the database we are unable
> > to start SQL. The error message we are getting in the application log is
> > that the initconfig: (error 5) access denied to g:\sqldata.
>|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters back
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
> > After changing the startup parameters and moving the database we are unable
> > to start SQL. The error message we are getting in the application log is
> > that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
> Used this article to move the database also tried to start it from a command
> prompt and would not start. Also tried to change the startup parameters back
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and tried
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
> > Hi
> >
> > This article descibes how to move your master database
> > http://support.microsoft.com/kb/224071/EN-US/
> >
> > You may want to try starting SQL Server from the command prompt
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
> > with the correct parameters (possibly with -f also!) and also making sure
> > that the permissions for the directories being used are correct.
> >
> > You can not use a mapped network drive for your database files.
> >
> > John
> >
> > "Ray Skweres" wrote:
> >
> > > After changing the startup parameters and moving the database we are unable
> > > to start SQL. The error message we are getting in the application log is
> > > that the initconfig: (error 5) access denied to g:\sqldata.|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved
> the master.mdf so I only changed that parameter.
> "doller" wrote:
> > HI,
> > How u moved the database and what parameter u have changed.
> >
> > from
> > killer
> >
> >
> > Ray Skweres wrote:
> > > After changing the startup parameters and moving the database we are
unable
> > > to start SQL. The error message we are getting in the application
log is
> > > that the initconfig: (error 5) access denied to g:\sqldata.
> >
> >|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:
>> Used this article to move the database also tried to start it from a
>> command
>> prompt and would not start. Also tried to change the startup parameters
>> back
>> though command prompt and did not work. I am not using a mapped network
>> drive. Permissions are fine on the file. Even went into registry and
>> tried
>> to change and then start sql still did not start and then when I went
>> back
>> into the registry and it was back to the old setting.
>> "John Bell" wrote:
>> > Hi
>> >
>> > This article descibes how to move your master database
>> > http://support.microsoft.com/kb/224071/EN-US/
>> >
>> > You may want to try starting SQL Server from the command prompt
>> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
>> > with the correct parameters (possibly with -f also!) and also making
>> > sure
>> > that the permissions for the directories being used are correct.
>> >
>> > You can not use a mapped network drive for your database files.
>> >
>> > John
>> >
>> > "Ray Skweres" wrote:
>> >
>> > > After changing the startup parameters and moving the database we are
>> > > unable
>> > > to start SQL. The error message we are getting in the application
>> > > log is
>> > > that the initconfig: (error 5) access denied to g:\sqldata.
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Error 5 is access denied. Make sure that the SQL Server service account has permissions to the file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Moved it based on Microsoft articel changed startup parameters and only moved
the master.mdf so I only changed that parameter.
"doller" wrote:
> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
> > After changing the startup parameters and moving the database we are unable
> > to start SQL. The error message we are getting in the application log is
> > that the initconfig: (error 5) access denied to g:\sqldata.
>|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters back
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
> > After changing the startup parameters and moving the database we are unable
> > to start SQL. The error message we are getting in the application log is
> > that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
> Used this article to move the database also tried to start it from a command
> prompt and would not start. Also tried to change the startup parameters back
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and tried
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
> > Hi
> >
> > This article descibes how to move your master database
> > http://support.microsoft.com/kb/224071/EN-US/
> >
> > You may want to try starting SQL Server from the command prompt
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
> > with the correct parameters (possibly with -f also!) and also making sure
> > that the permissions for the directories being used are correct.
> >
> > You can not use a mapped network drive for your database files.
> >
> > John
> >
> > "Ray Skweres" wrote:
> >
> > > After changing the startup parameters and moving the database we are unable
> > > to start SQL. The error message we are getting in the application log is
> > > that the initconfig: (error 5) access denied to g:\sqldata.|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved
> the master.mdf so I only changed that parameter.
> "doller" wrote:
> > HI,
> > How u moved the database and what parameter u have changed.
> >
> > from
> > killer
> >
> >
> > Ray Skweres wrote:
> > > After changing the startup parameters and moving the database we are
unable
> > > to start SQL. The error message we are getting in the application
log is
> > > that the initconfig: (error 5) access denied to g:\sqldata.
> >
> >|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:
>> Used this article to move the database also tried to start it from a
>> command
>> prompt and would not start. Also tried to change the startup parameters
>> back
>> though command prompt and did not work. I am not using a mapped network
>> drive. Permissions are fine on the file. Even went into registry and
>> tried
>> to change and then start sql still did not start and then when I went
>> back
>> into the registry and it was back to the old setting.
>> "John Bell" wrote:
>> > Hi
>> >
>> > This article descibes how to move your master database
>> > http://support.microsoft.com/kb/224071/EN-US/
>> >
>> > You may want to try starting SQL Server from the command prompt
>> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
>> > with the correct parameters (possibly with -f also!) and also making
>> > sure
>> > that the permissions for the directories being used are correct.
>> >
>> > You can not use a mapped network drive for your database files.
>> >
>> > John
>> >
>> > "Ray Skweres" wrote:
>> >
>> > > After changing the startup parameters and moving the database we are
>> > > unable
>> > > to start SQL. The error message we are getting in the application
>> > > log is
>> > > that the initconfig: (error 5) access denied to g:\sqldata.
Monday, February 20, 2012
MS Reporting, Oracle
Hi,
when I try to run a select-statement to an oracle database (10.1.03) with a
parameter from the SQL-area in MS Reporting I get a message like:
'The provider can not determine parameter information and setParameterInfo'
is not called' (or similar, the original message is in german).
The select statement is like:
SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE,
TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT
FROM TBLLOT
WHERE (MACHINENUM = @.machineNum)
ORDER BY LOT
There is no problem without the parameter, and there is no problem with the
parameter when I use a SQLServer DB.
Can someone help?
Thanks
Ulf
@.param is SQL Server specific, from BOL
Support for parameters in Oracle depends on the data provider that is used
to connect to the Oracle database. If your query contains named parameters
(for example, SELECT * FROM <table> WHERE <column name> = :ParameterName)
then you must use the Oracle data processing extension. If your query
contains unnamed parameters (for example, SELECT * FROM <table> WHERE
<column name> = ?), then you must use the OLE DB data processing extension
and select Microsoft OLE DB Provider for Oracle as a data provider
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Ulf" <Ulf@.discussions.microsoft.com> wrote in message
news:AFA90B76-8342-4EBA-AF07-BA5B01A78715@.microsoft.com...
> Hi,
> when I try to run a select-statement to an oracle database (10.1.03) with
> a
> parameter from the SQL-area in MS Reporting I get a message like:
> 'The provider can not determine parameter information and
> setParameterInfo'
> is not called' (or similar, the original message is in german).
> The select statement is like:
> SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE,
> TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT
> FROM TBLLOT
> WHERE (MACHINENUM = @.machineNum)
> ORDER BY LOT
> There is no problem without the parameter, and there is no problem with
> the
> parameter when I use a SQLServer DB.
> Can someone help?
> Thanks
> Ulf
|||Hi Jasper,
thank you for your answer. But this answer does not solve my problem. It is
simply not possible to use a syntax like :parameter in MS Reporting, and I
have had no success with unnamed parameters. It also seems like a MS
Reporting problem (or bug). I expect that MS Reporting will replace my
parameter (@.machineNum) with the value before sendeing the statement to
Oracle but may be I am wrong in this point.
I need a method to send a select-statement to Oracle with consideartion of
a user input. May be stored procedures will help but I prefer not to use
them.
ulf
"Ulf" wrote:
> Hi,
> when I try to run a select-statement to an oracle database (10.1.03) with a
> parameter from the SQL-area in MS Reporting I get a message like:
> 'The provider can not determine parameter information and setParameterInfo'
> is not called' (or similar, the original message is in german).
> The select statement is like:
> SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE,
> TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT
> FROM TBLLOT
> WHERE (MACHINENUM = @.machineNum)
> ORDER BY LOT
> There is no problem without the parameter, and there is no problem with the
> parameter when I use a SQLServer DB.
> Can someone help?
> Thanks
> Ulf
|||Hi Jasper,
thank you for your answer. But this answer does not solve my problem. It is
simply not possible to use a syntax like :parameter in MS Reporting, and I
have had no success with unnamed parameters. It also seems like a MS
Reporting problem (or bug). I expect that MS Reporting will replace my
parameter (@.machineNum) with the value before sendeing the statement to
Oracle but may be I am wrong in this point.
I need a method to send a select-statement to Oracle with consideartion of
a user input. May be stored procedures will help but I prefer not to use
them.
ulf
"Jasper Smith" wrote:
> @.param is SQL Server specific, from BOL
> Support for parameters in Oracle depends on the data provider that is used
> to connect to the Oracle database. If your query contains named parameters
> (for example, SELECT * FROM <table> WHERE <column name> = :ParameterName)
> then you must use the Oracle data processing extension. If your query
> contains unnamed parameters (for example, SELECT * FROM <table> WHERE
> <column name> = ?), then you must use the OLE DB data processing extension
> and select Microsoft OLE DB Provider for Oracle as a data provider
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
>
> "Ulf" <Ulf@.discussions.microsoft.com> wrote in message
> news:AFA90B76-8342-4EBA-AF07-BA5B01A78715@.microsoft.com...
>
>
when I try to run a select-statement to an oracle database (10.1.03) with a
parameter from the SQL-area in MS Reporting I get a message like:
'The provider can not determine parameter information and setParameterInfo'
is not called' (or similar, the original message is in german).
The select statement is like:
SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE,
TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT
FROM TBLLOT
WHERE (MACHINENUM = @.machineNum)
ORDER BY LOT
There is no problem without the parameter, and there is no problem with the
parameter when I use a SQLServer DB.
Can someone help?
Thanks
Ulf
@.param is SQL Server specific, from BOL
Support for parameters in Oracle depends on the data provider that is used
to connect to the Oracle database. If your query contains named parameters
(for example, SELECT * FROM <table> WHERE <column name> = :ParameterName)
then you must use the Oracle data processing extension. If your query
contains unnamed parameters (for example, SELECT * FROM <table> WHERE
<column name> = ?), then you must use the OLE DB data processing extension
and select Microsoft OLE DB Provider for Oracle as a data provider
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Ulf" <Ulf@.discussions.microsoft.com> wrote in message
news:AFA90B76-8342-4EBA-AF07-BA5B01A78715@.microsoft.com...
> Hi,
> when I try to run a select-statement to an oracle database (10.1.03) with
> a
> parameter from the SQL-area in MS Reporting I get a message like:
> 'The provider can not determine parameter information and
> setParameterInfo'
> is not called' (or similar, the original message is in german).
> The select statement is like:
> SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE,
> TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT
> FROM TBLLOT
> WHERE (MACHINENUM = @.machineNum)
> ORDER BY LOT
> There is no problem without the parameter, and there is no problem with
> the
> parameter when I use a SQLServer DB.
> Can someone help?
> Thanks
> Ulf
|||Hi Jasper,
thank you for your answer. But this answer does not solve my problem. It is
simply not possible to use a syntax like :parameter in MS Reporting, and I
have had no success with unnamed parameters. It also seems like a MS
Reporting problem (or bug). I expect that MS Reporting will replace my
parameter (@.machineNum) with the value before sendeing the statement to
Oracle but may be I am wrong in this point.
I need a method to send a select-statement to Oracle with consideartion of
a user input. May be stored procedures will help but I prefer not to use
them.
ulf
"Ulf" wrote:
> Hi,
> when I try to run a select-statement to an oracle database (10.1.03) with a
> parameter from the SQL-area in MS Reporting I get a message like:
> 'The provider can not determine parameter information and setParameterInfo'
> is not called' (or similar, the original message is in german).
> The select statement is like:
> SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE,
> TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT
> FROM TBLLOT
> WHERE (MACHINENUM = @.machineNum)
> ORDER BY LOT
> There is no problem without the parameter, and there is no problem with the
> parameter when I use a SQLServer DB.
> Can someone help?
> Thanks
> Ulf
|||Hi Jasper,
thank you for your answer. But this answer does not solve my problem. It is
simply not possible to use a syntax like :parameter in MS Reporting, and I
have had no success with unnamed parameters. It also seems like a MS
Reporting problem (or bug). I expect that MS Reporting will replace my
parameter (@.machineNum) with the value before sendeing the statement to
Oracle but may be I am wrong in this point.
I need a method to send a select-statement to Oracle with consideartion of
a user input. May be stored procedures will help but I prefer not to use
them.
ulf
"Jasper Smith" wrote:
> @.param is SQL Server specific, from BOL
> Support for parameters in Oracle depends on the data provider that is used
> to connect to the Oracle database. If your query contains named parameters
> (for example, SELECT * FROM <table> WHERE <column name> = :ParameterName)
> then you must use the Oracle data processing extension. If your query
> contains unnamed parameters (for example, SELECT * FROM <table> WHERE
> <column name> = ?), then you must use the OLE DB data processing extension
> and select Microsoft OLE DB Provider for Oracle as a data provider
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
>
> "Ulf" <Ulf@.discussions.microsoft.com> wrote in message
> news:AFA90B76-8342-4EBA-AF07-BA5B01A78715@.microsoft.com...
>
>
Subscribe to:
Posts (Atom)