Wise Package Studio v7 SP3 & Wise Repositary Manager Configuration
Wise Package Studio & Wise Repositary Manager
I have just ordered a copy of Wise Package Studio 7 SP3, on installing i am having problems creating the 3 backend DB's on a SQL (2008) server, as i go through the repository wizard i supple the SQL server name and select SQL Authentication with a valid account and password with SYSAdmin permissions (tried and tested), all seems good the Wise Share Point is Created at the specified location but the whole process fails with "A database processing error was encountered".
In the event viewer on the SQL server all the error message says is as below:
Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: Logon
Event ID: 18456
Date: 5/11/2009
Time: 5:08:51 PM
User: N/A
Computer: BAS-FLU-SQL-01
Description:
Login failed for user 'sa'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.16.11.15]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00 .H......
0008: 0f 00 00 00 42 00 41 00 ....B.A.
0010: 53 00 2d 00 46 00 4c 00 S.-.F.L.
0018: 55 00 2d 00 53 00 51 00 U.-.S.Q.
0020: 4c 00 2d 00 30 00 31 00 L.-.0.1.
0028: 00 00 07 00 00 00 6d 00 ......m.
0030: 61 00 73 00 74 00 65 00 a.s.t.e.
0038: 72 00 00 00 r...
Can anyone throw light on the problem, i have setup WPS many times and never encountered these problems, maybe i am just doing something wrong but i have tried everything to get this working. I could really do with some help!!!
The PC i am using is running XPProSP3
Thanks in advance
sql setup
ensure you have tcp/ip enabled on your SQL box. (particularly on the nic SQL clients are likely to use) often this is disabled by default on new installations.
also ensure that you have enabled SQL auth on SQL. restart the SQL services and you should be ok.
John, Your reply implies that
John, Your reply implies that TCP/IP isn't enabled on the box itself. Presumably you meant that the OP should ensure that SQL's transport is set to be TCP/IP as opposed to Named Pipes.
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Thanks guys, i have had one
Thanks guys, i have had one of the SQL guru's check what you have suggested and apparently all is well with the SQL side of things, does anyone know if Visual Studio 2008 causes any issues with WPS 7 SP3 as this is the only pointer i have, i have run through this setup many times before and never encountered such issues with running the create db scripts. The only help the install log offers is below.
"WiseAdmin.log"
~~~~~~~~~~~~
Stopping WiseSvc... [Diagnostic Code: 997 (3E5h)]
Service 'WiseSvc' stopped. [Diagnostic Code: 1062 (426h)]
Failed to stop WiseSvc.
Preparing installation files...
Combining installation files from \\172.16.10.52\d$\data\Packaging\Wise Package Studio\DbSetup\Professional Edition 7.03\
Merging languages.ini [Diagnostic Code: 183 (B7h)]
Merging themes.ini [Diagnostic Code: 183 (B7h)]
Combining installation files from \\172.16.10.52\d$\data\Packaging\Wise Package Studio\DbSetup\Language Pack 7.03\
Merging languages.ini [Diagnostic Code: 183 (B7h)]
Combining installation files from \\172.16.10.52\d$\data\Packaging\Wise Package Studio\DbSetup\Common 7.03\
Merging report.ini [Diagnostic Code: 183 (B7h)]
Organizing installation files
Backing up existing share point files...
Backing up \\IPAddressWasHere\d$\data\packaging\WSP\ to \\172.16.10.52\d$\data\packaging\WSP\Backup\
Backing up \\IPAddressWasHere\d$\data\packaging\WSP\Workbench\ to \\172.16.10.52\d$\data\packaging\WSP\Backup\Workbench\ [Diagnostic Code: 18 (12h)]
Backing up \\IPAddressWasHere\d$\data\packaging\WSP\Workbench\dct\ to \\172.16.10.52\d$\data\packaging\WSP\Backup\Workbench\dct\ [Diagnostic Code: 18 (12h)]
Backing up \\IPAddressWasHere\d$\data\packaging\WSP\Templates\ to \\172.16.10.52\d$\data\packaging\WSP\Backup\Templates\ [Diagnostic Code: 18 (12h)]
Upgrading the existing share point directory...
Processing the share point databases...
Creating/upgrading Workbench
Unable to open db 'Workbench Database' on server '172.16.10.52'
DBSETUP: A database processing error was encountered.
DoMessageBox:A database processing error was encountered.
Your time and effort is appreciated...
Check the ODBC drivers
Do your System ODBC drivers pass the "access test" from within Control Panel?
Have you tried an install of SQL Express Server 2005 on your WPS box as an alternative, to test if that works OK. The instructions for setting up SQL Express 2005 are in the Altiris KB.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
ODBC Checked
I have checked the ODBC drivers and they appear to work correctly although Symantec don't say these should be pre-configured, I have installed SQLExpress 2005 (locally) and configured that but it still fails to connect to even that!. I have even dowloaded the trialware although we do have a valid license for Wise now, and nothing seems to work.
This is quickly becomming urgent and i don't really know which way to go with it.
Ed meant, have you checked
Ed meant, have you checked the connection without Wise in the way, i.e. through the 'ODBC Data Sources' Control Panel applet?
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Time to go to testing on a clean machine, or VM
The install process for WPS 7 is pretty foolproof from my experience, so I would recommend the following steps:
1. Start with a clean machine or virtual machine, with just XP installed and updated.
2. Install SQL Express 2005 Server SP1, following the configuration instructions in the KB article I mentioned earlier.
3. Install WPS 7 SP3 - if I recall correctly, I normally choose windows authentication when installing on the same box as SQL Express.
4. Run repository manager from the WPS start menu icons - this will prepare the database for user
5. Voila - it should all be working.
Once you have cracked this aspect, you should be in a position to move on.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.