connect from ASP app: created

Showing posts with label created. Show all posts

Tuesday, March 27, 2012

can't get in anymore

I installed SQL 2005 on a new machine last week. Created a database using
scripts. Worked fine for a few days.
Yesterday, I attached a database that had been created on another machine,
with SQL 2000. Seemed to work fine. I closed SQL Server to work on something
else, then opened it back up. It won't let me in now. It says that it
doesn't allow remote connections, even though I am doing it from the same
machine that it resides on.
Text of the message is below the line at the bottom of this.
I tried changing the way I log in, including Windows Authentication, SQL
Server authentication, using my network name, and then using the user name I
created just for this thing when I installed SQL Server. I alwasy get the
same message. I also tried connecting remotely from another machine.
I was able to use this same machine to connect to another SQL Server
instance on the network, so it's apparent that the installation of SQL
Server isn't messed up.
I know that I will probably get asked about an admin username and password,
but I don't know what mine is. I tried sa with no password, but it didn't
work.
This is really causing some problems and I have something due at noon today.
Any help appreciated.
If I uninstalled SQL Server and re-install, will that let me in then?
-----
TITLE: Connect to Server
--
Cannot connect to SERV423.
--
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: 2)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
--
BUTTONS:
OK
--did you enable TCP/IP and gave a proper IP Address in network
configuration under configuration manager?|||I don't recall that being part of the installation. Is it something I can
change now?
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegroups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>|||I had never seen Config mgr before you mentioned it. Opening it up showed me
that the services weren't running. I started them and it works now.
thanks
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegroups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>

can't get in anymore

I installed SQL 2005 on a new machine last week. Created a database using
scripts. Worked fine for a few days.
Yesterday, I attached a database that had been created on another machine,
with SQL 2000. Seemed to work fine. I closed SQL Server to work on something
else, then opened it back up. It won't let me in now. It says that it
doesn't allow remote connections, even though I am doing it from the same
machine that it resides on.
Text of the message is below the line at the bottom of this.
I tried changing the way I log in, including Windows Authentication, SQL
Server authentication, using my network name, and then using the user name I
created just for this thing when I installed SQL Server. I alwasy get the
same message. I also tried connecting remotely from another machine.
I was able to use this same machine to connect to another SQL Server
instance on the network, so it's apparent that the installation of SQL
Server isn't messed up.
I know that I will probably get asked about an admin username and password,
but I don't know what mine is. I tried sa with no password, but it didn't
work.
This is really causing some problems and I have something due at noon today.
Any help appreciated.
If I uninstalled SQL Server and re-install, will that let me in then?
-----
TITLE: Connect to Server
Cannot connect to SERV423.
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: 2)
For help, click:
http://go.microsoft.com/fwlink?ProdN...2&LinkId=20476
BUTTONS:
OK
did you enable TCP/IP and gave a proper IP Address in network
configuration under configuration manager?
|||I don't recall that being part of the installation. Is it something I can
change now?
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegr oups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>
|||I had never seen Config mgr before you mentioned it. Opening it up showed me
that the services weren't running. I started them and it works now.
thanks
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegr oups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>

can't get in anymore

I installed SQL 2005 on a new machine last week. Created a database using
scripts. Worked fine for a few days.
Yesterday, I attached a database that had been created on another machine,
with SQL 2000. Seemed to work fine. I closed SQL Server to work on something
else, then opened it back up. It won't let me in now. It says that it
doesn't allow remote connections, even though I am doing it from the same
machine that it resides on.
Text of the message is below the line at the bottom of this.
I tried changing the way I log in, including Windows Authentication, SQL
Server authentication, using my network name, and then using the user name I
created just for this thing when I installed SQL Server. I alwasy get the
same message. I also tried connecting remotely from another machine.
I was able to use this same machine to connect to another SQL Server
instance on the network, so it's apparent that the installation of SQL
Server isn't messed up.
I know that I will probably get asked about an admin username and password,
but I don't know what mine is. I tried sa with no password, but it didn't
work.
This is really causing some problems and I have something due at noon today.
Any help appreciated.
If I uninstalled SQL Server and re-install, will that let me in then?
----
--
TITLE: Connect to Server
--
Cannot connect to SERV423.
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: 2)
For help, click:
tID=2&LinkId=20476" target="_blank">http://go.microsoft.com/fwlink?Prod...=2&LinkId=20476
BUTTONS:
OK
--did you enable TCP/IP and gave a proper IP Address in network
configuration under configuration manager?|||I don't recall that being part of the installation. Is it something I can
change now?
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegroups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>|||I had never seen Config mgr before you mentioned it. Opening it up showed me
that the services weren't running. I started them and it works now.
thanks
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegroups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>sql

Sunday, March 25, 2012

Cant get Access Database Synchronizer set up on client machine

I have created a PPC application that uses ADS to synchronize my sqlce db with a desktop MS Access database. It works fine on my computers, but my client cant get it to work on his. Here is the situation.

His "Computer Name" as it's stated in his 'My Computer' properties is "PAVSGP024FE.NWFSC.NOAA.GOV"

However his Access.MDW File is located in the directory "C:\Documents and Settings\Joe Nobody\Application Data\Microsoft\Access\System.MDW".

There is no directory called "C:\Documents and Settings\PAVSGP024FE.NWFSC.NOAA.GOV\Application Data\Microsoft\Access\System.MDW".

His current config.xml file looks like this.

<?xml version="1.0" encoding="UTF-8"?>
<SystemNode>
<AccessDB>C:\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.mdb</AccessDB>
<DeviceDB>\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.sdf</DeviceDB>
<Login>Joe Nobody</Login>
<URL>http://Joe Nobody:1024/</URL>
<WinDir>C:\</WinDir>
</SystemNode>

He has tried adding port 1024 as an exception for his firewall settings, has installed Access Database Synchronizer on his computer, and I have also tried using the "long" computer name as the url setting in the config file. (i.e. <URL>http://PAVSGP024FE.NWFSC.NOAA.GOV:1024/</URL> but this throws the error

"The HTTP request failed due to incorrect format or content. Try restarting the IIS server.[]"

I dont know what else to try! Anybody have any suggestions?

I have had the same problems when I first installed. THen for some reason things started working. Now a few weeks later, when I get back to trying it, no work anymore. I suggest you read the readme.doc that comes with it. THere are some things to check there. Make sure IIS is running. THen you add a 1024 port if you have the firewall enabled. I also had some success when I manually copied the .cab file to the device, then installed that way. I don't think I have ever got it to work just downloading the sample project.

Another thing to verify is that your internet connection is going from device to desktop. Open IE and try to open http://<computer>:1024/. Presently, I am unable to do this so I think something is wrong on my Desktop platform. I am going to try another platform that used to work.

|||

Tried to run the synchronizer on the other platform that it used to work on also. Now that one is not working either. I went through all the steps I know of to get it working, no luck. I cannot get the IE to link up to the web service either which I am thinking must be the main problem.

I am sorry to say, I need to give up trying to get it to work now.

|||

Wanted to check, have you got it running now.

Please note: You do not IIS to run ADS applications. Stop the IIS and try.

The path of the .msw file should be C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW.

So if his user name on the computer is "Joe Nobody" then specify the path as "C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW" as indicated in your post.

|||

We did finally get this working but, only because we gave up installing it on this particular computer. His computer was part of a business network and something about it would not allow this to work. Once he installed everything on a non-network computer everything worked as it should. So, unfortunately, we never did actually get to the root of this particular problem.

Mike

Cant get Access Database Synchronizer set up on client machine

His "Computer Name" as it's stated in his 'My Computer' properties is "PAVSGP024FE.NWFSC.NOAA.GOV"

However his Access.MDW File is located in the directory "C:\Documents and Settings\Joe Nobody\Application Data\Microsoft\Access\System.MDW".

There is no directory called "C:\Documents and Settings\PAVSGP024FE.NWFSC.NOAA.GOV\Application Data\Microsoft\Access\System.MDW".

His current config.xml file looks like this.

"The HTTP request failed due to incorrect format or content. Try restarting the IIS server.[]"

I dont know what else to try! Anybody have any suggestions?

|||

I am sorry to say, I need to give up trying to get it to work now.

|||

Wanted to check, have you got it running now.

Please note: You do not IIS to run ADS applications. Stop the IIS and try.

The path of the .msw file should be C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW.

So if his user name on the computer is "Joe Nobody" then specify the path as "C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW" as indicated in your post.

|||

Mike

Can't find properties

This is the first time I've used SSRS. I've created a report and in preparation for deploying it I am trying to find where I set the properties. In Visual Studio 2005, in the Solution Explorer I right click on my .rdl file and select properties. The only properties listed are File Name (which is changeable) and File Path (which is not changeable). The property pages icon in the same dialog box is greyed out. Am I missing someghing? Any help would be greatly appreciated.

Thanks.

Go to the layout tab and try clicking on an area outside of the white area where you place your report objects. This should give you the report properties. Is that what you're looking for?

There is also a report properties dialog that will let you set most of the report properties. Go to the Report menu and select Report Properties. You have to have a report open in the designer for the Report menu to even be there.

|||

Thank you very much for the tip, I can see a number of properties of the report. However I still cannot find where to set the following properties

OverWriteDataSources:

TargetDataSourceFolder:

TargetRootFolder:

TargetServerURL:

I couldn't see these deployment properties where you pointed. Am I still missing something? Sorry if I seem kind of slow.

|||

These are properties of the report solution:

After you opened a report project, go to the VS Solution Explorer window. Right-click your report solution and select "Properties". The popup-dialog will contain the four properties you are looking for.

-- Robert

|||

Robert,

Thank you for the feed back. I've tried this many times now and I keep getting the same thing i.e. Open my project report, go to the VS Solution Explorer window under Reports I highlight the name of my report (Report1.rdl) right click on that report and I get a property window which only has two properties File Name: (which is editable) and File Path: (which is uneditable).

Do I possibly not have SSRS installed properly? This seems a simple thing but it is driving me crazy. Thanks for your help.

Bill

|||

Right-click on the root of the tree shown in the VS Solution Explorer. The root of the tree represents the entire report project - do not select a particular report.

-- Robert

|||

Robert,

Thank you so very much, I tried every level in the VS Solution Explorer BUT the root. Who would have thought! All of the documentation and tutorials were not as clear as your last note. Thank you again.

Bill

Tuesday, March 20, 2012

Can''t drop trigger assembly

Created an assembly based on this article...

http://sqljunkies.com/Article/4CD01686-5178-490C-A90A-5AEEF5E35915.scuk

Now I want to make changes and redeploy the assembly but when I try to drop I get this.

IF EXISTS (SELECT * FROM sys.assemblies asms WHERE asms.name = N'AuditCommon')

DROP ASSEMBLY [AuditCommon]

Msg 6590, Level 16, State 1, Line 3

DROP ASSEMBLY failed because 'AuditCommon' is referenced by object 'clr_trigger'.

Any ideas?

Figured it out. clr_trigger was a trigger that I created somewhere along the way which was dependent upon the assembly. It didn't appear anywhere in SQL Manager Studio so I thought that it was some sort of system object.|||A late reply,

using show dependencies, list out those need to removed. Remove the listed first and then drop the assembly.

Can't drop trigger assembly

Created an assembly based on this article...

http://sqljunkies.com/Article/4CD01686-5178-490C-A90A-5AEEF5E35915.scuk

Now I want to make changes and redeploy the assembly but when I try to drop I get this.

IF EXISTS (SELECT * FROM sys.assemblies asms WHERE asms.name = N'AuditCommon')

DROP ASSEMBLY [AuditCommon]

Msg 6590, Level 16, State 1, Line 3

DROP ASSEMBLY failed because 'AuditCommon' is referenced by object 'clr_trigger'.

Any ideas?

using show dependencies, list out those need to removed. Remove the listed first and then drop the assembly.

can't drop trigger

Hi,
I just created a tirgger. when I tried to drop it, it say "Cannot drop the
trigger 'trigger_name', because it does not exist in the system catalog." But
it shows when I query as:
SELECT *
FROM sysobjects o INNER JOIN syscomments c
ON o.id = c.id
WHERE o.type = 'TR' and o.name = 'trigger_name'
when I tried to create again, it failed "There is already an object named
'trigger_name' in the database.
what can I do? ThanksJen wrote:
> Hi,
> I just created a tirgger. when I tried to drop it, it say "Cannot drop the
> trigger 'trigger_name', because it does not exist in the system catalog." But
> it shows when I query as:
> SELECT *
> FROM sysobjects o INNER JOIN syscomments c
> ON o.id = c.id
> WHERE o.type = 'TR' and o.name = 'trigger_name'
> when I tried to create again, it failed "There is already an object named
> 'trigger_name' in the database.
> what can I do? Thanks
You should always used schema-qualified object names, i.e.
"dbo.MyTriggerName". Sounds like you're dealing with a schema-naming
issue, "dbo.MyTriggerName" vs. "userA.MyTriggerName".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I used "create trigger dbo.trigger_name on userA.table_name..."
I tried to user "sp_helptrigger userA.table_name" it says "Incorrect syntax
near '.'"
How can I drop the trigger? How can I view the trigger? Thanks
"Tracy McKibben" wrote:
> Jen wrote:
> > Hi,
> >
> > I just created a tirgger. when I tried to drop it, it say "Cannot drop the
> > trigger 'trigger_name', because it does not exist in the system catalog." But
> > it shows when I query as:
> >
> > SELECT *
> > FROM sysobjects o INNER JOIN syscomments c
> > ON o.id = c.id
> > WHERE o.type = 'TR' and o.name = 'trigger_name'
> >
> > when I tried to create again, it failed "There is already an object named
> > 'trigger_name' in the database.
> >
> > what can I do? Thanks
> You should always used schema-qualified object names, i.e.
> "dbo.MyTriggerName". Sounds like you're dealing with a schema-naming
> issue, "dbo.MyTriggerName" vs. "userA.MyTriggerName".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||is it in SQL 2000 or 2005
try specifying someting like
Drop Trigger <TriggerName>
ON <Database or ALL Server>
Maninder
MCDBA
On Jan 30, 1:54 pm, Tracy McKibben <t...@.realsqlguy.com> wrote:
> Jen wrote:
> > Hi,
> > I just created a tirgger. when I tried to drop it, it say "Cannot drop the
> > trigger 'trigger_name', because it does not exist in the system catalog." But
> > it shows when I query as:
> > SELECT *
> > FROM sysobjects o INNER JOIN syscomments c
> > ON o.id = c.id
> > WHERE o.type = 'TR' and o.name = 'trigger_name'
> > when I tried to create again, it failed "There is already an object named
> > 'trigger_name' in the database.
> > what can I do? Thanks
> You should always used schema-qualified object names, i.e.
> "dbo.MyTriggerName". Sounds like you're dealing with a schema-naming
> issue, "dbo.MyTriggerName" vs. "userA.MyTriggerName".
> --
> Tracy McKibben
> MCDBAhttp://www.realsqlguy.com- Hide quoted text -
> - Show quoted text -|||It's sql2000. I got "Incorrect syntax near the keyword 'on'".
"Maninder" wrote:
> is it in SQL 2000 or 2005
> try specifying someting like
> Drop Trigger <TriggerName>
> ON <Database or ALL Server>
> Maninder
> MCDBA
> On Jan 30, 1:54 pm, Tracy McKibben <t...@.realsqlguy.com> wrote:
> > Jen wrote:
> > > Hi,
> >
> > > I just created a tirgger. when I tried to drop it, it say "Cannot drop the
> > > trigger 'trigger_name', because it does not exist in the system catalog." But
> > > it shows when I query as:
> >
> > > SELECT *
> > > FROM sysobjects o INNER JOIN syscomments c
> > > ON o.id = c.id
> > > WHERE o.type = 'TR' and o.name = 'trigger_name'
> >
> > > when I tried to create again, it failed "There is already an object named
> > > 'trigger_name' in the database.
> >
> > > what can I do? Thanks
> >
> > You should always used schema-qualified object names, i.e.
> > "dbo.MyTriggerName". Sounds like you're dealing with a schema-naming
> > issue, "dbo.MyTriggerName" vs. "userA.MyTriggerName".
> >
> > --
> > Tracy McKibben
> > MCDBAhttp://www.realsqlguy.com- Hide quoted text -
> >
> > - Show quoted text -
>
>|||Jen wrote:
> I used "create trigger dbo.trigger_name on userA.table_name..."
> I tried to user "sp_helptrigger userA.table_name" it says "Incorrect syntax
> near '.'"
>
sp_helptrigger 'userA.table_name'
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||As Tracy suggestd, try using the Object owner in the drop statement.
Or if you are db_owner or a sa you can drop the Trigger with the
Schemaname.Triggername
Maninder
MCDBA
On Jan 30, 2:23 pm, Jen <J...@.discussions.microsoft.com> wrote:
> It's sql2000. I got "Incorrect syntax near the keyword 'on'".
>
> "Maninder" wrote:
> > is it in SQL 2000 or 2005
> > try specifying someting like
> > Drop Trigger <TriggerName>
> > ON <Database or ALL Server>
> > Maninder
> > MCDBA
> > On Jan 30, 1:54 pm, Tracy McKibben <t...@.realsqlguy.com> wrote:
> > > Jen wrote:
> > > > Hi,
> > > > I just created a tirgger. when I tried to drop it, it say "Cannot drop the
> > > > trigger 'trigger_name', because it does not exist in the system catalog." But
> > > > it shows when I query as:
> > > > SELECT *
> > > > FROM sysobjects o INNER JOIN syscomments c
> > > > ON o.id = c.id
> > > > WHERE o.type = 'TR' and o.name = 'trigger_name'
> > > > when I tried to create again, it failed "There is already an object named
> > > > 'trigger_name' in the database.
> > > > what can I do? Thanks
> > > You should always used schema-qualified object names, i.e.
> > > "dbo.MyTriggerName". Sounds like you're dealing with a schema-naming
> > > issue, "dbo.MyTriggerName" vs. "userA.MyTriggerName".
> > > --
> > > Tracy McKibben
> > > MCDBAhttp://www.realsqlguy.com-Hide quoted text -
> > > - Show quoted text -- Hide quoted text -
> - Show quoted text -|||Thanks. I droped it. Even though I specify "dbo.trigger_name" in create
trigger, but the trigger's owner is "userA" by checking sysobjects table. Is
it strange?
Thanks
"Maninder" wrote:
> As Tracy suggestd, try using the Object owner in the drop statement.
> Or if you are db_owner or a sa you can drop the Trigger with the
> Schemaname.Triggername
> Maninder
> MCDBA
>
> On Jan 30, 2:23 pm, Jen <J...@.discussions.microsoft.com> wrote:
> > It's sql2000. I got "Incorrect syntax near the keyword 'on'".
> >
> >
> >
> > "Maninder" wrote:
> > > is it in SQL 2000 or 2005
> > > try specifying someting like
> > > Drop Trigger <TriggerName>
> > > ON <Database or ALL Server>
> >
> > > Maninder
> > > MCDBA
> > > On Jan 30, 1:54 pm, Tracy McKibben <t...@.realsqlguy.com> wrote:
> > > > Jen wrote:
> > > > > Hi,
> >
> > > > > I just created a tirgger. when I tried to drop it, it say "Cannot drop the
> > > > > trigger 'trigger_name', because it does not exist in the system catalog." But
> > > > > it shows when I query as:
> >
> > > > > SELECT *
> > > > > FROM sysobjects o INNER JOIN syscomments c
> > > > > ON o.id = c.id
> > > > > WHERE o.type = 'TR' and o.name = 'trigger_name'
> >
> > > > > when I tried to create again, it failed "There is already an object named
> > > > > 'trigger_name' in the database.
> >
> > > > > what can I do? Thanks
> >
> > > > You should always used schema-qualified object names, i.e.
> > > > "dbo.MyTriggerName". Sounds like you're dealing with a schema-naming
> > > > issue, "dbo.MyTriggerName" vs. "userA.MyTriggerName".
> >
> > > > --
> > > > Tracy McKibben
> > > > MCDBAhttp://www.realsqlguy.com-Hide quoted text -
> >
> > > > - Show quoted text -- Hide quoted text -
> >
> > - Show quoted text -
>
>|||> Even though I specify "dbo.trigger_name" in create
> trigger, but the trigger's owner is "userA" by checking sysobjects table. Is
> it strange?
Yes, that is strange. If you can provide a repro, we can submit a bug report. If you create an
object, specifying dbo, then that object will be owned by dbo, or you would get an error (if you
don't have permissions to do so). Unless you do something like:
CREATE TRIGGER [dbo.mytrigger]
CREATE TRIGGER "dbo.mytrigger"
Now the name of the trigger will be "dbo.mytrigger" and the owner would be whoever created the
trigger.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jen" <Jen@.discussions.microsoft.com> wrote in message
news:CD8044B8-FD3D-4759-8437-EB974F1E0017@.microsoft.com...
> Thanks. I droped it. Even though I specify "dbo.trigger_name" in create
> trigger, but the trigger's owner is "userA" by checking sysobjects table. Is
> it strange?
> Thanks
> "Maninder" wrote:
>> As Tracy suggestd, try using the Object owner in the drop statement.
>> Or if you are db_owner or a sa you can drop the Trigger with the
>> Schemaname.Triggername
>> Maninder
>> MCDBA
>>
>> On Jan 30, 2:23 pm, Jen <J...@.discussions.microsoft.com> wrote:
>> > It's sql2000. I got "Incorrect syntax near the keyword 'on'".
>> >
>> >
>> >
>> > "Maninder" wrote:
>> > > is it in SQL 2000 or 2005
>> > > try specifying someting like
>> > > Drop Trigger <TriggerName>
>> > > ON <Database or ALL Server>
>> >
>> > > Maninder
>> > > MCDBA
>> > > On Jan 30, 1:54 pm, Tracy McKibben <t...@.realsqlguy.com> wrote:
>> > > > Jen wrote:
>> > > > > Hi,
>> >
>> > > > > I just created a tirgger. when I tried to drop it, it say "Cannot drop the
>> > > > > trigger 'trigger_name', because it does not exist in the system catalog." But
>> > > > > it shows when I query as:
>> >
>> > > > > SELECT *
>> > > > > FROM sysobjects o INNER JOIN syscomments c
>> > > > > ON o.id = c.id
>> > > > > WHERE o.type = 'TR' and o.name = 'trigger_name'
>> >
>> > > > > when I tried to create again, it failed "There is already an object named
>> > > > > 'trigger_name' in the database.
>> >
>> > > > > what can I do? Thanks
>> >
>> > > > You should always used schema-qualified object names, i.e.
>> > > > "dbo.MyTriggerName". Sounds like you're dealing with a schema-naming
>> > > > issue, "dbo.MyTriggerName" vs. "userA.MyTriggerName".
>> >
>> > > > --
>> > > > Tracy McKibben
>> > > > MCDBAhttp://www.realsqlguy.com-Hide quoted text -
>> >
>> > > > - Show quoted text -- Hide quoted text -
>> >
>> > - Show quoted text -
>>|||We had the same Problem with the windows user accounts.
I had a Workaround for this problem.
I Created a Trigger on the Database for Events we need to capture like
Create_table,Create_procedure
So,every time a user creates a object this trigger Fires and renames
the schema to dbo for the object.
or Use ALTER SCHEMA for single use.
Maninder
MCDBAsql

Monday, March 19, 2012

cant display calculated members

I have created a few calculated members under one dimension (meaning the parent dimension is not Measures, but other dimensions). It can be showed in the Analysis Manager, but cannot be displayed in MS Excel PivotTable (MS Office 2k, xp, even 2003). Is there any solution to display the calculated members (as with the dimension) in Excel PivotTable? vba code needed? service pack needed?Don;t know whether the SP may fix or not, but you can try though.

BTW what is the level of SP on OLAP & SQL?|||Originally posted by Satya
Don;t know whether the SP may fix or not, but you can try though.

BTW what is the level of SP on OLAP & SQL?

i have installed the service pack 3 for SQL Server 2000 & Analysis Services (OLAP); sp4 for Windows 2k; MS Office 2003... but seems no change with the presentation of the Excel PivotTable from OLAP cube... still can't display the calculated members under the dimensions. Or is there anyway to force the calculated members be displayed under the dimensions?|||Any error or information during this process?

I feel user interface is not able to simulate the data contained
in the dimension using a local cube. This may be because the estimated size of the dimension is large or possibly because it uses a feature not
supported in local cubes.
HTH|||I think i got the solution for this...
When i create a calculated member in Calculated Member Builder, besides changing the Parent dimension, need also to specify the Parent member. Then only the calculated member will be displayed under the specified dimension in MS Excel XP/2003 PivotTable (Excel 2k doesn't support this feature). At least we know that the newer version of Excel has solved this problem.
Really thanks a lot for all the guidance & advices.

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; 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.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Can't Deploy AdventureWorks Database

Hi All,

For some reason, I encountered the following error (after deployment during processing):

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Sunday, March 11, 2012

Can't Deploy AdventureWorks Database

Hi All,

For some reason, I encountered the following error (after deployment during processing):

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Can't delete Replicated Database

I was just experimenting with something in replication and created a test
database called "ReplicationTest"
This is on a server that is currently a subscriber for other databases, but I
thought I'd also be able to set up a publication from "ReplicationTest" Db.
I tried to create a publication and got the error:
Error 14294 supply either @.Job_id or @.Job_name to identify the job.
What does that mean ?
So I said "to heck with it" (or something like that) and decided to just
delete ReplicationTest database since I got stuck & had real work to do and
no publication had been created. But now it won't let me delete
ReplicationTest database because it says it's being used for replication ....
.... So, what should I try ?
Before you can delete it.
Right click on the replication folder on your enterprise manager treeview,
click on the configure publishers, subscribers, distributions on the context
menu that pops up, go to the publication database tabs and make sure you
untick the boxes next to Replication Test.
Once that is done you can delete the db.
"Gabriel D via droptable.com" wrote:

> I was just experimenting with something in replication and created a test
> database called "ReplicationTest"
> This is on a server that is currently a subscriber for other databases, but I
> thought I'd also be able to set up a publication from "ReplicationTest" Db.
>
> I tried to create a publication and got the error:
> Error 14294 supply either @.Job_id or @.Job_name to identify the job.
> What does that mean ?
>
> So I said "to heck with it" (or something like that) and decided to just
> delete ReplicationTest database since I got stuck & had real work to do and
> no publication had been created. But now it won't let me delete
> ReplicationTest database because it says it's being used for replication ....
> .... So, what should I try ?
>

Can't delete filegroup, even though it is empty

Hi All,
I have a SQL 2000 database that I had created a seperate file group for to
hold indexes. I have since deleted the indexes and want to delete the file
groups. When I execute the ALTER DATABASE <dbname> REMOVE FILEGROUP
<filegroupname> I receive an error indicating that 'The filegroup <filegroup>
cannot be removed because it is not empty'
If have verified that there are no tables or indexes in this filegroup and
have also run the following below queries to verify that the given filegroups
are empty:
select name,groupid
from sysindexes
where groupid=filegroup_id(<groupname>)
and indid > 0
Although there are no objects residing in the actual devices, they are still
listed in sysfiles. As such, even if I try to detach and reattach the DB,
the files are still linked and loaded with the database.
The tables to which the indexes existed are very large, so I also
stopped/restarted the sql services (thinking that possibly something may have
been stuck in memory) however that did not resolve the problem.
Has aonyone encountered this before? Is anyone aware of a fix for this?
Thanks,You can try using DBCC SHRINKFILE with the EmptyFile
option first. Then use ALTER DATABASE to remove the filegroup.
"DBADave" <DBADave@.discussions.microsoft.com> wrote in message
news:703563A7-BF30-445B-B563-2E0C323A9957@.microsoft.com...
> Hi All,
> I have a SQL 2000 database that I had created a seperate file group for to
> hold indexes. I have since deleted the indexes and want to delete the
file
> groups. When I execute the ALTER DATABASE <dbname> REMOVE FILEGROUP
> <filegroupname> I receive an error indicating that 'The filegroup
<filegroup>
> cannot be removed because it is not empty'
> If have verified that there are no tables or indexes in this filegroup and
> have also run the following below queries to verify that the given
filegroups
> are empty:
> select name,groupid
> from sysindexes
> where groupid=filegroup_id(<groupname>)
> and indid > 0
> Although there are no objects residing in the actual devices, they are
still
> listed in sysfiles. As such, even if I try to detach and reattach the DB,
> the files are still linked and loaded with the database.
> The tables to which the indexes existed are very large, so I also
> stopped/restarted the sql services (thinking that possibly something may
have
> been stuck in memory) however that did not resolve the problem.
> Has aonyone encountered this before? Is anyone aware of a fix for this?
> Thanks,|||I have tried this. The DBCC shows no output other then the standard DBCC
execution statement. When I attempt to issue an ALTER DATABASE to drop the
filegroups I get the error indicating that the filesgroups are not empty.
There are no objects in these filegroups, sysfilesgroups also does not show
the filegroups although sysfiles and sysfiles1 still show the filegroups that
I am trying to remove.
Any help would be greatly appreciated.
Thanks,
"Armando Prato" wrote:
> You can try using DBCC SHRINKFILE with the EmptyFile
> option first. Then use ALTER DATABASE to remove the filegroup.
> "DBADave" <DBADave@.discussions.microsoft.com> wrote in message
> news:703563A7-BF30-445B-B563-2E0C323A9957@.microsoft.com...
> > Hi All,
> >
> > I have a SQL 2000 database that I had created a seperate file group for to
> > hold indexes. I have since deleted the indexes and want to delete the
> file
> > groups. When I execute the ALTER DATABASE <dbname> REMOVE FILEGROUP
> > <filegroupname> I receive an error indicating that 'The filegroup
> <filegroup>
> > cannot be removed because it is not empty'
> >
> > If have verified that there are no tables or indexes in this filegroup and
> > have also run the following below queries to verify that the given
> filegroups
> > are empty:
> >
> > select name,groupid
> > from sysindexes
> > where groupid=filegroup_id(<groupname>)
> > and indid > 0
> >
> > Although there are no objects residing in the actual devices, they are
> still
> > listed in sysfiles. As such, even if I try to detach and reattach the DB,
> > the files are still linked and loaded with the database.
> >
> > The tables to which the indexes existed are very large, so I also
> > stopped/restarted the sql services (thinking that possibly something may
> have
> > been stuck in memory) however that did not resolve the problem.
> >
> > Has aonyone encountered this before? Is anyone aware of a fix for this?
> >
> > Thanks,
>
>|||This is kind of weird, but if i manually add the filegroup records back to
sysfilesgroups I can then see that there is an empty file in each (also
verified in EM by then looking at the filegroups properties to see the number
of files within). I was then able to ALTER DATABASE with a REMOVE FILE
refernecing what the original file name was, then issue an ALTER DATABASE
with a REMOVE FILEGROUP.
I am all set now.
Thanks All,
Dave
"DBADave" wrote:
> I have tried this. The DBCC shows no output other then the standard DBCC
> execution statement. When I attempt to issue an ALTER DATABASE to drop the
> filegroups I get the error indicating that the filesgroups are not empty.
> There are no objects in these filegroups, sysfilesgroups also does not show
> the filegroups although sysfiles and sysfiles1 still show the filegroups that
> I am trying to remove.
> Any help would be greatly appreciated.
> Thanks,
>
> "Armando Prato" wrote:
> > You can try using DBCC SHRINKFILE with the EmptyFile
> > option first. Then use ALTER DATABASE to remove the filegroup.
> >
> > "DBADave" <DBADave@.discussions.microsoft.com> wrote in message
> > news:703563A7-BF30-445B-B563-2E0C323A9957@.microsoft.com...
> > > Hi All,
> > >
> > > I have a SQL 2000 database that I had created a seperate file group for to
> > > hold indexes. I have since deleted the indexes and want to delete the
> > file
> > > groups. When I execute the ALTER DATABASE <dbname> REMOVE FILEGROUP
> > > <filegroupname> I receive an error indicating that 'The filegroup
> > <filegroup>
> > > cannot be removed because it is not empty'
> > >
> > > If have verified that there are no tables or indexes in this filegroup and
> > > have also run the following below queries to verify that the given
> > filegroups
> > > are empty:
> > >
> > > select name,groupid
> > > from sysindexes
> > > where groupid=filegroup_id(<groupname>)
> > > and indid > 0
> > >
> > > Although there are no objects residing in the actual devices, they are
> > still
> > > listed in sysfiles. As such, even if I try to detach and reattach the DB,
> > > the files are still linked and loaded with the database.
> > >
> > > The tables to which the indexes existed are very large, so I also
> > > stopped/restarted the sql services (thinking that possibly something may
> > have
> > > been stuck in memory) however that did not resolve the problem.
> > >
> > > Has aonyone encountered this before? Is anyone aware of a fix for this?
> > >
> > > Thanks,
> >
> >
> >|||Have you tried a DBCC SHRINKFILE with EMPTYFILE on the member files and then
dropping the files first?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
.
"DBADave" <DBADave@.discussions.microsoft.com> wrote in message
news:95372080-4621-4B1B-9F3E-907D7503D8B9@.microsoft.com...
I have tried this. The DBCC shows no output other then the standard DBCC
execution statement. When I attempt to issue an ALTER DATABASE to drop the
filegroups I get the error indicating that the filesgroups are not empty.
There are no objects in these filegroups, sysfilesgroups also does not show
the filegroups although sysfiles and sysfiles1 still show the filegroups
that
I am trying to remove.
Any help would be greatly appreciated.
Thanks,
"Armando Prato" wrote:
> You can try using DBCC SHRINKFILE with the EmptyFile
> option first. Then use ALTER DATABASE to remove the filegroup.
> "DBADave" <DBADave@.discussions.microsoft.com> wrote in message
> news:703563A7-BF30-445B-B563-2E0C323A9957@.microsoft.com...
> > Hi All,
> >
> > I have a SQL 2000 database that I had created a seperate file group for
> > to
> > hold indexes. I have since deleted the indexes and want to delete the
> file
> > groups. When I execute the ALTER DATABASE <dbname> REMOVE FILEGROUP
> > <filegroupname> I receive an error indicating that 'The filegroup
> <filegroup>
> > cannot be removed because it is not empty'
> >
> > If have verified that there are no tables or indexes in this filegroup
> > and
> > have also run the following below queries to verify that the given
> filegroups
> > are empty:
> >
> > select name,groupid
> > from sysindexes
> > where groupid=filegroup_id(<groupname>)
> > and indid > 0
> >
> > Although there are no objects residing in the actual devices, they are
> still
> > listed in sysfiles. As such, even if I try to detach and reattach the
> > DB,
> > the files are still linked and loaded with the database.
> >
> > The tables to which the indexes existed are very large, so I also
> > stopped/restarted the sql services (thinking that possibly something may
> have
> > been stuck in memory) however that did not resolve the problem.
> >
> > Has aonyone encountered this before? Is anyone aware of a fix for this?
> >
> > Thanks,
>
>

Thursday, March 8, 2012

Can't delete filegroup, even though it is empty

Can't created a linked server on a named instance to default insta

I have been trying to create a linked server on a named instance to a defaul
t
instance using intergrated security. It seems to work fine from a default
instance to any other SQL instance, including a named instance, but any time
I create the linked server on the named instance a call to the linked server
fails with the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
All servers are running SQL Server 2000 and the only difference in the
installation besides the fact one is named, is that the named instance is SP
4
and all others are SP3.
From a default instance the following works fine:
sp_addlinkedserver 'ORDEV01'
ORDEV01.Master.dbo.sp_helpdb
and the following to a named instance works as well:
sp_addlinkedserver 'LOU\Master'
[LOU\Master].Master.dbo.sp_helpdb
But if I try to created a linked server on the name dinstance LOU\Master I
get the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Thanks in advance for any help.Byron
Does the instance have Windows Authentication?
"Byron" <Byron@.discussions.microsoft.com> wrote in message
news:CB90A676-83FF-41CC-9C04-221920F998FF@.microsoft.com...
>I have been trying to create a linked server on a named instance to a
>default
> instance using intergrated security. It seems to work fine from a default
> instance to any other SQL instance, including a named instance, but any
> time
> I create the linked server on the named instance a call to the linked
> server
> fails with the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> All servers are running SQL Server 2000 and the only difference in the
> installation besides the fact one is named, is that the named instance is
> SP4
> and all others are SP3.
> From a default instance the following works fine:
> sp_addlinkedserver 'ORDEV01'
> ORDEV01.Master.dbo.sp_helpdb
> and the following to a named instance works as well:
> sp_addlinkedserver 'LOU\Master'
> [LOU\Master].Master.dbo.sp_helpdb
> But if I try to created a linked server on the name dinstance LOU\Master I
> get the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> Thanks in advance for any help.

Tuesday, March 27, 2012

can't get in anymore

can't get in anymore

can't get in anymore

Sunday, March 25, 2012

Cant get Access Database Synchronizer set up on client machine

Cant get Access Database Synchronizer set up on client machine

Can't find properties

Tuesday, March 20, 2012

Can''t drop trigger assembly

Can't drop trigger assembly

can't drop trigger

can't drop trigger

can't drop trigger

Monday, March 19, 2012

cant display calculated members

Can't Deploy AdventureWorks Database

Can't Deploy AdventureWorks Database

Sunday, March 11, 2012

Can't Deploy AdventureWorks Database

Can't delete Replicated Database

Can't delete filegroup, even though it is empty

Thursday, March 8, 2012

Can't delete filegroup, even though it is empty

Can't delete filegroup, even though it is empty

Can't created a linked server on a named instance to default insta

connect from ASP app

Blog Archive

About Me