ERwin

Hi,
I have just installed ERwin data modeler and can't seem to get past
the 'connection manager'. In 'Master dafatase' I have put: master but
it is saying invalid object master..m7License. I have enteretd the
license keys during installation. Do I have to make any changes in the
database too?
Thanks
It looks like the problem was either with your installation, your
configuration, or your rights. (I have not installed any of the more recent
versions of ERwin, so just things to look for.)
Installation: The installation apparently should have created the table
m7License in the master database, but perhaps that step failed.
Configuration: The table m7License was successfully created in another
database, but the ERwin application configuration does not know where the
table is.
Rights: Everything is where it should be, but you personally do not have
rights to the m7License table in master.
FWIW,
RLF
<othellomy@.yahoo.com> wrote in message
news:1175056298.365698.98030@.d57g2000hsg.googlegro ups.com...
> Hi,
> I have just installed ERwin data modeler and can't seem to get past
> the 'connection manager'. In 'Master dafatase' I have put: master but
> it is saying invalid object master..m7License. I have enteretd the
> license keys during installation. Do I have to make any changes in the
> database too?
> Thanks
>

Errors using the uninstall tool - 'vs_uninst_betas'

Hi Folks

getting the following error message when using the tool and can get past it. i can email the error dialog to you if required, i just cant post it.

the setup has encountered an unexpected error in data store. The action is RestoreSetupParams. The error is: Failed to read property installl ds

What are you trying to uninstall?

This tool was written by VS, it might be valueable to post this question into one of the VS forums.

Mike

|||

Hi Mike,

i am trying to install SQL server express edition 2005 however i am being told that there are incompatable components from beta versions of visual studio, .net framework or sql 2005. I have removed all of these and rebooted and run the tool however it makes no difference.

Previously both the express edition and the full edition of sql2005 have been on this computer at seperate times, however both have been removed. I have tried to install the full version however the same error occurs.

I have removed everything remotely connected with sql 2005, .net and visual studio and the problem remains.

I can email you screen shots of all error messages if required

thanks for the help

Nick

|||

Hi Nick,

The setup log should list the specific components that are causing the problem on your computer. If you can not find those components listed in Add/Remove Programs, you can remove them manually using the following in the Run dialog:

msiexec /x <product id>

Product ID will be a long number listed in the setup log for each of the offending product. Run this for each of the products listed in the log.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

Hi Mike,

again thanks for replying to me!

Unfortunately your reply was of limited help. I am not sure what/where the setup log is that you refer to. When the original error messages appear after running the tool, there are no product id’s and no indication of what they are.

if you let me know where to get the setup log i will run

msiexec /x <product id>

for the offending products

thanks in advance

nick

|||

Hi Nick,

You can find the setup logs at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG. The summary.txt has general information, will usually tell you which specific component of SQL failed to install and point you to a more detailed log in the Files folder. The detailed log should contain the product IDs.

Mike

|||

hi,

the information stored in the summary.txt is as follows -

Microsoft SQL Server 2005 Setup beginning at Mon Jul 17 12:27:30 2006
Process ID : 1268
c:\b4bd99cb30de03073795be5c67\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/6/17 12:27:30
Complete: LoadResourcesAction at: 2006/6/17 12:27:30, returned true
Running: ParseBootstrapOptionsAction at: 2006/6/17 12:27:30
Loaded DLL:c:\b4bd99cb30de03073795be5c67\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/6/17 12:27:30, returned true
Running: ValidateWinNTAction at: 2006/6/17 12:27:30
Complete: ValidateWinNTAction at: 2006/6/17 12:27:30, returned true
Running: ValidateMinOSAction at: 2006/6/17 12:27:30
Complete: ValidateMinOSAction at: 2006/6/17 12:27:30, returned true
Running: PerformSCCAction at: 2006/6/17 12:27:30
Complete: PerformSCCAction at: 2006/6/17 12:27:30, returned true
Running: ActivateLoggingAction at: 2006/6/17 12:27:30
Complete: ActivateLoggingAction at: 2006/6/17 12:27:30, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1268" returned false.
Running: PerformSCCAction2 at: 2006/6/17 12:27:30
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

Class not registered.

i am unable to manually delete the last two using the run command that you supplied as it says the installation package could not be opened when i place the product id in the run command. is it possible to manually remove these last two items in some other way?

as always mike - thanks for your help

nick

|||

sorry for the delay Nick, this one fell off the radar.

If the manual uninstall trick doesn't work, it could be that the product is actually already uninstalled and only the Add/Remove Programs entry still exists, which is messing things up. As a last resort, you can try the Windows Installer Cleanup Utility, which removes entries from the ARP list. If that doesn't resolve the issue, I'm not sure what is wrong with your computer. You may need to phone into support to get more directed help.

Mike

|||

Hi Mike

I think a reformat may be in order! Thanks for all the help.

By the way, would you know of a good article/thread on how to preform sql 2005 express back ups by any chance?

thanks again for all the help

nick

|||

just what i needed.. great application

many thanks

:)

|||

I don't think the definitive article exists on backup for Express, we pretty much default to "just use Windows Task Scheduler" like that really helps. That said, I've found a few interesting bits to suffice untill I finally write the definitive article.

One of our MVPs wrote a couple articles, a SProc and a tool that helps with maintenance of your database. Check it out at http://www.sqldbatips.com/showarticle.asp?ID=27.sql

Errors using the uninstall tool - 'vs_uninst_betas'

Hi Folks

getting the following error message when using the tool and can get past it. i can email the error dialog to you if required, i just cant post it.

the setup has encountered an unexpected error in data store. The action is RestoreSetupParams. The error is: Failed to read property installl ds

What are you trying to uninstall?

This tool was written by VS, it might be valueable to post this question into one of the VS forums.

Mike

|||

Hi Mike,

i am trying to install SQL server express edition 2005 however i am being told that there are incompatable components from beta versions of visual studio, .net framework or sql 2005. I have removed all of these and rebooted and run the tool however it makes no difference.

Previously both the express edition and the full edition of sql2005 have been on this computer at seperate times, however both have been removed. I have tried to install the full version however the same error occurs.

I have removed everything remotely connected with sql 2005, .net and visual studio and the problem remains.

I can email you screen shots of all error messages if required

thanks for the help

Nick

|||

Hi Nick,

The setup log should list the specific components that are causing the problem on your computer. If you can not find those components listed in Add/Remove Programs, you can remove them manually using the following in the Run dialog:

msiexec /x <product id>

Product ID will be a long number listed in the setup log for each of the offending product. Run this for each of the products listed in the log.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

|||

Hi Mike,

again thanks for replying to me!

Unfortunately your reply was of limited help. I am not sure what/where the setup log is that you refer to. When the original error messages appear after running the tool, there are no product id’s and no indication of what they are.

if you let me know where to get the setup log i will run

msiexec /x <product id>

for the offending products

thanks in advance

nick

|||

Hi Nick,

You can find the setup logs at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG. The summary.txt has general information, will usually tell you which specific component of SQL failed to install and point you to a more detailed log in the Files folder. The detailed log should contain the product IDs.

Mike

|||

hi,

the information stored in the summary.txt is as follows -

Microsoft SQL Server 2005 Setup beginning at Mon Jul 17 12:27:30 2006
Process ID : 1268
c:\b4bd99cb30de03073795be5c67\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/6/17 12:27:30
Complete: LoadResourcesAction at: 2006/6/17 12:27:30, returned true
Running: ParseBootstrapOptionsAction at: 2006/6/17 12:27:30
Loaded DLL:c:\b4bd99cb30de03073795be5c67\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/6/17 12:27:30, returned true
Running: ValidateWinNTAction at: 2006/6/17 12:27:30
Complete: ValidateWinNTAction at: 2006/6/17 12:27:30, returned true
Running: ValidateMinOSAction at: 2006/6/17 12:27:30
Complete: ValidateMinOSAction at: 2006/6/17 12:27:30, returned true
Running: PerformSCCAction at: 2006/6/17 12:27:30
Complete: PerformSCCAction at: 2006/6/17 12:27:30, returned true
Running: ActivateLoggingAction at: 2006/6/17 12:27:30
Complete: ActivateLoggingAction at: 2006/6/17 12:27:30, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1268" returned false.
Running: PerformSCCAction2 at: 2006/6/17 12:27:30
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

Class not registered.

i am unable to manually delete the last two using the run command that you supplied as it says the installation package could not be opened when i place the product id in the run command. is it possible to manually remove these last two items in some other way?

as always mike - thanks for your help

nick

|||

sorry for the delay Nick, this one fell off the radar.

If the manual uninstall trick doesn't work, it could be that the product is actually already uninstalled and only the Add/Remove Programs entry still exists, which is messing things up. As a last resort, you can try the Windows Installer Cleanup Utility, which removes entries from the ARP list. If that doesn't resolve the issue, I'm not sure what is wrong with your computer. You may need to phone into support to get more directed help.

Mike

|||

Hi Mike

I think a reformat may be in order! Thanks for all the help.

By the way, would you know of a good article/thread on how to preform sql 2005 express back ups by any chance?

thanks again for all the help

nick

|||

just what i needed.. great application

many thanks

:)

|||

I don't think the definitive article exists on backup for Express, we pretty much default to "just use Windows Task Scheduler" like that really helps. That said, I've found a few interesting bits to suffice untill I finally write the definitive article.

One of our MVPs wrote a couple articles, a SProc and a tool that helps with maintenance of your database. Check it out at http://www.sqldbatips.com/showarticle.asp?ID=27.

error:40 connecting with sql server 2000

Hi
I am getting this really annoying error that I cant resolve.
I have created a website that accesses a SQL SERVER 2000 database and
it works perfectly on my home machine. The error has occurred when I
have transferred it to my hosts server.
This is the error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)
This is my connection string:
<add key="ConnectionString" value="Provider=sqloledb;Data
Source=hostsserver****,1433;Initial
Catalog=db******;User Id=dbo*******;Password=********; "/>
It says I am trying to connect to a SQL SERVER 2000 database as this is
what I devloped the site on so I do not know why it thinks I am trying
to connect to SQL SERVER 2005.
Can anyone help?Is your host database server and your home database server the same? It look
s
like that your host database server is in SQL Server 2005.
By the way do you use outside host provider? If yes, you might want to
consider giving them an e-mail. Looking at the connection string, I don't se
e
any problem:
"Provider=SQLOLEDB;Data Source=Your_Server_Name;Initial Catalog=
Your_Database_Name;UserId=Your_Username;
Password=Your_Password;" .
So I am thinking that the host database server might be on different port
number than 1433 or use a named instance?
Lucas
"chrisbarber1@.gmail.com" wrote:

> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>|||Thanks for your reply.

> Is your host database server and your home database server the same?
Yes both are on sql server 2000

> By the way do you use outside host provider? If yes, you might want to
> consider giving them an e-mail.
The host providor has been absolutely hopeless.

> So I am thinking that the host database server might be on different port
> number than 1433 or use a named instance?
I'll look in to this although on the hosts control panel definately
says 1433.
Any other ideas?|||<chrisbarber1@.gmail.com> wrote in message
news:1149755323.823279.142210@.u72g2000cwu.googlegroups.com...
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
It really sounds like the ISP is full of it and somehow your site is trying
to connect to a 2005 server with remote connections turned off.

> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>|||Check the value of instance config parameter: "remote access" and see
whether it is enabled..
> sp_configure 'remote access'
Jayesh
<chrisbarber1@.gmail.com> wrote in message
news:1149755323.823279.142210@.u72g2000cwu.googlegroups.com...
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>

error:40 connecting with sql server 2000

Hi
I am getting this really annoying error that I cant resolve.
I have created a website that accesses a SQL SERVER 2000 database and
it works perfectly on my home machine. The error has occurred when I
have transferred it to my hosts server.
This is the error:
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)
This is my connection string:
<add key="ConnectionString" value="Provider=sqloledb;Data
Source=hostsserver****,1433;Initial
Catalog=db******;User Id=dbo*******;Password=********; "/>
It says I am trying to connect to a SQL SERVER 2000 database as this is
what I devloped the site on so I do not know why it thinks I am trying
to connect to SQL SERVER 2005.
Can anyone help?Is your host database server and your home database server the same? It looks
like that your host database server is in SQL Server 2005.
By the way do you use outside host provider? If yes, you might want to
consider giving them an e-mail. Looking at the connection string, I don't see
any problem:
"Provider=SQLOLEDB;Data Source=Your_Server_Name;Initial Catalog=Your_Database_Name;UserId=Your_Username;Password=Your_Password;" .
So I am thinking that the host database server might be on different port
number than 1433 or use a named instance?
Lucas
"chrisbarber1@.gmail.com" wrote:
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>|||Thanks for your reply.
> Is your host database server and your home database server the same?
Yes both are on sql server 2000
> By the way do you use outside host provider? If yes, you might want to
> consider giving them an e-mail.
The host providor has been absolutely hopeless.
> So I am thinking that the host database server might be on different port
> number than 1433 or use a named instance?
I'll look in to this although on the hosts control panel definately
says 1433.
Any other ideas?|||<chrisbarber1@.gmail.com> wrote in message
news:1149755323.823279.142210@.u72g2000cwu.googlegroups.com...
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
It really sounds like the ISP is full of it and somehow your site is trying
to connect to a 2005 server with remote connections turned off.
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>|||Check the value of instance config parameter: "remote access" and see
whether it is enabled..
> sp_configure 'remote access'
Jayesh
<chrisbarber1@.gmail.com> wrote in message
news:1149755323.823279.142210@.u72g2000cwu.googlegroups.com...
> Hi
> I am getting this really annoying error that I cant resolve.
> I have created a website that accesses a SQL SERVER 2000 database and
> it works perfectly on my home machine. The error has occurred when I
> have transferred it to my hosts server.
> This is the error:
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)
>
> This is my connection string:
> <add key="ConnectionString" value="Provider=sqloledb;Data
> Source=hostsserver****,1433;Initial
> Catalog=db******;User Id=dbo*******;Password=********; "/>
>
> It says I am trying to connect to a SQL SERVER 2000 database as this is
> what I devloped the site on so I do not know why it thinks I am trying
> to connect to SQL SERVER 2005.
> Can anyone help?
>

Error: There is already an open DataReader associated with this Command

Hi

I'm trying to loop through all the records in a recordset and perform a database update within the loop. The problem is that you can't have more than one datareader open at the same time. How should I be doing this?

cmdPhoto =New SqlCommand("select AuthorityID,AuthorityName,PREF From qryStaffSearch where AuthorityType='User' Order by AuthorityName", conWhitt)

conWhitt.Open()

dtrPhoto = cmdPhoto.ExecuteReader

While dtrPhoto.Read()

IfNot File.Exists("D:WhittNetLive\Web\images\staffphotos\pat_images_resize\" & dtrPhoto("PRef") &".jpg")Then

cmdUpdate =New SqlCommand("Update tblAuthority Set NoPhoto = 1 Where AuthorityID =" & dtrPhoto("AuthorityID"), conWhitt)

cmdUpdate.ExecuteNonQuery()

EndIf

EndWhile

Thanks

What you could do is create a update sub that you just passed the ID of the photo to, which then set the NoPhoto to 1

i.e.

While dtrPhoto.Read()

IfNot File.Exists("D:WhittNetLive\Web\images\staffphotos\pat_images_resize\" & dtrPhoto("PRef") &".jpg")Then

SetPhoto(dtrPhoto("AuthorityID"))

cmdUpdate.ExecuteNonQuery()

Then create a sub

Sub SetPhoto(Byval id as Integer)

' Your database stuff

cmdUpdate =New SqlCommand("Update tblAuthority Set NoPhoto = 1 Where AuthorityID =" & id, conWhitt)

End Sub

Hope that helps

|||

Thanks, I thought that would work but I get the same error

PrivateSub Page_Load(ByVal senderAs System.Object, _

ByVal eAs System.EventArgs)HandlesMyBase.Load

Dim cmdPhotoAs SqlCommand

Dim dtrPhotoAs SqlDataReader

cmdPhoto =New SqlCommand("select AuthorityID,AuthorityName,PREF From qryStaffSearch where AuthorityType='User' Order by AuthorityName", conWhitt)

conWhitt.Open()

dtrPhoto = cmdPhoto.ExecuteReader

While dtrPhoto.Read()

IfNot File.Exists("D:WhittNetLive\Web\images\staffphotos\pat_images_resize\" & dtrPhoto("Pref") &".jpg")And dtrPhoto("Pref") <>""Then

NoPhotoUpdate(dtrPhoto("Pref"))

EndIf

EndWhile

conWhitt.Close()

dtrPhoto.Close()

EndSub

Sub NoPhotoUpdate(ByVal PrefAsInteger)

Dim cmdUpdateAs SqlCommand

cmdUpdate =New SqlCommand("Update tblAuthority Set NoPhoto = 1 Where Pref =" & Pref, conWhitt)

cmdUpdate.ExecuteNonQuery()

EndSub

|||

Hi there

Sorry i didnt reply sooner, i was moving house!

The problem your having is that the NoPhotoUpdate sub cannot access the datareader of the page_load sub.

(its a bit of a git to get your head around at first, then when you do you will wonder how you ever managed without it!)

You might want to get a book on OOP for asp.net - The dummies book one is quite good (and written by a comedian!), but covers only vb1.1 (AFAIK).

Anyways that said..

Private Sub Page_Load(ByVal sender As System.Object, _

ByVal e As System.EventArgs) Handles MyBase.Load
SelectPhoto()

End Sub

Sub SelectPhoto()
Dim cmdPhoto As SqlCommand
Dim dtrPhoto As SqlDataReader

cmdPhoto = New SqlCommand("select AuthorityID,AuthorityName,PREF From qryStaffSearch where AuthorityType='User' Order by AuthorityName", conWhitt)

conWhitt.Open()
dtrPhoto = cmdPhoto.ExecuteReader

While dtrPhoto.Read()

If Not File.Exists("D:WhittNetLive\Web\images\staffphotos\pat_images_resize\" & dtrPhoto("Pref") & ".jpg") And dtrPhoto("Pref") <> "" Then

NoPhotoUpdate(dtrPhoto("Pref"))

End If

End While

conWhitt.Close()

dtrPhoto.Close()

End Sub

Sub NoPhotoUpdate(ByVal Pref As Integer)

Dim strConnectionString As String
strConnectionString = ' Your connection String

Dim DBConn As New SqlConnection(strConnectionString)
Dim DBCmd As New SqlCommand
Dim DBAdap As New SqlDataAdapter
DBConn.Open()

DBCmd = New SqlCommand("Update tblAuthority Set NoPhoto = 1 Where Pref = @.Pref", DBConn)
DBCmd.Parameters.Add("@.Pref", SqlDbType.NVarChar).Value = Pref
DBCmd.ExecuteNonQuery()
DBCmd.Dispose()
DBAdap.Dispose()
DBConn.Close()
DBConn = Nothing

End Sub

The whole @. thing is a safer way to pass paramaters to your SQL

http://weblogs.asp.net/scottgu/archive/2006/09/30/Tip_2F00_Trick_3A00_-Guard-Against-SQL-Injection-Attacks.aspx for a explanation

Notice how each sub is a seperate little program, with one activating the other whilst passing data.

I hope ive been of some help

|||

Thanks that works. Thanks also for the heads up about sql injection attacks. I do normally pass my parameters the safe way but was not aware of the dangers of not doing so.

Enjoy your new house

|||

I'm having the same problem and i have to believe there is a better solution then creating a sep sub and then creating another connection. Based on your solution you should problably just create a second connection in the first sub and just use that, no need for the whole extra nophotoupdate sub.

Having said that there needs to be a solution for activly using the same connection at the same time. In good old ADO days we were able to open many recordsets and execute sql commands all at the same time with one DB connection. There is a way to do this here.

RageMonkey:

Sub NoPhotoUpdate(ByVal Pref As Integer)

Dim strConnectionString As String
strConnectionString = ' Your connection String

Dim DBConn As New SqlConnection(strConnectionString)
Dim DBCmd As New SqlCommand
Dim DBAdap As New SqlDataAdapter
DBConn.Open()

DBCmd = New SqlCommand("Update tblAuthority Set NoPhoto = 1 Where Pref = @.Pref", DBConn)
DBCmd.Parameters.Add("@.Pref", SqlDbType.NVarChar).Value = Pref
DBCmd.ExecuteNonQuery()
DBCmd.Dispose()
DBAdap.Dispose()
DBConn.Close()
DBConn = Nothing

End Sub

|||

I'm having the same problem and i have to believe there is a better solution then creating a sep sub and then creating another connection. Based on your solution you should problably just create a second connection in the first sub and just use that, no need for the whole extra nophotoupdate sub.

Having said that there needs to be a solution for activly using the same connection at the same time. In good old ADO days we were able to open many recordsets and execute sql commands all at the same time with one DB connection. There is a way to do this here.

RageMonkey:

Sub NoPhotoUpdate(ByVal Pref As Integer)

Dim strConnectionString As String
strConnectionString = ' Your connection String

Dim DBConn As New SqlConnection(strConnectionString)
Dim DBCmd As New SqlCommand
Dim DBAdap As New SqlDataAdapter
DBConn.Open()

DBCmd = New SqlCommand("Update tblAuthority Set NoPhoto = 1 Where Pref = @.Pref", DBConn)
DBCmd.Parameters.Add("@.Pref", SqlDbType.NVarChar).Value = Pref
DBCmd.ExecuteNonQuery()
DBCmd.Dispose()
DBAdap.Dispose()
DBConn.Close()
DBConn = Nothing

End Sub

|||

I found the solution on the msdn forums. Seems to only work for SQL 2005

"This is due to a change in the default setting for MARs. It used to be on by default and we changed it to off by default post RC1. So just change your connection string to add it back (add MultipleActiveResultSets=True to connection string)."

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=123691&SiteID=1

Error: StringStartsWith can't accept null parameters

Hi,
I wish to edit security on a certain report that has been published on my report
server. I visit the "Properties" tab in Report Manager, then click on "Security".
I click on "Edit Item Security" and click through the javascript popup about
inheritance. Then I get a page which says simply, "Error - StringStartsWith can't
accept null parameters".
Has anyone encountered this error? I have no clue how to proceed with debugging,
since I can't even find the code that's throwing this error, nor do I know to
which parameter it's trying to apply StringStartsWith.
Any help would be appreciated.
--Adam BlissPlease, tell us which version of Reporting Service you are using. Also
please provide stack trace for this failure. You should be able to locate it
in one of the log files. Log files are located in the LogFiles directory in
Reporting Services. Look at ones like
ReportServer__07_08_2004_##_##_##.log
and
ReportServerWebApp__07_08_2004_##_##_##.log
Look inside appropriate files and search for string 'StringStartsWith'.
Attach about 50 lines around it.
Thank you.
--
Dmitry Vasilevsky, SQL Server Reporting Services Developer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
---
"Adam Bliss" <abliss@.gmail.com> wrote in message
news:c52bcaf.0407081034.6f9bd2a2@.posting.google.com...
> Hi,
> I wish to edit security on a certain report that has been published on my
report
> server. I visit the "Properties" tab in Report Manager, then click on
"Security".
> I click on "Edit Item Security" and click through the javascript popup
about
> inheritance. Then I get a page which says simply, "Error -
StringStartsWith can't
> accept null parameters".
> Has anyone encountered this error? I have no clue how to proceed with
debugging,
> since I can't even find the code that's throwing this error, nor do I know
to
> which parameter it's trying to apply StringStartsWith.
> Any help would be appreciated.
> --Adam Bliss|||Has anyone solved this?
I am hitting this error when using the Sample Security Extension supplied by M$. Eventviewer tells me that Report server could not load the forms extension.
w3wp!ui!1!9/6/2006-09:09:40:: e ERROR: StringStartsWith can't accept null parameters
w3wp!ui!1!9/6/2006-09:09:40:: e ERROR: HTTP status code --> 500
--Details--
System.ArgumentException: StringStartsWith can't accept null parameters
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!1!9/6/2006-09:09:41:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
Thanks,
Zac
From http://www.developmentnow.com/g/115_2004_7_0_0_448611/Error-StringStartsWith-cant-accept-null-parameters.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||Did you get this resolved? I'm getting exactly the same error message in different circumstances..
From http://www.developmentnow.com/g/115_2004_7_0_0_448611/Error-StringStartsWith-cant-accept-null-parameters.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||Got this error when trying to make RS work with forms authentication overr SSL. Though i can browse ReportServer folder, trying to access Reports virtual directory brings this error up.
Anyone has solved this issue
From http://developmentnow.com/g/115_2004_7_0_0_448611/Error-StringStartsWith-cant-accept-null-parameters.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||Hi
I'm also getting a very similar error. Any solutions for the same?
Any help would be appreciated
From http://www.developmentnow.com/g/115_2004_7_0_0_448611/Error-StringStartsWith-cant-accept-null-parameters.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

Error: Server: Msg 1101, Level 17, State 10 when I run script

Hi All,
I can't not run the query to update data but it raice an error as below:
"Server: Msg 1101, Level 17, State 10, Line 1
Could not allocate new page for database 'TEMPDB'. There are no more pages
available in filegroup DEFAULT. Space can be created by dropping objects,
adding additional files, or allowing file growth."
HDD free space: 5GB
RAM: 1GB
CPU: 2.8MHz
SQL server 2000
Windows 2000 server
What should I do?
Please advice me on this.
Thanks in advance,
TN
As per the error message: Increate the size for your tempdb database (data, not log).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TN" <TN@.discussions.microsoft.com> wrote in message
news:72E79234-7E66-4C0F-9198-A2564A99BEE4@.microsoft.com...
> Hi All,
> I can't not run the query to update data but it raice an error as below:
> "Server: Msg 1101, Level 17, State 10, Line 1
> Could not allocate new page for database 'TEMPDB'. There are no more pages
> available in filegroup DEFAULT. Space can be created by dropping objects,
> adding additional files, or allowing file growth."
> HDD free space: 5GB
> RAM: 1GB
> CPU: 2.8MHz
> SQL server 2000
> Windows 2000 server
> What should I do?
> Please advice me on this.
> Thanks in advance,
> TN
>
|||My tempdb is umlimited file growth.
"Tibor Karaszi" wrote:

> As per the error message: Increate the size for your tempdb database (data, not log).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "TN" <TN@.discussions.microsoft.com> wrote in message
> news:72E79234-7E66-4C0F-9198-A2564A99BEE4@.microsoft.com...
>
>
|||Sometimes autogrow doesn't grow the files fast enough for the operation that needs the storage.
Solution is to pre-allocate storage.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TN" <TN@.discussions.microsoft.com> wrote in message
news:473EFAC4-F9E0-4CE8-A895-C146BCE11C6C@.microsoft.com...[vbcol=seagreen]
> My tempdb is umlimited file growth.
> "Tibor Karaszi" wrote:

Error: Server Agent cant find dts file

Im trying to schedule an integration sevice package with no anvile. I have tried both running it in Agent under Integration services and operation system (CmdExec) and still wont work. Under CmdExec, the command is /FILE "C:\Documents and Settings\ebuah\My Documents\Visual Studio 2005\Projects\Swamp_Solution\FIRSTTIME_DOWNLOAD\SSIS_ACT.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF. In the advance tab, I checked outfile to a log.txt file so as to read the log if there was any errors. The account running the job is the same account that sql server agent services is running which would only mean I really dont need any proxy account to run the job. When i run the job under CmdExec, i get the error

Message
Executed as user: CYPRESS\Administrator. The process could not be created for step 1 of job 0x529C255F20199B40A83858B1CCC875F2 (reason: The system cannot find the file specified). The step failed.

when I run the same package under integeration system, the error I get in the logg file is

<record>
<event>OnError</event>
<message>System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction)</message>
<computer>SPIDERMAN</computer>
<operator>CYPRESS\Administrator</operator>
<source>ACT TABLE 250</source>
<sourceid>{99b92f4c-686d-47a6-b136-4d1ec698c837}</sourceid>
<executionid>{CD95BB1A-7FE4-468B-904D-C02B3FEBF1B0}</executionid>
<starttime>4/17/2006 1:20:47 PM</starttime>
<endtime>4/17/2006 1:20:47 PM</endtime>
<datacode>-1073450910</datacode>
<databytes>0x</databytes>
</record>

If you ask me, I dont know whats going on but I am very fustrated. Have been working on this for 4 days now. I really really need help.

The error is right there. "Data source name not found".

I would guess that either you haven't deployed the ODBC DSN on that machine or the account you are running it as doesn't have permission to see it.

-Jamie

|||I am running on a 64x machine on which i installed the 64x version of SSIS. The odbc driver in installed in the wow folder (32 bit). My packages are set up to execute in 32bit so they can see the odbc driver. Do you think that under server agent, its not able to see the 32bit odbc driver. (by the way, the account i running under is an admin account, has rights to everything)

Also, in the process of debugging, I tried a few things to eliminate causing senarios. I created a simple parkage that doesnt use the odbc drive. It does a staight pull from one sql server table to another using ole connection . When i run that under Sever Agent with Integration services, it runs smoothly. For the same simple package, when i run under CmdExec, I get the error: The process could not be created for step 1 of job 0xF791BD51E4709E48AD83FB56038ECF95 (reason: The system cannot find the file specified). The step failed. So, my question is what is wrong. It runs fine under integeration services but errors out under CmdExec.

From my first test, I made an assumption that only running under intergration service in Sever Agent will work since its passed the test. Based on that, I changed my simple package to include an odbc source connection (pulling from a remote DB/4 FC server with 32bit DB/4 odbc driver installed in wow on 64bit). When I run the package in Agent under integration services, I got an error: The package execution failed. The step failed. Luckly, a detailed error information by the package log indicated

<message>System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction)</message>

which was my intial error. So Jamie, I think you are right that it has something to do with the DNS. Since the odbc drive is registered in the 32bit DNS, Server Agent is not able to see it.

If you can help me answer my trial error as to how a package could runs fine under intergeration services but breakes under CmdExec (does the command sting have to be different) and also if there is a way to get around this driver issue. Thanks.|||I tried a 32bit install of sql server on a 32bit machine and the job run just fine so the problem is that Sever Agent on 64bit machine can only see the 64x DNS and not 32 but in SSIS, the IDE give you the option to run in 64bit debugging mode or not, and when you choose not to run in 64 mode, it able to see the 32bit DNS. That was why it was able to run in SSIS just fine but not in Server Agent. In summary, make sure your driver has a 64bit version before developing packages to be run in Server Agent on a 64bit machine.|||I am having the same problem. It looks like when I run the SSIS package through the SQL Server Management Studio or through Visual Studio, the package honors the 64 bit runtime option. But, when I run it through the SQL Server Agent, it doesn't. I did some checking, and it looks like the package file doesn't even contain that flag. Is there some way to alter the command line in the job step to force the package to run in 32 bit mode?|||You could just use the CmdExec job step and specify the 32 bit dtexec program. This has other benefits, in that you have job step logging for CmdExec steps, unlike the SSIS subssytem. This can be very usefull in troubleshooting, e.g. Scheduled Packages
(http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html)|||Thanks. That seems to be working.

Error: Server Agent cant find dts file

Im trying to schedule an integration sevice package with no anvile. I have tried both running it in Agent under Integration services and operation system (CmdExec) and still wont work. Under CmdExec, the command is /FILE "C:\Documents and Settings\ebuah\My Documents\Visual Studio 2005\Projects\Swamp_Solution\FIRSTTIME_DOWNLOAD\SSIS_ACT.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF. In the advance tab, I checked outfile to a log.txt file so as to read the log if there was any errors. The account running the job is the same account that sql server agent services is running which would only mean I really dont need any proxy account to run the job. When i run the job under CmdExec, i get the error

Message
Executed as user: CYPRESS\Administrator. The process could not be created for step 1 of job 0x529C255F20199B40A83858B1CCC875F2 (reason: The system cannot find the file specified). The step failed.

when I run the same package under integeration system, the error I get in the logg file is

<record>
<event>OnError</event>
<message>System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction)</message>
<computer>SPIDERMAN</computer>
<operator>CYPRESS\Administrator</operator>
<source>ACT TABLE 250</source>
<sourceid>{99b92f4c-686d-47a6-b136-4d1ec698c837}</sourceid>
<executionid>{CD95BB1A-7FE4-468B-904D-C02B3FEBF1B0}</executionid>
<starttime>4/17/2006 1:20:47 PM</starttime>
<endtime>4/17/2006 1:20:47 PM</endtime>
<datacode>-1073450910</datacode>
<databytes>0x</databytes>
</record>

If you ask me, I dont know whats going on but I am very fustrated. Have been working on this for 4 days now. I really really need help.

The error is right there. "Data source name not found".

I would guess that either you haven't deployed the ODBC DSN on that machine or the account you are running it as doesn't have permission to see it.

-Jamie

|||I am running on a 64x machine on which i installed the 64x version of SSIS. The odbc driver in installed in the wow folder (32 bit). My packages are set up to execute in 32bit so they can see the odbc driver. Do you think that under server agent, its not able to see the 32bit odbc driver. (by the way, the account i running under is an admin account, has rights to everything)

Also, in the process of debugging, I tried a few things to eliminate causing senarios. I created a simple parkage that doesnt use the odbc drive. It does a staight pull from one sql server table to another using ole connection . When i run that under Sever Agent with Integration services, it runs smoothly. For the same simple package, when i run under CmdExec, I get the error: The process could not be created for step 1 of job 0xF791BD51E4709E48AD83FB56038ECF95 (reason: The system cannot find the file specified). The step failed. So, my question is what is wrong. It runs fine under integeration services but errors out under CmdExec.

From my first test, I made an assumption that only running under intergration service in Sever Agent will work since its passed the test. Based on that, I changed my simple package to include an odbc source connection (pulling from a remote DB/4 FC server with 32bit DB/4 odbc driver installed in wow on 64bit). When I run the package in Agent under integration services, I got an error: The package execution failed. The step failed. Luckly, a detailed error information by the package log indicated

<message>System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction)</message>

which was my intial error. So Jamie, I think you are right that it has something to do with the DNS. Since the odbc drive is registered in the 32bit DNS, Server Agent is not able to see it.

If you can help me answer my trial error as to how a package could runs fine under intergeration services but breakes under CmdExec (does the command sting have to be different) and also if there is a way to get around this driver issue. Thanks.|||I tried a 32bit install of sql server on a 32bit machine and the job run just fine so the problem is that Sever Agent on 64bit machine can only see the 64x DNS and not 32 but in SSIS, the IDE give you the option to run in 64bit debugging mode or not, and when you choose not to run in 64 mode, it able to see the 32bit DNS. That was why it was able to run in SSIS just fine but not in Server Agent. In summary, make sure your driver has a 64bit version before developing packages to be run in Server Agent on a 64bit machine.|||I am having the same problem. It looks like when I run the SSIS package through the SQL Server Management Studio or through Visual Studio, the package honors the 64 bit runtime option. But, when I run it through the SQL Server Agent, it doesn't. I did some checking, and it looks like the package file doesn't even contain that flag. Is there some way to alter the command line in the job step to force the package to run in 32 bit mode?|||You could just use the CmdExec job step and specify the 32 bit dtexec program. This has other benefits, in that you have job step logging for CmdExec steps, unlike the SSIS subssytem. This can be very usefull in troubleshooting, e.g. Scheduled Packages
(http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html)|||Thanks. That seems to be working.