MsSql , VPS , plsek software .... PROBLEM ! [:(]

Hi ,

like i said i have VPS plan but on this plan the plsek sofware does not support
MsSql , the stuff that host my website told me that they will not support anything that invovled to MsSql

so ... what i was doing till now ?

i download SqlExpress 2005 on the remote machine . and i can login to the Database engine using Windows Authentication ,

also , i have 'webs develeoper express' (asp.net) on my PC and also have SQLExpress 2005 - when i run my website on my PC i successfuly
insert some data into the DataTables .

but when i run the same file on the VPS (after i upload them using FTP)
that does not work and i see this message :

Cannot open database "horse" requested by the login. The login failed. Login failed for user 'VE326\IWPD_4(main)'.

my connectin string on my "DBLayer" class looks like this :

connString = @."Server=(local)\sqlexpress;Integrated Security=True;Database=horse";

ANY IDEA ?

thanks .

Hi greekhand,

The error messaged indicates that it's a login failure. So, just make sure the user account VE326\IWPD_4(main) has sufficient permission to the "horse" database. Open your Management Studio and connect to your db, select the "horse" database and expand it. In the "security" section, choose "Users" and verify if account "ve326\iwpd_4(main)" has been included. And if not, right click and slect "new users", you can assign permissions to that account here.

Hope my suggestion helps

MSQLSERVER service will not start

I have just been through the restoring of all the data on
my using a Third party backup software.
I cannot get my MSSQLService to start. Error comes up
cannot find the path specified.
An error 3 - (the system cannot find the path specified)
occured while performing this operation on the
MSSQLService service.
Can anyone help or point me in the direction of some
article so that I can get the local DB running on my
computer without reinstalling SQLserver.
Thanks| I cannot get my MSSQLService to start. Error comes up
| cannot find the path specified.
|
| An error 3 - (the system cannot find the path specified)
| occured while performing this operation on the
| MSSQLService service.
|
| Can anyone help or point me in the direction of some
| article so that I can get the local DB running on my
| computer without reinstalling SQLserver.
--
Hi Peter,
Try to start the SQL Server service from the command line in minimum
configuration and single user modes and post the output here for us to look
at.
--
Eric Cárdenas
SQL Server support

MSOLAP.DLL Version Numbers

I have been trying to install some third party software that checks for
pre-requisite software in my computer. The third party software is
returning the following diagnostic result (saying I do not heve the correct version of PTS).
Microsoft PivotTable Service 2000
Required: OLAP Server 8.0.986.0
Currently: OLAP Server 8.0.760.0
Status: Error

It is my understanding that "PTS" is MSOLAP.DLL.

I have Analysis Server 2000 SP3 installed and all appears OK.
According to other posts in this group, the correct version of
msolap.dll (pivot table services) for SP3 and SP3A is 8.0.760.0.

My version of msolap.dll currently installed is 8.0.2039.0, which I
believe to be the SP4 version of PTS

The third party software is searching for a version 8.0.986.0.
Nowhere in the MSDN world can I find ANY mention of 8.0.986.0 as a
version number of anything.

Is this an error in the third party diagnostic?
Where would they possibly be getting that version number (8.0.986.0)?
What do you think they are looking at when they say "OLAP SERVER"

The third party support people are saying I must uninstall Analysis

Server 2000 and then download and install PTSFullSP4.exe. I am not

prepared to take so drastic a step, especially given the strange

Product Titles and version numbers they are looking for.
Can anyone shed some light on this issue?

Version 8.00.2039 corresponds to the service pack 4 of SQL Server 2000.

So looks like you've got SP4 of PTS installed and not SP3.

From the error message it looks like the software you trying to install requires SP4 version of Analysis Server.

You can try and run SP4 setup for Analysis Services from

http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5&DisplayLang=en

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

MSDTC w/ Oracle 8i EventID=4156

On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MTxOCI registry settings in order to correct the problem of failed ODBC connections to an Oracle 8.1.7 linked server.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I]
"OracleXaLib"="oraclient8.dll"
"OracleSqlLib"="orasql8.dll"
"OracleOciLib"="oci.dll"
It appeared to fix our problems -- but...
After doing so, we began getting MSDTC EventID 4156 information events in the application log - String message: Session idle timeout over, tearing down the session.
Since making the registry change, 328 of these errors have occurred to date. The first one occurred ~2 hours after making the registry change.
OPENQUERY statements to the Oracle server are now intermittently requiring long access times (minutes) that used to take a split second.
Since making the registry change, 328 of these errors have occurred to date.
Are there any suggestions on how to rectify this problem?
Hello !!
I have the exact same error message. Did you find any resolution for this ?
Mirna.-
"elpepe" wrote:

> On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MTxOCI registry settings in order to correct the problem of failed ODBC connections to an Oracle 8.1.7 linked server.
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I]
> "OracleXaLib"="oraclient8.dll"
> "OracleSqlLib"="orasql8.dll"
> "OracleOciLib"="oci.dll"
> It appeared to fix our problems -- but...
> After doing so, we began getting MSDTC EventID 4156 information events in the application log - String message: Session idle timeout over, tearing down the session.
> Since making the registry change, 328 of these errors have occurred to date. The first one occurred ~2 hours after making the registry change.
> OPENQUERY statements to the Oracle server are now intermittently requiring long access times (minutes) that used to take a split second.
> Since making the registry change, 328 of these errors have occurred to date.
> Are there any suggestions on how to rectify this problem?
|||below is the likely solution
PRB: MS DTC Event 4156: "Session Idle Timeout Over"
Article ID : 290334
Last Review : February 20, 2002
Revision : 1.0
This article was previously published under Q290334
On this Page
SYMPTOMS
CAUSE
RESOLUTION
REFERENCES
SYMPTOMS
You may see the following entry in the application event log:
String message: Session idle timeout over, tearing down the session.
CAUSE
This message indicates that the connection between a Distributed Transaction Coordinator (DTC) client and Microsoft Distributed Transaction Coordinator (MS DTC) is being torn down due to inactivity.
RESOLUTION
This message is usually just informational and can be ignored. Under normal circumstances, MS DTC tears down inactive connections after 10 minutes of idle time.
REFERENCES
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
197810 FIX: Upgrading DTC to Close Idle Connections
250987 HOWTO: Reinstall MS DTC for a Nonclustered Windows NT 4.0 Server
279786 HOWTO: Reinstall MS DTC for a Nonclustered Windows 2000 Serve

Quote:

Originally posted by Mirna Da Costa
Hello !!
I have the exact same error message. Did you find any resolution for this ?
Mirna.-
"elpepe" wrote:

> On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MTxOCI registry settings in order to correct the problem of failed ODBC connections to an Oracle 8.1.7 linked server.
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOC I]
> "OracleXaLib"="oraclient8.dll"
> "OracleSqlLib"="orasql8.dll"
> "OracleOciLib"="oci.dll"
> It appeared to fix our problems -- but...
> After doing so, we began getting MSDTC EventID 4156 information events in the application log - String message: Session idle timeout over, tearing down the session.
> Since making the registry change, 328 of these errors have occurred to date. The first one occurred ~2 hours after making the registry change.
> OPENQUERY statements to the Oracle server are now intermittently requiring long access times (minutes) that used to take a split second.
> Since making the registry change, 328 of these errors have occurred to date.
> Are there any suggestions on how to rectify this problem?

MSDTC w/ Oracle 8i EventID=4156

On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\MT
xOCI registry settings in order to correct the problem of failed ODBC connec
tions to an Oracle 8.1.7 linked server.
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]
"OracleXaLib"="oraclient8.dll"
"OracleSqlLib"="orasql8.dll"
"OracleOciLib"="oci.dll"
It appeared to fix our problems -- but...
After doing so, we began getting MSDTC EventID 4156 information events in th
e application log - String message: Session idle timeout over, tearing down
the session.
Since making the registry change, 328 of these errors have occurred to date.
The first one occurred ~2 hours after making the registry change.
OPENQUERY statements to the Oracle server are now intermittently requiring l
ong access times (minutes) that used to take a split second.
Since making the registry change, 328 of these errors have occurred to date.
Are there any suggestions on how to rectify this problem?Hello !!
I have the exact same error message. Did you find any resolution for this '
Mirna.-
"elpepe" wrote:

> On June 11th, we changed the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ MSDTC\
MTxOCI registry settings in order to correct the problem of failed ODBC conn
ections to an Oracle 8.1.7 linked server.
> & #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSDTC\MTxOCI]
> "OracleXaLib"="oraclient8.dll"
> "OracleSqlLib"="orasql8.dll"
> "OracleOciLib"="oci.dll"
> It appeared to fix our problems -- but...
> After doing so, we began getting MSDTC EventID 4156 information events in
the application log - String message: Session idle timeout over, tearing do
wn the session.
> Since making the registry change, 328 of these errors have occurred to dat
e. The first one occurred ~2 hours after making the registry change.
> OPENQUERY statements to the Oracle server are now intermittently requiring
long access times (minutes) that used to take a split second.
> Since making the registry change, 328 of these errors have occurred to dat
e.
> Are there any suggestions on how to rectify this problem?|||below is the likely solution
PRB: MS DTC Event 4156: "Session Idle Timeout Over"
Article ID : 290334
Last Review : February 20, 2002
Revision : 1.0
This article was previously published under Q290334
On this Page
SYMPTOMS
CAUSE
RESOLUTION
REFERENCES
SYMPTOMS
You may see the following entry in the application event log:
String message: Session idle timeout over, tearing down the session.
CAUSE
This message indicates that the connection between a Distributed
Transaction Coordinator (DTC) client and Microsoft Distributed
Transaction Coordinator (MS DTC) is being torn down due to inactivity.
RESOLUTION
This message is usually just informational and can be ignored. Under
normal circumstances, MS DTC tears down inactive connections after 10
minutes of idle time.
REFERENCES
For additional information, click the article numbers below to view the
articles in the Microsoft Knowledge Base:
197810 FIX: Upgrading DTC to Close Idle Connections
250987 HOWTO: Reinstall MS DTC for a Nonclustered Windows NT 4.0 Server
279786 HOWTO: Reinstall MS DTC for a Nonclustered Windows 2000 Serve
Mirna Da Costa wrote:[vbcol=seagreen]
> *Hello !!
> I have the exact same error message. Did you find any resolution for
> this '
> Mirna.-
>
> "elpepe" wrote:
>
> MSDTC\MTxOCI registry settings in order to correct the problem of
> failed ODBC connections to an Oracle 8.1.7 linked server.
> events in the application log - String message: Session idle timeout
> over, tearing down the session.
> to date. The first one occurred ~2 hours after making the registry
> change.
> requiring long access times (minutes) that used to take a split
> second.
> to date.
acsekar
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message808237.html