connect from ASP app: run

Showing posts with label run. Show all posts

Sunday, March 25, 2012

Cant get a simple code to work

Can someone please help me fix this. The if statement always runs. I only want it to run if the statement is true and there is a result coming back. If the productID does not have any magazines linking to it, I don't want the If statement to run. Thanks in advance.

ASP.NET code:

If Not Magazine.GetMagazinesForProduct(ProductID) Is Nothing Then
blanklabel.Text = categoryDetails.Spacer
blanklabel.Visible = True
blanklabel2.Text = categoryDetails.Spacer
blanklabel2.Visible = True
magazinerecommendedlabel.Text = "Recommended/Featured in the following magazine(s):"
magazinerecommendedlabel.Visible = True
End If
--------

magazine class:

Public Function GetMagazinesForProduct(ByVal productID As String) As SqlDataReader
Dim connection As New SqlConnection(connectionString)

Dim command As New SqlCommand("GetMagazinesForProduct", connection)
command.CommandType = CommandType.StoredProcedure

command.Parameters.Add("@.ProductID", SqlDbType.VarChar, 50)
command.Parameters("@.ProductID").Value = productID

connection.Open()

Return command.ExecuteReader(CommandBehavior.CloseConnection)
End Function

--------

Stored Procedure:

CREATE PROCEDURE GetMagazinesForProduct
(@.ProductID varchar)
AS
SELECT Magazine.[Name], Magazine.[Issue], Magazine.SmallImagePath
FROM Magazine INNER JOIN MagazineProduct
ON Magazine.MagazineID = MagazineProduct.MagazineID
WHERE MagazineProduct.ProductID = @.ProductID
RETURN
GO

--------How about trying a while instead? I'm not sure of the exact VB syntax, maybe something like this:


dim myReader as Magazine.GetMagazinesForProduct(ProductID)
While myReader .Read()
 .. do your stuff
end while

|||for some reason, myReader.Read() always executes FALSE. Why is that?|||It means there's no data in present. Are you positive your stored proc is returning data for the id you are passing to it?

Thursday, March 22, 2012

Can't find PInvoke DLL 'sqlceme30.dll'

I am developing for an ipaq handheld. I just upgraded to Windows Mobile 5.0 and tried to run my application and I get this message.

Can't find PInvoke DLL 'sqlceme30.dll'

I am using a sql Mobile DB and vs2005
found fix here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=220816&SiteID=1
sql

Tuesday, March 20, 2012

Can't execute sp in vb.net

Hellou
I'm trying to execute simple sp with 5 input parmeters from vb.net. This sp works great when it is run from SQL Server management studio, but when I want to execute it from vb.net, I allways get this error:
"Syntax error, permission violation, or other nonspecific error"
Here's the code:

Cnn.Open("...")

Comm.ActiveConnection = Cnn

Comm.CommandType = ADODB.CommandTypeEnum.adCmdStoredProc

Comm.CommandText = "spSklVnos-Prenos" 'that's thename of the sp

RetParam.Direction = ADODB.ParameterDirectionEnum.adParamOutput

RetParam.Type = ADODB.DataTypeEnum.adInteger

Comm.Parameters.Append(RetParam)

P1.Direction = ADODB.ParameterDirectionEnum.adParamInput

P1.Type = ADODB.DataTypeEnum.adVarChar

P1.Size = 1

P1.Value = LocParA

Comm.Parameters.Append(P1)

P2.Direction = ADODB.ParameterDirectionEnum.adParamInput

P2.Type = ADODB.DataTypeEnum.adInteger

P2.Value = LocPar1

Comm.Parameters.Append(P2)

P3.Direction = ADODB.ParameterDirectionEnum.adParamInput

P3.Type = ADODB.DataTypeEnum.adInteger

P3.Value = LocPar2

Comm.Parameters.Append(P3)

P4.Direction = ADODB.ParameterDirectionEnum.adParamInput

P4.Type = ADODB.DataTypeEnum.adInteger

P4.Value = LocPar3

Comm.Parameters.Append(P4)

P5.Direction = ADODB.ParameterDirectionEnum.adParamInput

P5.Type = ADODB.DataTypeEnum.adInteger

P5.Value = PrevzemIDx

Comm.Parameters.Append(P5)

Comm.Execute()

Am I missing something?
Thanks for any suggestion.
Dido

Your syntax looks fine to me, but I'm not a VB.NET expert. Make sure your datatypes for the parameters match the stored procedure exactly. You might try asking this question on the VB forums, since it doesn't seem to be related to SSIS.

Can't drop procedure ... Snapshot won't run... Help!

Hi,
I have a server set up for Merge replication. It is the publisher and the
distributer. Has been working fine.
It has two publications.
I wanted the subscribers to get a new copy of the data next time they
replicate, so I went to the first publication, which is stored procs and
view, went to Status tab of the publication properties, and clicked the run
agent now. When it was done, I right clicked on the publication and selected
reinitialize subscriptions.
Then I went to the publication for tables. Right clicked and selected
Re-initialize subscritions. Then I went to the status tab and selected run
agent now. When it came back with a timestamp, red x's appeared on the
replication monitor on the snap shot agents.
The error message it give is :
Cannot drop the procedure 'dbo.sp_sel_B4AC8FE9123F47EDB952DCE5249B4F84_pal'
because it is being used for replication.
As a last resort, I tried to delete the publication, I was going to re do
it. When I try to delete it
it gives me the same error message as above, but with a different sp_sel_
name.
What should I do, or what did I do. I really need it back to working today.
.. .
Any help,
Thanks,
Steve
Well, here is what I did.
I kept trying to delete the publication that I could not get the snapshot
agent to run on, and kept getting the error above. So I delete the stored
proc publication, it went OK. Then I deleted the table publication, and this
time it let me. Then I went to each of the clients, deleted both
subscriptions, and re-created them. Ran fine then, and am able to do manual
pull replications from the subscriber boxes now.
If any one can help me understand what happened, please do. How did I get
in that mess, and what would have been a good way to get out. I was lucky
that I could get to all subscriber boxes and re-create the subscriptions.
Thanks,
Steve
"SteveInBeloit" wrote:

> Hi,
> I have a server set up for Merge replication. It is the publisher and the
> distributer. Has been working fine.
> It has two publications.
> I wanted the subscribers to get a new copy of the data next time they
> replicate, so I went to the first publication, which is stored procs and
> view, went to Status tab of the publication properties, and clicked the run
> agent now. When it was done, I right clicked on the publication and selected
> reinitialize subscriptions.
> Then I went to the publication for tables. Right clicked and selected
> Re-initialize subscritions. Then I went to the status tab and selected run
> agent now. When it came back with a timestamp, red x's appeared on the
> replication monitor on the snap shot agents.
> The error message it give is :
> Cannot drop the procedure 'dbo.sp_sel_B4AC8FE9123F47EDB952DCE5249B4F84_pal'
> because it is being used for replication.
> As a last resort, I tried to delete the publication, I was going to re do
> it. When I try to delete it
> it gives me the same error message as above, but with a different sp_sel_
> name.
> What should I do, or what did I do. I really need it back to working today.
> . .
> Any help,
> Thanks,
> Steve
>
sql

Sunday, March 11, 2012

Can''t deploy "unsafe assembly", permission problem(?)

Hello,

I think I have some kind of permission problem. But first things first:

I have code which I would like to run in SQL Server (CLR Integration). First thing is that my code uses third-party-dll. I have to deploy my code as unsafe because of

CREATE ASSEMBLY failed because method "add_FunctionAdd" on type "USP.Express.Pro.FunctionsCollection" in safe assembly "USP.Express.Pro.2.0" has a synchronized attribute. Explicit synchronization is not allowed in safe assemblies.

Of course I can not create "asymmetric key" for third-party-dll (Or can I?).

So, I tried to use trustworthy DB. But I get all the time error Msg 10327: "Assembly is not authorised for PERMISSION_SET=UNSAFE"

I am using Windows Login to log on Sql Server. Login is granted "Unsafe assembly" and DB has trustworthy setting "on".

DB user owns schemas "db_owner" and "db_securityadmin".

Am I missing something?

Interesting thing is that I can do deployment (as unsafe assembly) in master-database. But not in the other databases.

Questions are:

- Is there other way to authorise third-party-dll than using trustworthy?

- Why deployment can be done in master-database?

And finally:

- Why deployment can not be done in other database?

So when you are deploying an assembly with the UNSAFE permission set (or EXTERNAL_ACCESS) and are using the TRUSTWORTHY settings (i.e. not assymetric keys etc), the login of the owner of the database has to have the relevant permissions. In your case UNSAFE ASSEMBLY.

Niels
|||

Hello Niels,

" login of the owner of the database has to have the relevant permissions. In your case UNSAFE ASSEMBLY."

As far as I know, permission _should_ be OK.

I checked following:

1. database -> properties (the database I want unsafe assembly to be created): owner is <DOMAIN\username>.

2. corresponding database user -> properties: Login name is same.

I have done "Grant UNSAFE ASSEMBLY to <DOMAIN\username>;" and "ALTER DATABASE <database> SET trustworthy on". Both are executed without errors.

<DOMAIN\username> is the Login name of owner of <database> and <database> is the db I want my assembly to be created.

Is there something still missing?

What I should check next?

- Jorma

|||Hmm, what is the exact error message you are getting? Is this database a new database, or is it restored from (perhaps) SQL 2000? What happens if you were to create a new database (with DOMAIN\username as owner), setting the database to TRUSTWORTHY and deply the assembly?

Niels
|||

Hello again,

Error message is:

Msg 10327, Level 14, State 1, Line 1

CREATE ASSEMBLY for assembly 'MillCC' failed because assembly 'USP.Express.Pro.2.0' is not authorized for PERMISSION_SET = UNSAFE.

"USP.Express.Pro.2.0" is the third-party-dll my code is using. Previously message were same but assembly named in the message was my code... Interesting.

I created new database as you suggested. And assembly was created without errors. Why in the world I didn't try this before... So, problem is somehow related with the database I am using.

The database is restored from SQL Server 2005 Express Edition.

Is there something I should know when using restored database and CLR?

|||Ah, it is restored. Try this for me please:
1. Run ALTER AUTHORIZATION against the database and change it to [Domain\username] (I know that you said that was the owner, but do it once again, please.
2. Run ALTER DATABASE and reset TRUSTWORTHY to on
3. Try and deploy

Niels
|||

I tried

Alter authorization on DATABASE::<database> to <[DOMAIN\username]>

but there came out following error:

Msg 15110, Level 16, State 1, Line 1

The proposed new database owner is already a user or aliased in the database.

Should I remove something before running ALTER AUTHORIZATION? I am quite confused about the permissions at this stage Smile

|||OK, drop the user in the database, which is the user for the login [Domain\username], then run the ALTER AUTHORIZATION again.

Alternatively, you can create a SQL login (just a login) and make that login the owner of the database and assign the login the necessary permissions.

Niels
|||

OK,

first I tried to drop my user but there came out errors because user owns schemas etc.

I was impatient to test this, so I created new login and made login owner of the database. After givin permissions to the login I was able to create assembly.

In other words, now it is working! Thank you very much Niels!

Can you explain to me what was wrong with the "original" owner? I quess there happens "something" when database is restored...

Can''t deploy "unsafe assembly", permission problem(?)

Hello,

I think I have some kind of permission problem. But first things first:

I have code which I would like to run in SQL Server (CLR Integration). First thing is that my code uses third-party-dll. I have to deploy my code as unsafe because of

Of course I can not create "asymmetric key" for third-party-dll (Or can I?).

So, I tried to use trustworthy DB. But I get all the time error Msg 10327: "Assembly is not authorised for PERMISSION_SET=UNSAFE"

I am using Windows Login to log on Sql Server. Login is granted "Unsafe assembly" and DB has trustworthy setting "on".

DB user owns schemas "db_owner" and "db_securityadmin".

Am I missing something?

Interesting thing is that I can do deployment (as unsafe assembly) in master-database. But not in the other databases.

Questions are:

- Is there other way to authorise third-party-dll than using trustworthy?

- Why deployment can be done in master-database?

And finally:

- Why deployment can not be done in other database?

Niels
|||

Hello Niels,

" login of the owner of the database has to have the relevant permissions. In your case UNSAFE ASSEMBLY."

As far as I know, permission _should_ be OK.

I checked following:

1. database -> properties (the database I want unsafe assembly to be created): owner is <DOMAIN\username>.

2. corresponding database user -> properties: Login name is same.

I have done "Grant UNSAFE ASSEMBLY to <DOMAIN\username>;" and "ALTER DATABASE <database> SET trustworthy on". Both are executed without errors.

<DOMAIN\username> is the Login name of owner of <database> and <database> is the db I want my assembly to be created.

Is there something still missing?

What I should check next?

- Jorma

Niels
|||

Hello again,

Error message is:

Msg 10327, Level 14, State 1, Line 1

CREATE ASSEMBLY for assembly 'MillCC' failed because assembly 'USP.Express.Pro.2.0' is not authorized for PERMISSION_SET = UNSAFE.

"USP.Express.Pro.2.0" is the third-party-dll my code is using. Previously message were same but assembly named in the message was my code... Interesting.

I created new database as you suggested. And assembly was created without errors. Why in the world I didn't try this before... So, problem is somehow related with the database I am using.

The database is restored from SQL Server 2005 Express Edition.

Is there something I should know when using restored database and CLR?

Niels
|||

I tried

Alter authorization on DATABASE::<database> to <[DOMAIN\username]>

but there came out following error:

Msg 15110, Level 16, State 1, Line 1

The proposed new database owner is already a user or aliased in the database.

Should I remove something before running ALTER AUTHORIZATION? I am quite confused about the permissions at this stage Smile

|||OK, drop the user in the database, which is the user for the login [Domain\username], then run the ALTER AUTHORIZATION again.

Alternatively, you can create a SQL login (just a login) and make that login the owner of the database and assign the login the necessary permissions.

Niels
|||

OK,

first I tried to drop my user but there came out errors because user owns schemas etc.

I was impatient to test this, so I created new login and made login owner of the database. After givin permissions to the login I was able to create assembly.

In other words, now it is working! Thank you very much Niels!

Can you explain to me what was wrong with the "original" owner? I quess there happens "something" when database is restored...

Thursday, March 8, 2012

Can't debug Script tasks

After upgrading to CTP16 (Sept.), I can't seem to debug my script tasks. Everytime I run the package with a breakpoint in script task I get following error: "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience. "

If I remove the breakpoint the scrip task runs successfully. So my question is how do I debug a script task with CTP 16?
As per my knowledge, there was no debugging support for script component.
So, you are left with few options like MessageBox.Show or rowcount etc.

Don't know if debugging support is there in sept/nov versions.

hth,
Nitesh|||No he said script task not script component and the script task does indeed support debugging.

As for the problem, do you get any error information in the error pane or progress pane. Do you get a minidump in 90\shared\ErrorDumps?

Thanks,
Matt|||Thank you for you reply Matt. No. I do not get any error info in error pane, output windows, or errordumps folder. I just get a dialog box with the error message listed above.

My Script task is set to Precompile and all the other properties are deafulted. I was under the impression that I would only get the error when there was syntax or logic problem, however, that's not true since I can take the breakpoint out and the script runs successfully.|||

If you set precompile to false then open and save the script does that make the breakpoints work or do you still get the same problem?

Thanks,
Matt

|||I have tried setting the precompile to false and it does break. However, it's not consistant. I guess CTP16 still has debugger issues hope they fix it in sql 2005 rel.

Can't debug proc after Sp2 on WinXP

Hi,
After installation of SP2 on my WinXP Prof I can't run debug in SQL Query
Analyzer.
Unable to connect to debugger on "SERVER" (Error = 0x800706ba). Ensure that
client-side components, such as SQLDBREG.EXE, are installed and registered on
"MYXP". Debugging disabled for connection nn.
Server is Win 2003 and SQL 2000 with Sp3
Before Sp2 everything was OK.
Thanks for the help.
ML
Make sure you have followed all the steps in the help topic
in books online: Troubleshooting the Transact-SQL Debugger
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Wed, 27 Oct 2004 05:13:03 -0700, MarekL
<MarekL@.discussions.microsoft.com> wrote:

>Hi,
>After installation of SP2 on my WinXP Prof I can't run debug in SQL Query
>Analyzer.
>Unable to connect to debugger on "SERVER" (Error = 0x800706ba). Ensure that
>client-side components, such as SQLDBREG.EXE, are installed and registered on
>"MYXP". Debugging disabled for connection nn.
>Server is Win 2003 and SQL 2000 with Sp3
>Before Sp2 everything was OK.
>Thanks for the help.
>ML

Can't Debug a script task

After upgrading to CTP16 (Sept.), I can't seem to debug my script task. Everytime I run the package with a breakpoint in script task I get following error: "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience. "

If I remove the breakpoint the scrip task runs successfully. So my question is how do I debug a script task with CTP 16?

This should be posted to SQL Server Integration Services. Please acknowledge and I'll move the thread to the appropriate group.

Friday, February 24, 2012

can't connect to the ODBC database named aspol54

can any one provide any suggestions to help this error i installed automation studion 5.4 and the program will not run on my laptop.

i traced the data below when i try to start the program.

AsProjet db0-b5c ENTER SQLAllocEnv
HENV * 015CF6B0

AsProjet db0-b5c EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS)
HENV * 0x015CF6B0 ( 0x015e1540)

AsProjet db0-b5c ENTER SQLGetEnvAttr
SQLHENV 015E1540
SQLINTEGER 201 <unknown>
SQLPOINTER [Unknown attribute 201]
SQLINTEGER 4
SQLINTEGER * 0x0013E380

AsProjet db0-b5c EXIT SQLGetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 015E1540
SQLINTEGER 201 <unknown>
SQLPOINTER [Unknown attribute 201]
SQLINTEGER 4
SQLINTEGER * 0x0013E380 (1567744)
any help would be great.

tks

I don't know how much help this is, but the '201' attribute is for 'SQL_ATTR_CONNECTION_POOLING'. The weird thing is that the return value seems to be 1567744. It should be returning '0' in this case. Here are possible values (from SQLEXT.H):

/* values for SQL_ATTR_CONNECTION_POOLING */
#define SQL_CP_OFF 0UL
#define SQL_CP_ONE_PER_DRIVER 1UL
#define SQL_CP_ONE_PER_HENV 2UL
#define SQL_CP_DEFAULT SQL_CP_OFF

It looks like you're receiving invalid data, but I don't know why or how. Sorry I can't be of more help.

Perhaps someone else on the alias can shed some light on this?

|||

Hi,

In addition to Warren's comments - what you see in the ODBC trace doesn't indicate an error. Simply an Environment handle was allocated and GetEnvAttr was called to retrieve the Environment's connection pooling attribute setting. Both calls appear to have succeeded. The fact that we get a strange value, probably means that the ODBC driver doesn't support it (it's an ODBC 3.0 attribute). Is the application using the driver directly (without Driver Manager)? Could you post the actual error that you get or is there any additional information in the ODBC trace?

HTH,

Jivko Dobrev - MSFT

This posting is provided "AS IS" with no warranties, and confers no rights.

can't connect to SQLCMD

dear sirits my first time to work with SQL server 2005

i've installed it and tried to connect to sqlcmd by :

run sqlcmd

i got errors

after that i logged to the database engine normally and created new database and tried again to relogin to the database engine but i failed and faced error:4064

i have three points needed to be answered :

1- SQLCMD loin problem

2- database engine error:4064

3- i need to import .mdb file to my new database

regards

1. See your post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=671937&SiteID=1&mode=1
2. The user you are currently trying to login with does not have the appropiate permissions to the assigned default database or the database does not exist anymore. To solve this issue you can login with a priviledged account and change the default database of the user to a valid / granted one via the GUI or the proc sp_defaultdb.
3. Attach the database to your server and use the import wizrad to transfer the objects to the new database. You can also access the objects using the three part name notation like

SELECT * FROM DatabaseName.SchemaName.ObjectName

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Sunday, February 19, 2012

cant connect to sql server 2005 from my asp.net application

I can't connect to sql server 2005 from my asp.net web page. I seem to be able to connect to it when i run the application from within visual studio but i can't connect to it when i run the application from IIS.

I am new to sql server 2005 express so please bear with me.

The error message i get is:

Cannot open database "Vets" requested by the login. The login failed.
Login failed for user 'OSCAR2K4\ASPNET'.

I don't know where this user OSCAR2K4\ASPNET came from but i looked in sql server 2005 and there he is. In the left hand pane I went to Security and then logins and found oscar2k4\asp.net there. I went to the properties for this user and went to User Mappings. There was no tick next to my Vets database so I added one and ran the application from IIS. I also added the user to every single role in the vets database (including dbowner). I also went into the vets database itself and found the oscar/aspnet user and made sure he was added to every role.

I ran the application again. This time i got a lots of different errors. If the page was trying to run a select procedure I got the error user does not have select permission. If the page was running an SP i got the error or user does not execute permission

I have never had this problem before so I don't understand.

Where did this user come from? Was he created automatically when i configured my database for membership and roles? How do i set up this user so he can access the databsae from IIS.

The only way I could get the application to run from IIS was to go to Security - Logins for sql server and add the oscar2k4\asp.net user to the sysadmin role.

I find this very strange. Naturally i don't want to leave oscar2k4 in sysadmin.

Please help :) I can't upload my website until i fix this

Thanks, andrea

<server>\ASPNET is 'ASP.NET Machine Account', one of the access control lists (ACLs) that are set by default on the Machine.config file and the root Web.config file.

What's the OS version (e.g. Window2000 or Xp) of the box? You can take a look at this articlehttp://msdn2.microsoft.com/en-us/library/ab4e6cky.aspx

Tuesday, February 14, 2012

Can't connect to SeptCTP x64

I've built and deployed cubes on a x64 server, with x64 SQL2005 SeptCTP.

Works pretty much fine. I can run 32 bit Excel on the server, and browse the cubes no problem.

However, if I fire up 32 bit Excel on my 32 bit client machine, and go through the MultiDimensional data source wizard to connet to the cubes, after I put the server name in, it throws this error:

"The peer prematurely closed the connection"

Then this error:

"An error was encountered in the transport layer"

Like a fool, I went from 32 bit to 64 bit and from JunCTP to SeptCTP at the same time, so I don't know which is to blame.

I'm aware of the classic "re-register msolap90.dll on the client" fix, and I've tried it, and it aint that.

Any ideas?

Some more info on this:

If I open up SeptCTP Management Studio on a 32 bit client machine, connect to the Analysis Server on the 64 bit server, it connects. I can see the database on teh x64 machine, and below that, I can see the Data Source, DSVs, Cubes etc.

BUT

When I right click on cube, and try to browse, it fails with the following error:

Cannot show requested dialog.

ADDITIONAL INFORMATION:

Deserialization failed: The 'EditionID' element in the 'http://schemas.microsoft.com/analysisservices/2003/engine' namespace is unexpected. (Microsoft.AnalysisServices)

Exactly the same error presents whether I try to get the properties of a cub, data source, dsv, whatever.

I do not understand this at all.

|||I got the same error on deploying my project. It works fine on Jun CTP but got the error in Sep CTP and the MSSQL 2005 evaluation copy. Any advise? Thanks in advance!

Can't connect to SeptCTP x64

I've built and deployed cubes on a x64 server, with x64 SQL2005 SeptCTP.

Works pretty much fine. I can run 32 bit Excel on the server, and browse the cubes no problem.

However, if I fire up 32 bit Excel on my 32 bit client machine, and go through the MultiDimensional data source wizard to connet to the cubes, after I put the server name in, it throws this error:

"The peer prematurely closed the connection"

Then this error:

"An error was encountered in the transport layer"

Like a fool, I went from 32 bit to 64 bit and from JunCTP to SeptCTP at the same time, so I don't know which is to blame.

I'm aware of the classic "re-register msolap90.dll on the client" fix, and I've tried it, and it aint that.

Any ideas?

Some more info on this:

BUT

When I right click on cube, and try to browse, it fails with the following error:

Cannot show requested dialog.

ADDITIONAL INFORMATION:

Deserialization failed: The 'EditionID' element in the 'http://schemas.microsoft.com/analysisservices/2003/engine' namespace is unexpected. (Microsoft.AnalysisServices)

Exactly the same error presents whether I try to get the properties of a cub, data source, dsv, whatever.

I do not understand this at all.

|||I got the same error on deploying my project. It works fine on Jun CTP but got the error in Sep CTP and the MSSQL 2005 evaluation copy. Any advise? Thanks in advance!

cant connect to my databse in lan

Hi all!

I am using MSSQL 2005 and asp.net .I have made a web application that needs to be run in LAN.The authentication used is windows authentication.The problem is that when in LAN I cannot connect to the database The sqlexception error shows that the connection is closed.Is there any thing that i am missing?Any configurations i need to make??Is this the issue of remote connections?? Please help!!I am new and dont knw much abt it .Thanks!!

Quote:

Originally Posted by dotnetgal

Hi all!

yes you have to setup the Security of SQL Server to accept Mix Authentication|||

Quote:

Originally Posted by ck9663

yes you have to setup the Security of SQL Server to accept Mix Authentication

hello !!

Thanks for the reply.But how am i to set it up to accept Mix Authentication?|||

Quote:

Originally Posted by dotnetgal

hello !!

Thanks for the reply.But how am i to set it up to accept Mix Authentication?

open enterprise manager. right click on your server. choose properties. a dialog box will appear. choose Securtiy. on Server Authentication, choose SQL Server and Windows authentication mode|||

Quote:

Originally Posted by ck9663

open enterprise manager. right click on your server. choose properties. a dialog box will appear. choose Securtiy. on Server Authentication, choose SQL Server and Windows authentication mode

thanks!!I did it but dtill the problem persists!!Any idea?

Friday, February 10, 2012

Can't connect remotely when SQL services running as a domain account

I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts. I
configured the sql service and sql agent service to run as a domain account.
I made that account a member of the administrators group on the SQL server,
and restarted the services. Everything looked fine. The problem is, some of
my remote applications cannot connect when it is running as a domain
account, but they are fine when it is running as a local system account. On
a remote Microsoft WSUS server, it breaks when the SQL services on the SQL
server use a domain account. Osql on the remote box generates this:
Cannot generate SSPI context
I did try to research this before posting here, but I couldn't find anything
that described this problem. Everything was referring to PCs connecting from
a different domain. That is not the case here.
Thanks,
MatthewCannot Generate SSPI context is almost always related to there not being a
Service Principal Name defined for that server, account and port in a
Kerberos environment.
Domain accounts do not create an SPN, whereas Domain Admins and Local System
do.
Test this by making (temporarily) your startup account a domain admin and
the resetting in in SQL Enterprise Manager. restart and test connectivity.
If it connects, have your domain admin (must be a domain admin) create an
SPN for the MSSQLSvc in Active Directory.
See the Books Online article "Security Account Delegation" for formot of
what the resulting SPN should look like.
Also, make sure the SQL Server is listening on TCP...make that your first
step.
--
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email alerts.
> I configured the sql service and sql agent service to run as a domain
> account. I made that account a member of the administrators group on the
> SQL server, and restarted the services. Everything looked fine. The
> problem is, some of my remote applications cannot connect when it is
> running as a domain account, but they are fine when it is running as a
> local system account. On a remote Microsoft WSUS server, it breaks when
> the SQL services on the SQL server use a domain account. Osql on the
> remote box generates this:
> Cannot generate SSPI context
> I did try to research this before posting here, but I couldn't find
> anything that described this problem. Everything was referring to PCs
> connecting from a different domain. That is not the case here.
> Thanks,
> Matthew
>|||I am the domain admin, so that won't be a problem. As soon as some of the
current activity dies down, I will try this. Thanks!
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators group
>> on the SQL server, and restarted the services. Everything looked fine.
>> The problem is, some of my remote applications cannot connect when it is
>> running as a domain account, but they are fine when it is running as a
>> local system account. On a remote Microsoft WSUS server, it breaks when
>> the SQL services on the SQL server use a domain account. Osql on the
>> remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>|||Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
having problems configuring the alerts. Outlook 2003 SP2 is installed. I
logged in with he SQL service account, and setup the MAPI profile. That
worked fine. When I set up an operator logged in as the service account,
clicking Test email generates this error:
http://img167.imageshack.us/my.php?image=sqlerroran3.png
If I log in as my self, it acts like it went through when I click test, but
no email is generated.
Any ideas?
Thanks again for your help.
-Matthew
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Cannot Generate SSPI context is almost always related to there not being a
> Service Principal Name defined for that server, account and port in a
> Kerberos environment.
> Domain accounts do not create an SPN, whereas Domain Admins and Local
> System do.
> Test this by making (temporarily) your startup account a domain admin and
> the resetting in in SQL Enterprise Manager. restart and test
> connectivity.
> If it connects, have your domain admin (must be a domain admin) create an
> SPN for the MSSQLSvc in Active Directory.
> See the Books Online article "Security Account Delegation" for formot of
> what the resulting SPN should look like.
> Also, make sure the SQL Server is listening on TCP...make that your first
> step.
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators group
>> on the SQL server, and restarted the services. Everything looked fine.
>> The problem is, some of my remote applications cannot connect when it is
>> running as a domain account, but they are fine when it is running as a
>> local system account. On a remote Microsoft WSUS server, it breaks when
>> the SQL services on the SQL server use a domain account. Osql on the
>> remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>|||All I can tell you is that SQL mail is profiel specific...could be a
permissions issue on the profile itself?
That's not my area :-)
--
Kevin Hill
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
> Thanks! Adding the SPN took care of it. I thought I was there, but now I'm
> having problems configuring the alerts. Outlook 2003 SP2 is installed. I
> logged in with he SQL service account, and setup the MAPI profile. That
> worked fine. When I set up an operator logged in as the service account,
> clicking Test email generates this error:
> http://img167.imageshack.us/my.php?image=sqlerroran3.png
> If I log in as my self, it acts like it went through when I click test,
> but no email is generated.
> Any ideas?
> Thanks again for your help.
> -Matthew
> "Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
> news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
>> Cannot Generate SSPI context is almost always related to there not being
>> a Service Principal Name defined for that server, account and port in a
>> Kerberos environment.
>> Domain accounts do not create an SPN, whereas Domain Admins and Local
>> System do.
>> Test this by making (temporarily) your startup account a domain admin and
>> the resetting in in SQL Enterprise Manager. restart and test
>> connectivity.
>> If it connects, have your domain admin (must be a domain admin) create an
>> SPN for the MSSQLSvc in Active Directory.
>> See the Books Online article "Security Account Delegation" for formot of
>> what the resulting SPN should look like.
>> Also, make sure the SQL Server is listening on TCP...make that your first
>> step.
>> --
>> Kevin Hill
>> 3NF Consulting
>> www.3nf-inc.com/NewsGroups.htm
>>
>>
>> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
>> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators group
>> on the SQL server, and restarted the services. Everything looked fine.
>> The problem is, some of my remote applications cannot connect when it is
>> running as a domain account, but they are fine when it is running as a
>> local system account. On a remote Microsoft WSUS server, it breaks when
>> the SQL services on the SQL server use a domain account. Osql on the
>> remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>>
>|||This thing is baffling. I read a couple posts that just the 'Test' button
has issues. I scheduled some maintenance to run at 4 AM last night. It ran,
sent me the results, and the log indicated the job failed because the last
step, the email, failed.
The job failed. The Job was invoked by Schedule 4 (Schedule 1). The last
step to run was step 1 (Step 1). NOTE: Failed to notify 'SQL Alerts' via
email.
"Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
news:uFBi8n43GHA.4924@.TK2MSFTNGP05.phx.gbl...
> All I can tell you is that SQL mail is profiel specific...could be a
> permissions issue on the profile itself?
> That's not my area :-)
> --
> Kevin Hill
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
>
>
> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
> message news:eMiLlw33GHA.5000@.TK2MSFTNGP02.phx.gbl...
>> Thanks! Adding the SPN took care of it. I thought I was there, but now
>> I'm having problems configuring the alerts. Outlook 2003 SP2 is
>> installed. I logged in with he SQL service account, and setup the MAPI
>> profile. That worked fine. When I set up an operator logged in as the
>> service account, clicking Test email generates this error:
>> http://img167.imageshack.us/my.php?image=sqlerroran3.png
>> If I log in as my self, it acts like it went through when I click test,
>> but no email is generated.
>> Any ideas?
>> Thanks again for your help.
>> -Matthew
>> "Kevin3NF" <Kevin@.DontNeedNoSpam3NF-inc.com> wrote in message
>> news:OxBRke33GHA.1288@.TK2MSFTNGP03.phx.gbl...
>> Cannot Generate SSPI context is almost always related to there not being
>> a Service Principal Name defined for that server, account and port in a
>> Kerberos environment.
>> Domain accounts do not create an SPN, whereas Domain Admins and Local
>> System do.
>> Test this by making (temporarily) your startup account a domain admin
>> and the resetting in in SQL Enterprise Manager. restart and test
>> connectivity.
>> If it connects, have your domain admin (must be a domain admin) create
>> an SPN for the MSSQLSvc in Active Directory.
>> See the Books Online article "Security Account Delegation" for formot of
>> what the resulting SPN should look like.
>> Also, make sure the SQL Server is listening on TCP...make that your
>> first step.
>> --
>> Kevin Hill
>> 3NF Consulting
>> www.3nf-inc.com/NewsGroups.htm
>>
>>
>> "Matthew Kitchin (Usenet/Lists)" <mkitchin.public@.gmail.com> wrote in
>> message news:%231cmKJ33GHA.1300@.TK2MSFTNGP05.phx.gbl...
>> I'm running SQL 2000 SP4 on 2003 server. I'm trying to setup email
>> alerts. I configured the sql service and sql agent service to run as a
>> domain account. I made that account a member of the administrators
>> group on the SQL server, and restarted the services. Everything looked
>> fine. The problem is, some of my remote applications cannot connect
>> when it is running as a domain account, but they are fine when it is
>> running as a local system account. On a remote Microsoft WSUS server,
>> it breaks when the SQL services on the SQL server use a domain account.
>> Osql on the remote box generates this:
>> Cannot generate SSPI context
>> I did try to research this before posting here, but I couldn't find
>> anything that described this problem. Everything was referring to PCs
>> connecting from a different domain. That is not the case here.
>> Thanks,
>> Matthew
>>
>>
>

Sunday, March 25, 2012

Cant get a simple code to work

Thursday, March 22, 2012

Can't find PInvoke DLL 'sqlceme30.dll'

Tuesday, March 20, 2012

Can't execute sp in vb.net

Can't drop procedure ... Snapshot won't run... Help!

Sunday, March 11, 2012

Can''t deploy "unsafe assembly", permission problem(?)

Can''t deploy "unsafe assembly", permission problem(?)

Thursday, March 8, 2012

Can't debug Script tasks

Can't debug proc after Sp2 on WinXP

Can't Debug a script task

Friday, February 24, 2012

can't connect to the ODBC database named aspol54

can't connect to SQLCMD

Sunday, February 19, 2012

cant connect to sql server 2005 from my asp.net application

Tuesday, February 14, 2012

Can't connect to SeptCTP x64

Can't connect to SeptCTP x64

cant connect to my databse in lan

Friday, February 10, 2012

Can't connect remotely when SQL services running as a domain account

Can't connect remotely when SQL services running as a domain account

Can't connect remotely when SQL services running as a domain account

connect from ASP app

Blog Archive

About Me