Showing posts with label receiving. Show all posts
Showing posts with label receiving. Show all posts

Thursday, March 29, 2012

Error 18456

I am repeatedly receiving the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
This has been occuring since a network wide password
change ( for an employee leaving the company ) and I do
realize that there is some process trying to connect, but
I do not know how to find out what the process is, or
what it is trying to connect as. Is there a way to trace
this information?You may be able to catch this with SQL Profiler and/or a network trace.
The network trace will only work if the connection is coming from a remote
machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Have tried the profiler and don't get enough information
to track. Haven't tried a network trace, I will try, but
I don't think it is a remote connection. Thanks for your
help.
Rachel

>--Original Message--
>You may be able to catch this with SQL Profiler and/or a
network trace.
>The network trace will only work if the connection is
coming from a remote
>machine.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>

Monday, March 26, 2012

Error 17805 Invalid buffer received from Client when executing stored Procedure

Hello,
I am receiving this error when I try to execute a Stored Procedure in
SQL Server 2000 using SYBASE dblib.
I have been able to connect to connect to SQL Server from Unix, but
when I try to execute a Stored Procedure via dblib, I get the error:
"Error 17805 Invalid buffer received from Client"
My Stored Procedure does not receive parameters, so I don't know what
is happening.
If I execute a simple SQL Statement, it works fine
I have a SQL Server 2000 running SP 4.
anyone can help?
Thank you in advanced
Jose Manuel
Jose Manuel wrote:
> Hello,
> I am receiving this error when I try to execute a Stored Procedure in
> SQL Server 2000 using SYBASE dblib.
> I have been able to connect to connect to SQL Server from Unix, but
> when I try to execute a Stored Procedure via dblib, I get the error:
> "Error 17805 Invalid buffer received from Client"
> My Stored Procedure does not receive parameters, so I don't know what
> is happening.
> If I execute a simple SQL Statement, it works fine
> I have a SQL Server 2000 running SP 4.
> anyone can help?
> Thank you in advanced
> Jose Manuel
Just curious: Why are you executing SQL on SQL Server 2000 usin the
Sybase dbLib instead of a SQL Server client library?
David Gugick
Imceda Software
www.imceda.com
|||Jose Manuel,
I am having exactlly the same problem as you had.
Could you please tell me how did you solve it?
Thanks
creo que voy varios pasos atras de ti. ojal me puedas ayudar. tengo el
mismo problema.
te ha contactado alguien ?
lo pudiste resolver?
gracias.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

error 16389

Hello,
We have a active x script that has been running for weeks from sql server
agent and all of sudden last night we are receiving "ActiveScripting specific
error 16389 occurred" on the jobs. I have search both BOL and newsgroups but
not finding anything that is giving me any help on this. Has anyone seen
this before, is so what step are need to be performed to troubleshoot the
issue.
The sql server that we are running this from is central DBA sql server
connecting to both production and non-production servers via SQL-DMO trusted
connections and extracting scripts for object generation.
Stopping and starting SQL Agent has fixed the issue. What could have caused
this issue?
"Tom" wrote:

> Hello,
> We have a active x script that has been running for weeks from sql server
> agent and all of sudden last night we are receiving "ActiveScripting specific
> error 16389 occurred" on the jobs. I have search both BOL and newsgroups but
> not finding anything that is giving me any help on this. Has anyone seen
> this before, is so what step are need to be performed to troubleshoot the
> issue.
> The sql server that we are running this from is central DBA sql server
> connecting to both production and non-production servers via SQL-DMO trusted
> connections and extracting scripts for object generation.

error 16389

Hello,
We have a active x script that has been running for weeks from sql server
agent and all of sudden last night we are receiving "ActiveScripting specific
error 16389 occurred" on the jobs. I have search both BOL and newsgroups but
not finding anything that is giving me any help on this. Has anyone seen
this before, is so what step are need to be performed to troubleshoot the
issue.
The sql server that we are running this from is central DBA sql server
connecting to both production and non-production servers via SQL-DMO trusted
connections and extracting scripts for object generation.Stopping and starting SQL Agent has fixed the issue. What could have caused
this issue?
"Tom" wrote:
> Hello,
> We have a active x script that has been running for weeks from sql server
> agent and all of sudden last night we are receiving "ActiveScripting specific
> error 16389 occurred" on the jobs. I have search both BOL and newsgroups but
> not finding anything that is giving me any help on this. Has anyone seen
> this before, is so what step are need to be performed to troubleshoot the
> issue.
> The sql server that we are running this from is central DBA sql server
> connecting to both production and non-production servers via SQL-DMO trusted
> connections and extracting scripts for object generation.

error 16389

Hello,
We have a active x script that has been running for weeks from sql server
agent and all of sudden last night we are receiving "ActiveScripting specifi
c
error 16389 occurred" on the jobs. I have search both BOL and newsgroups bu
t
not finding anything that is giving me any help on this. Has anyone seen
this before, is so what step are need to be performed to troubleshoot the
issue.
The sql server that we are running this from is central DBA sql server
connecting to both production and non-production servers via SQL-DMO trusted
connections and extracting scripts for object generation.Stopping and starting SQL Agent has fixed the issue. What could have caused
this issue?
"Tom" wrote:

> Hello,
> We have a active x script that has been running for weeks from sql server
> agent and all of sudden last night we are receiving "ActiveScripting speci
fic
> error 16389 occurred" on the jobs. I have search both BOL and newsgroups
but
> not finding anything that is giving me any help on this. Has anyone seen
> this before, is so what step are need to be performed to troubleshoot the
> issue.
> The sql server that we are running this from is central DBA sql server
> connecting to both production and non-production servers via SQL-DMO trust
ed
> connections and extracting scripts for object generation.

Wednesday, March 21, 2012

error 15004: Name cannot be NULL'

Hi,
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
PingPlease see my reply in the Replication group.
Paul Ibison

Sunday, March 11, 2012

error 1069

I am receiving the following error:
An error 1069 - (The service did not start due to a logon
failure) occurred while peforming the service operation
on the MSSQLServer service.
Any suggestions?Check the password for the account that the SQL Server Service is using.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Haas" <h_widemond@.hotmail.com> wrote in message
news:cf1d01c4104b$22447580$a001280a@.phx.gbl...
> I am receiving the following error:
> An error 1069 - (The service did not start due to a logon
> failure) occurred while peforming the service operation
> on the MSSQLServer service.
> Any suggestions?

Friday, February 24, 2012

Error "An attempt to attach an auto-named database for file"

Hello,

I have seen some solutions of which I tried on this form for the error I am receiving, but I still cannot get the issue resolved.

Here is my case:

I developed an app using SQL Express as the local data source. I published it to my server using the Once Click install feature. When I look in my project viewer, under settings, My db connection strings are listed as follows: Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\TAP_Master.mdf;Integrated Security=True;User Instance=True

From another computer, I navigate to the publish site, install and run the application with no problems. I have on another computer, the same app with an updated version number that I wish to publish, however the difference is is that this published version does not include the database as I do not want the end user to overwrite any existing data that they may have from the previous version.

I publish the updated version, install it but when the app runs, I receive the message, "An attempt to attach an auto-named database for file".

Any suggestions?

Thanks in advance.

Rashar wrote:

I have on another computer, the same app with an updated version number that I wish to publish, however the difference is is that this published version does not include the database as I do not want the end user to overwrite any existing data that they may have from the previous version.

Please explain what this means. What do you mean by "another computer" is this a different computer than your development computer and the end-user computer? How did you create this updated version of the application, did you just remove the database or did you create a copy of the project?

When you install this "update" is it really updating the original deployment or is it installing a completely separate copy of the program?

Shrot answer: I don't think ClickOnce works like this from a VS perspective. I know it doesn't work like this from a SQL perspective. If you remove the database from your project and redeploy, I believe the database will actually be removed. (I say "belive" because I've never tried this.) You might want to consider an alternate way to deploy your database, I've documented one alternative in my blog, start with this post.

Mike

|||

Yes... It is a different computer from my development computer. Basically, I have the same code on both the development pc and the other pc... The reason being is that on my development pc, I would publish the entire app the database included. The problem I ran in to was if I made a change to the database on the development PC, published it, then have the client pc update their app, it would for some reason give them a new database overwriting any existintg data. It actually worked for me this way, until I decided to establish 2 different publishing locations, and I think that is where my problem lies.

Thanks for your reply and advice Mike!

Regards.

|||

I found the problem. When I published the second time around, the publish created an empty folder under C:\Documents and Settings\username\Local Settings\Apps\2.0.

So I just copied my database into that folder and it worked.

|||

I hadt he same problem en found thefollowing sollution:

This is what I found in web.config

<connectionStrings>

<add name="JopieString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Joop.mdf;Integrated Security=True;User Instance=True"

providerName="System.Data.SqlClient" />

</connectionStrings>

|DataDirectory| is the directory of visual webdeveloper.

Delete this and type the name of the path in which your database is stored (in my case c:\inetpub\wwwroot\etc.)

<connectionStrings>

<add name="JopieString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=C:\inetpub\wwwroot\App_Data\Joop.mdf;Integrated Security=True;User Instance=True"

providerName="System.Data.SqlClient" />

</connectionStrings>

This solved the problem for me, I hope it also solves yours.

Error "An attempt to attach an auto-named database for file"

Hello,

I have seen some solutions of which I tried on this form for the error I am receiving, but I still cannot get the issue resolved.

Here is my case:

I developed an app using SQL Express as the local data source. I published it to my server using the Once Click install feature. When I look in my project viewer, under settings, My db connection strings are listed as follows: Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\TAP_Master.mdf;Integrated Security=True;User Instance=True

From another computer, I navigate to the publish site, install and run the application with no problems. I have on another computer, the same app with an updated version number that I wish to publish, however the difference is is that this published version does not include the database as I do not want the end user to overwrite any existing data that they may have from the previous version.

I publish the updated version, install it but when the app runs, I receive the message, "An attempt to attach an auto-named database for file".

Any suggestions?

Thanks in advance.

Rashar wrote:

I have on another computer, the same app with an updated version number that I wish to publish, however the difference is is that this published version does not include the database as I do not want the end user to overwrite any existing data that they may have from the previous version.

Please explain what this means. What do you mean by "another computer" is this a different computer than your development computer and the end-user computer? How did you create this updated version of the application, did you just remove the database or did you create a copy of the project?

When you install this "update" is it really updating the original deployment or is it installing a completely separate copy of the program?

Shrot answer: I don't think ClickOnce works like this from a VS perspective. I know it doesn't work like this from a SQL perspective. If you remove the database from your project and redeploy, I believe the database will actually be removed. (I say "belive" because I've never tried this.) You might want to consider an alternate way to deploy your database, I've documented one alternative in my blog, start with this post.

Mike

|||

Yes... It is a different computer from my development computer. Basically, I have the same code on both the development pc and the other pc... The reason being is that on my development pc, I would publish the entire app the database included. The problem I ran in to was if I made a change to the database on the development PC, published it, then have the client pc update their app, it would for some reason give them a new database overwriting any existintg data. It actually worked for me this way, until I decided to establish 2 different publishing locations, and I think that is where my problem lies.

Thanks for your reply and advice Mike!

Regards.

|||

I found the problem. When I published the second time around, the publish created an empty folder under C:\Documents and Settings\username\Local Settings\Apps\2.0.

So I just copied my database into that folder and it worked.

|||

I hadt he same problem en found thefollowing sollution:

This is what I found in web.config

<connectionStrings>

<add name="JopieString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Joop.mdf;Integrated Security=True;User Instance=True"

providerName="System.Data.SqlClient" />

</connectionStrings>

|DataDirectory| is the directory of visual webdeveloper.

Delete this and type the name of the path in which your database is stored (in my case c:\inetpub\wwwroot\etc.)

<connectionStrings>

<add name="JopieString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=C:\inetpub\wwwroot\App_Data\Joop.mdf;Integrated Security=True;User Instance=True"

providerName="System.Data.SqlClient" />

</connectionStrings>

This solved the problem for me, I hope it also solves yours.

Sunday, February 19, 2012

Error

receiving error during backup.

Microsoft SQL-DMO (ODBC SQLState: 42000)

The media set for database '%' has 2 family members but only 3 are provided. All members must be provided. BACKUP DATABASE is terminating abnormally.

You might want to check your backup device definition. Remember that you can't mix a multi-file device with a single file device.