sql error 15138: ran

Showing posts with label ran. Show all posts

Tuesday, March 27, 2012

Error 1813 while attaching database

I ran out of space, detacted the .mdf and deleted
the .ldf, as I have done in the past. However, when I try
to attach the database I get "Error 1813: Could not open
the new database ... Device activation error. The
physical file name {OLD_LDF_FILE_NAME} may be incorrect."
In the past, it has created a new .ldf file. How can I
get the date out of the mdf? Attach, export, import?Never never never do this, you have just found out why. Grab your backup and do restore, quite
simply. If you don't have a backup, open a case with MS support and they *might* be able to help
you.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Matt Insko" <minsko@.inovie.com> wrote in message news:1afa01c39f3e$6c148a20$3101280a@.phx.gbl...
> I ran out of space, detacted the .mdf and deleted
> the .ldf, as I have done in the past. However, when I try
> to attach the database I get "Error 1813: Could not open
> the new database ... Device activation error. The
> physical file name {OLD_LDF_FILE_NAME} may be incorrect."
> In the past, it has created a new .ldf file. How can I
> get the date out of the mdf? Attach, export, import?|||I've had that problem in the past, and it was because I had truncated
the log at some point, and never done a full backup since. Doing so
meant I could not re-attach the database but had to restore from a
backup.
Since you're out of space, is there any chance you tried to truncate the
log first?
Doug

Thursday, March 22, 2012

Error 15401 Adding Domain Group to SQL Server

I have tried rebooting the system, I have ran the script to look for duplicate sids and am still having the issue when trying to add a domain group to SQL. I get the Error 15401: Windows NT user or group'mi\Trust Legal' not found. Check the name again. Running SQL 2000 Std, with SP3a, and the collation is set to SQL_Latin1_General_CP850_BIN, which makes this instance case sensitive, and the group name is spelt right and am following the case sensitivity of the name as well.

This is most likely an issue due to using a different casing. You could use a tool like sid2name, to obtain the correct casing of the group name from Windows. Then use that same casing and the statement should succeed. You might want to quickly try and capitalize the domain name: MI instead of mi; if this doesn't work then look for a sid2name tool and use it to determine the correct casing. If you cannot find such tool, you could write one easily by calling the LookupAccountSid WinAPI. You could use this post as an example: http://blogs.msdn.com/lcris/archive/2005/09/26/474202.aspx.

Thanks
Laurentiu

|||

Most likely the cause of such failure is because the SQL Server cannot gather the information for this account from the domain controller.

Please make sure that the service account used to run SQL Server has permission to query the domain controller (in most cases being a member of the domain is sufficient to query the domain controller), and that the machine has access to the domain controller.

-Raul Garcia

SDE/T

SQL Server Engine

|||

OK, so you've got two suggestions. To quickly discern between these, try to ACL something to the group, on the machine on which the server is installed. If you can, then the issue is not with reaching the DC; if you cannot, then it is a DC issue.

Thanks
Laurentiu

|||

Apprciate all the great advice, but nothing seemed to help.

1) I am able to login into server using the account in which sql is running under, and am able to add the group to a folder on the box

2) ran the groups sid up against sid2name, and found the following:

MI\Trust Legal, is a group

enter the username just like that when adding another user to SQL and get the same message?

|||

What command are you executing? sp_addlogin or sp_adduser?

Thanks
Laurentiu

|||

Neither actually:

use IMCEXCLUSIVE
exec sp_grantlogin 'MI\Trust Legal'

since its a domain group, from what I read grantlogin was the proper SP to use, am I wrong?

|||

No, you're right. sp_grantlogin is the right command.

You're using the right command and what appears to be the correct group name. So the issue is probably elsewhere. Does the command work for other groups or users in the same domain or does it consistently fail? What about users or groups from another domain? Does it work for local accounts? We need to try to identify the extent of this issue - it might hopefully lead us to its cause. If this is a blocking issue for you, I suggest to contact customer support as well.

Thanks
Laurentiu

|||Interesting idea, now when I try to add a user MI\15451a it works fine, when I try to add another group MI\Trust Technology Services it works just fine, just an issue so far with this one group MI\Trust Legal, arrgghhhhh this sucks. @. this point, if I cant get it fixed, I might just create a new group and go that route.|||

The group must be different in some way from the others. You might want to try downloading SQL Server 2005 Express SP1 and trying this command out on it, to see if you get the same issue.

Thanks
Laurentiu

Wednesday, March 21, 2012

error 14294

Hi -
I am an extremely novice user attempting to use transactional replication. I successfully ran the replication and then opted to remove the subscriptions, publications and so forth and start again. I did not remove the distributor. I may have removed
jobs associated with the distributor though. When i attempt to recreate the publication, I recieve error 14294 - indicating that a job name or id is desired. I am seeking suggestions as to how I can recover from the error.
Lily,
probably the best way is to start again. You can disable publishing which
removes the distribution database and any remaining jobs/alerts then enable
publishing and distribution which will add all the plumbing including any
alerts and jobs which have been deleted.
HTH,
Paul Ibison
|||Thanks you are the greatest!!
It worked and I am on my way again.
Thanks again!
sql

Error 14262

Merge replication - SQL 2000. I ran some scripts to add a column to a table
and to add a new table and view to articles. All went fine. Then I tried
to manually start the snapshot agent and it gave me this error "The
specified @.job_id('guid number...') does not exist."
What do I need to do? I looked at Paul's site and found the explanation but
I'm not sure if this applies and was not clear what to do. Please help,
thanks.
David
Hi David - the explanation on my site refers to a scripting error and
doesn't seem relevant to your case to be honest. Can you refresh the jobs
folder as I think that you might be attempting to start a job that has been
removed/replaced. Also check under replication monitor that the agent has a
job (right-click and select "Agent properties..." and see what the name is
there.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul,
I got this message from the Snapshot Agents folder, right-click of the
publication (which has a red X on it) and selecting "Start Agent". The
status column shows "Failed" due to "Timeout expired. ..." Apparently the
last attempt to create this had a problem. This server is not on our site,
so I'm not sure what happened. Also, this publication under the Publishers
folder also has a red X on it. Do I have to re-create the Publication
entirely?
Also, when I was there yesterday I created a new table and added it to the
articles via sp_addmergearticle. I also ran sp_repladdcolumn to add a
column to an existing publication. I have 2 publications, one for tables
and the other for views and stored procs. The one with the problems is the
tables publication and these problems (red X) existed before I ran these
additions.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:egCdwmKMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> Hi David - the explanation on my site refers to a scripting error and
> doesn't seem relevant to your case to be honest. Can you refresh the jobs
> folder as I think that you might be attempting to start a job that has
> been removed/replaced. Also check under replication monitor that the agent
> has a job (right-click and select "Agent properties..." and see what the
> name is there.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>

Sunday, February 26, 2012

Error : insufficient system memory

Hi,
We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
issues. As soon as we installed the Database on Windows 2003 we are getting
the error saying that there is insufficient system memory. We get this at
least twice every week. Once this error happens most of SQL statements give
similar error message.
Kindly provide some help on this.
Here is the error message
SQLState: 42000, ErrorCode:701
[Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient system
memory to run this query.
--
Thanks,
Mr GeekWithout seeing a stack dump file , it is hard to say exactly what is causing
the problem.
Are the queries that trigger this problem , dealing with UNION ALL or IN
with largae data sets?
Have you thought about upgarding to sp4?
--
Jack Vamvas
__________________________________________________________________
"LSolve" <L0L@.newsgroups.nospam> wrote in message
news:F4561270-E1BA-4B4C-9841-DA55FE250789@.microsoft.com...
> Hi,
> We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
> issues. As soon as we installed the Database on Windows 2003 we are
getting
> the error saying that there is insufficient system memory. We get this at
> least twice every week. Once this error happens most of SQL statements
give
> similar error message.
> Kindly provide some help on this.
> Here is the error message
> SQLState: 42000, ErrorCode:701
> [Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient
system
> memory to run this query.
> --
> Thanks,
> Mr Geek|||Hello,
Please refer to the following article which describes how to troubleshoot
the slow performance of many concurrent ad-hoc queries:
243588 HOW TO: Troubleshoot the Performance of Ad-Hoc Queries
http://support.microsoft.com/?id=243588
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.|||Hi Lsolve,
If u want to check that ur sql server need more merory then check this
artical .
http://www.computerperformance.co.uk/HealthCheck/Memory_Health.htm
from
Doller

Error : insufficient system memory

Hi,
We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
issues. As soon as we installed the Database on Windows 2003 we are getting
the error saying that there is insufficient system memory. We get this at
least twice every week. Once this error happens most of SQL statements give
similar error message.
Kindly provide some help on this.
Here is the error message
SQLState: 42000, ErrorCode:701
[Microsoft][ODBC SQL Server Driver][SQL Server]There is insuffic
ient system
memory to run this query.
Thanks,
Mr GeekWithout seeing a stack dump file , it is hard to say exactly what is causing
the problem.
Are the queries that trigger this problem , dealing with UNION ALL or IN
with largae data sets?
Have you thought about upgarding to sp4?
Jack Vamvas
________________________________________
__________________________
"LSolve" <L0L@.newsgroups.nospam> wrote in message
news:F4561270-E1BA-4B4C-9841-DA55FE250789@.microsoft.com...
> Hi,
> We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
> issues. As soon as we installed the Database on Windows 2003 we are
getting
> the error saying that there is insufficient system memory. We get this at
> least twice every week. Once this error happens most of SQL statements
give
> similar error message.
> Kindly provide some help on this.
> Here is the error message
> SQLState: 42000, ErrorCode:701
> [Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient[/
vbcol]
system[vbcol=seagreen]
> memory to run this query.
> --
> Thanks,
> Mr Geek|||Hello,
Please refer to the following article which describes how to troubleshoot
the slow performance of many concurrent ad-hoc queries:
243588 HOW TO: Troubleshoot the Performance of Ad-Hoc Queries
http://support.microsoft.com/?id=243588
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.|||Hi Lsolve,
If u want to check that ur sql server need more merory then check this
artical .
http://www.computerperformance.co.u...mory_Health.htm
from
Doller

Error : insufficient system memory

Hi,
We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
issues. As soon as we installed the Database on Windows 2003 we are getting
the error saying that there is insufficient system memory. We get this at
least twice every week. Once this error happens most of SQL statements give
similar error message.
Kindly provide some help on this.
Here is the error message
SQLState: 42000, ErrorCode:701
[Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient system
memory to run this query.
Thanks,
Mr Geek
Without seeing a stack dump file , it is hard to say exactly what is causing
the problem.
Are the queries that trigger this problem , dealing with UNION ALL or IN
with largae data sets?
Have you thought about upgarding to sp4?
Jack Vamvas
__________________________________________________ ________________
"LSolve" <L0L@.newsgroups.nospam> wrote in message
news:F4561270-E1BA-4B4C-9841-DA55FE250789@.microsoft.com...
> Hi,
> We ran our application on Windows 2000 with SQL 2000 SP3a, and had no
> issues. As soon as we installed the Database on Windows 2003 we are
getting
> the error saying that there is insufficient system memory. We get this at
> least twice every week. Once this error happens most of SQL statements
give
> similar error message.
> Kindly provide some help on this.
> Here is the error message
> SQLState: 42000, ErrorCode:701
> [Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient
system
> memory to run this query.
> --
> Thanks,
> Mr Geek
|||Hello,
Please refer to the following article which describes how to troubleshoot
the slow performance of many concurrent ad-hoc queries:
243588 HOW TO: Troubleshoot the Performance of Ad-Hoc Queries
http://support.microsoft.com/?id=243588
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.
|||Hi Lsolve,
If u want to check that ur sql server need more merory then check this
artical .
http://www.computerperformance.co.uk...ory_Health.htm
from
Doller

Tuesday, March 27, 2012

Error 1813 while attaching database

Thursday, March 22, 2012

Error 15401 Adding Domain Group to SQL Server

Wednesday, March 21, 2012

error 14294

Error 14262

Sunday, February 26, 2012

Error : insufficient system memory

Error : insufficient system memory

Error : insufficient system memory

Error : insufficient system memory

Error : insufficient system memory

Error : insufficient system memory

sql error 15138

Blog Archive

About Me